Database Users

Xdarit doesn't write with new .nbf files ?

I use the Xdarit to read & write the Rom image from my MDA.
I managed to read from the SD card and stored on my harddisk.
When I create back with a new rom .nbf files to the SD card and read back again to the harddisk, the SD show the original files size that from my MDA not the one that I'm going to upgrade to ? I rename the files to .nb1 extension.
Do I need to reformat the SD Card ? Do I need a new SD Card for the download ?
Dear XDA developer #..., please advice. I have been posting and yet to get some good advice and replies.
I would appreciate very much of your expertise in this matter.
Thanks again

they should be the same size, nb1, and nb0 files always are fixed size

more answer:
- when using xdarit you never have to format sd cards.
- renaming files will probably confuse XDARit, since this
is how xdarit recognizes what kind of file it has.

What I meant original file sizes.
1. Read from SD Card ( backup from MDA )
bootloader 5-15.nb0 256 K
WindowsCE 5-15.nb1 32,512 K
2. Write to SD Card ( with new ruu extract from O2 ie )
bootloader 5-15.nb0 256 K
WindowsCE NK_Wallaby31413wee_O2_Fulll.nbf 31,745 K
3. Read back the backup step 2.
bootloader 5-15v1.nb0 256 K
WindowsCE 5-15v1.nb1 32,512 K
As you mentioned, the files size are fixed, therefore my files of
the 5-15v1.nb1 should have the content of the NK-Wallaby.....
and I should had leave the file extention as .nbf without rename it to .nb1
Or should i had wite back using the step 1 files name ?
Please advice, many thanks

if you rename an .nbf file to .nb1, you will burn an incorrect os image
to your xda. making it unbootable in OS mode.
( your bootloader will still work )
also, be careful updating your bootloader, if it fails somehow
it is very difficult to restore your xda
if you just want to update your OS, only write the ..nb1 file
or select the .nbf from your distribution, without renaming it.
this http://openwince.sourceforge.net/jtag/iPAQ-3600/ might
give you an impression on what you would have to do, to repair
your xda after you've trashed your bootloader

Bootloader still appear but buttons not working ?
Thanks XDA developers,
My case is that I might accidently overwrite the bootloader.
The bootloader still be able to appear and the GSM OK showed but none of the functions button be able to work.
Do you think there is a way to work around ?
Many thanks for your replies

can u tell about bootloader version?

Bootloader v 5.15 on a T-Mobile MDA with 3.13.12 GER & Radio T310.

i think u can try to make sd card that contain wallaby path (.nb2) using xdarit... logically u can access "action button" to flash the rom.... this is only way to activate "action button"
after insert sd card u can go on bootloader and see wallaby path, press action button, if it work u can flash the rom (may be u should find exact rom that installed before xda died, more work?)
hope u can fix this prob
regards

Hello All,
I can't write new ROM image to SD card with XDArit: I can read image from card, but when I try write new ROM image, I get "Failed to open device \\Physical device12" error message. I try both USB and PCMCIA card readers, but don’t work… What is the problem? (My PC is an Asus P4 notebook with WinXP Pro)
Thx your help & sorry my bad English
Hanzy

try to change device "mass storage device" with driver from manufacture, use one of xdarit executable 180kb or 1.39mb (find out in other thread)

Hello,
I install manufacturer's drivers, but isn't work
I download (found) only 180kb version of XDArit (and source code, but my C++ knowledge... khm...)
Can you write the 1,3mb version's link from me?
Thx

from http://xda-developers.com/forum/viewtopic.php?t=1094&highlight=xdarit
found this link, try it
http://givemebeer.com:8080/warez/XDA/xdarit.exe

Hi,
thx your help...
I read on another thread, XDArit work only with USB 1.1 ports... My laptop have only USB 2.0 ports... :roll: I changed my laptop with one old IBM Thinkpad and XDArit work correctly...
Regadrs & thanks
Hanzy

Not really, coz im using usb 2.0 and its work normally

I only have USB 2.0 ports too and it worked fine.

fastblazer said:
try to change device "mass storage device" with driver from manufacture, use one of xdarit executable 180kb or 1.39mb (find out in other thread)
Click to expand...
Click to collapse
Just searching for why I couldn't get XDArit to work with my system - seems the larger (presumably debug) build of XDArit has what's needed to work with the v4 nbf's - thanks for the pointer!

XDArit new version more problem than the old ones ?

Dear XDA Developer #.....,
I did used the old version od XDArit to read and write the Boot+CE with not much of problem. The only thing to be careful is the Select SD card options because the physical Harddisk is one of the choices.
I noticed you had improvised the new version of XDArit to exclude the Harddisk choice but it seems imposible to used the write to SD option.
It always said cannot open physical drive #....
If i am using a 6 in 1 USB travel flash with Flash Memory on it, is this a problem for the XDArit to reconised which drive is the SD card ?
I did a bootloader backup on the SD card from the XDA, I am able to select the SD drive with no problem, it show HTC$WALLABY00 and be able to save to the harddisk ...nbo. I continue to write back the same file it show the cannot open physical drive #.... problem.
The other thing to confirm, how many block are written to SD Card if i choose to write only the Wallaby Patch Tools Image ? I did many time on the SD Card, sometime it said 2 Blocks and sometime 9 Blocks ??? It was able to write once but the XDArit did not write to the SD Card, instead it wrote to the Flash Memory parts of my travel flash ????
Do you think we are able to have the old version back on your homepage to download, give us a selection of version choice.
I would be much grateful if you be able to attached the old version to me for testing, my email : [email protected]
Many thanks for your reply

The old version is in:
http://xda-developers.com/XDArit/old
Please tell us if the old version does work for you...

Bummer Gus...
Works good for me.... Now I just have to figure out how to use it to repair my radio stack...!!!
Another step for mankind, but a huge leap for Todd (aka OldManTod)...
THANK YOU!!!!!

old version work for me to, now i can write SD cards

We'll rework the current version, but read the XDArit page for the warning on the old version:
DO NOT CLICK 'YES' IF IT WARNS YOU'RE ABOUT TO OVERWRITE YOUR HARDDISK, EVEN IF IT LISTS THE SD-CARD AS DISK.

XDARit NT 4 Problem
Hi All,
I wonder if someone can tell me how to fix the XDArit.exe Entry Point Not Found error when trying to run this program under Win NT4.0 SP6?
I'm new to xda-developers.com, but earlier today I tried to update the CE ROM using the official o2 image and despite my USB connection working for ActiveSync, the update program tells me it can't open a USB port and now the PDA is showing only the progress bar screen. From reading your excellent site I guess I need to create an SD boot card to fix the problem, but then ran into the above problem with xdarit !
Please can someone help?
Thanks
Dave :roll:

(HELP) Tried to upgrade to WM2003

I downloaded the upgrade from Siemens web site and ran the program.
my phone is now stuck in the upgrade window and will not reboot.
Any Sugestions?

RE:
Phone will not reconect to activesync either.

RE:
Tried a hard reset and soft reset no results.
I think I'm Screwd

You need to get an sd memory card and card reader/writer, using the tools available here on the site you will need to write a rom to the sd card through sd card reader on your pc, then you go to bootloader mode and the sd card will burn the rom to your xda.

Thanks for the advise. I have a 1Gb sd card so I will get a reader.
I'm kind curious about Bootloader? Can Anyone enlighten me or point me to posts that have the info I'll need.
My computer is running windows is this ok?
All advise is much appreciated

Thanks For all the help. I fixed the Problem with the Bootloader. Finished the upgrade to A.30.09.
I just wanted to say that it is AWESOME to have a sight like this when the manufacturer doesn't have a clue how to answer many of these Q's.
THANK YOU QMAN (i got the info off one of your posts) AND ALL WHO PASS ON KNOWLEDGE HERE!!!!!!!!!!!1

How to fix failure during upgrading ROM

I have a siemens sx56 with AT&T. I was trying to upgrade the ROM version to unlock it. Using XDA developer software and during this process, somehow the connection between the computer and the phone stopped (active Sync). Now the phone is not responding and the screen still displaying the upgrading process. I tried to reconnect but the Active sync does not recognize the devise. I read in this forum that you can solve this problem by using SD card with a good ROM version. Here is what I did. I copied the NK.nbf to the SD card using my computer SD read/write slot. I inserted the SD card in the phone and did the boot loader mode. What I got is "Wallaby boot loader v5.22 GSM OK" that set. Does the phone will automatically ask to press action to start flashing or I have to press a certain key. I tryed all the keys but they give me different tests that they work fine. So far I am not able to find the key that will install the the cooked rom. After that, when I tried to use the SD card in the computer, it did not recognize the card and ask me to format the SD card. I tried the fat and the fat 32 format and download NK.nb1 and/or NK.nbf and again I got the samething. Do I need to down load the ROM file using the XDAtool or just copying the file from the computer to sd directory will do it. I would really appreciate it if someone points out the best way of handling this problem (i.e. get the phone to work with the appropriate ROM and unlocking it) thanks.

Seif said:
I have a siemens sx56 with AT&T. I was trying to upgrade the ROM version to unlock it. Using XDA developer software and during this process, somehow the connection between the computer and the phone stopped (active Sync). Now the phone is not responding and the screen still displaying the upgrading process. I tried to reconnect but the Active sync does not recognize the devise. I read in this forum that you can solve this problem by using SD card with a good ROM version. Here is what I did. I copied the NK.nbf to the SD card using my computer SD read/write slot. I inserted the SD card in the phone and did the boot loader mode. What I got is "Wallaby boot loader v5.22 GSM OK" that set. Does the phone will automatically ask to press action to start flashing or I have to press a certain key. I tryed all the keys but they give me different tests that they work fine. So far I am not able to find the key that will install the the cooked rom. After that, when I tried to use the SD card in the computer, it did not recognize the card and ask me to format the SD card. I tried the fat and the fat 32 format and download NK.nb1 and/or NK.nbf and again I got the samething. Do I need to down load the ROM file using the XDAtool or just copying the file from the computer to sd directory will do it. I would really appreciate it if someone points out the best way of handling this problem (i.e. get the phone to work with the appropriate ROM and unlocking it) thanks.
Click to expand...
Click to collapse
Bro, you shouldn't change the Sd fat you erased what's written on it anyway your unit is still on the safe side and you can bring it to normal.
First of all downgrade your bootloader to 5.15 >>>
goto this http://forum.xda-developers.com/viewtopic.php?t=3274

Hi,
I also have exactly the same problem with my Siemens SX56 as those of Seif's. My Wallaby's boot loader version is 5.22. Ramram said that the first thing to do is to downgrage bootloader. But I couldn't understand how to downgrade the bootloader because I do not have a copy of old bootloader. Should I use 'OSImageTools' or 'XDArit' to write backed up CE image to SD card?
Seif, how did you solve your problem?
Best Regards

rafia said:
Hi,
I also have exactly the same problem with my Siemens SX56 as those of Seif's. My Wallaby's boot loader version is 5.22. Ramram said that the first thing to do is to downgrage bootloader. But I couldn't understand how to downgrade the bootloader because I do not have a copy of old bootloader. Should I use 'OSImageTools' or 'XDArit' to write backed up CE image to SD card?
Seif, how did you solve your problem?
Best Regards
Click to expand...
Click to collapse
You need XDArit to write the rom to your SD read the past post on how to copy rom to your SD which is the safest way of installing the rom into the device, by using XDAtools press on FIX BROKEN BOOTLOADER this will downgrade you bootloader to 5.15 don't forget to connect your unit to the cradle when you want to downgrade.
I recommend 1rst of all to make a quick search in threads to be totaly ready for this
this would help :
http://forum.xda-developers.com/viewtopic.php?t=6581&highlight=downgrade+bootloader
http://forum.xda-developers.com/viewtopic.php?t=2068&highlight=downgrade+bootloader
Good Luck now.

Update : How to fix failure during upgrading ROM
The problem was solved. Here is what I did. I copied the NK.nbf file to the SD card using the XDAtools. It seems that the XDAtools uses special format for the bootloader that well recognize the ROM file on the SD card. Rafia your bootloader (v5.22) is fine you do not need to downgrade it.
You should follow this procedure:
1. Install ActiveSync that comes with the device.
2. download XDAtools from this site and install it in your computer.
3. Cook the ROM ( or get it by extracting the zip file from the XDA developers special edition ROM.)
4. Use the XDAtools to copy the cooked NK.nbf file from your computer to the directory of the SD card
5. Insert the SD card in the dead device and go to the bootloader mode (soft reset while pressing power key). Make sure it has more than 80% battery before starting.
6. If it is still working and the bootloader ver. is older than 6.22, it will ask you to press action to start flasing.
7. Once finished, remove the SD card and hard reset, wait 60 sec and hard reset again.
Good Luck and special thanks to Biso for his help.

Re: Update : How to fix failure during upgrading ROM
Seif said:
The problem was solved. Here is what I did. I copied the NK.nbf file to the SD card using the XDAtools. It seems that the XDAtools uses special format for the bootloader that well recognize the ROM file on the SD card. Rafia your bootloader (v5.22) is fine you do not need to downgrade it.
You should follow this procedure:
1. Install ActiveSync that comes with the device.
2. download XDAtools from this site and install it in your computer.
3. Cook the ROM ( or get it by extracting the zip file from the XDA developers special edition ROM.)
4. Use the XDAtools to copy the cooked NK.nbf file from your computer to the directory of the SD card
5. Insert the SD card in the dead device and go to the bootloader mode (soft reset while pressing power key). Make sure it has more than 80% battery before starting.
6. If it is still working and the bootloader ver. is older than 6.22, it will ask you to press action to start flasing.
7. Once finished, remove the SD card and hard reset, wait 60 sec and hard reset again.
Click to expand...
Click to collapse
Thanks a MILLION for this info. I'm in the same boat, with bootloader 5.22. One question though, when I'm in bootloader mode, which option do I choose from the menu to transfer the ROM to my device from the SD card? Will there be something automatically coming up? Or will I use one of the options listed below:
1. CE ROM TO SD
2. BOOT TO SD
3. CE + BOOT TO SD
4. GSM ROM TO SD
5. CE + GSM TO SD
By the way, so I never do anything to ruin my device again, can someone please explain what each option does?? I really don't have a clue.

as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's

Rudegar said:
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Click to expand...
Click to collapse
Thanks for answering my question. Now I simply need to find a really good ROM to use to load back onto my device. What I would like to do is end up with Windows Mobile 2003, but the device is locked at the moment.
Can someone recommend a ROM for me to load onto the device so that I can then unlock it and THEN upgrade to 2003? Or is there a 2003 ROM out there that will also unlock? Originally, I ended up in this predicament by upgrading to the 2003 upgrade from Rogers AT&T, but that locked the device on me. I then tried to use a cooked 2003 ROM, and that's where I am now, without a useable device.
Thanks for all replies!

Linger1974 said:
Rudegar said:
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Click to expand...
Click to collapse
Thanks for answering my question. Now I simply need to find a really good ROM to use to load back onto my device. What I would like to do is end up with Windows Mobile 2003, but the device is locked at the moment.
Can someone recommend a ROM for me to load onto the device so that I can then unlock it and THEN upgrade to 2003? Or is there a 2003 ROM out there that will also unlock? Originally, I ended up in this predicament by upgrading to the 2003 upgrade from Rogers AT&T, but that locked the device on me. I then tried to use a cooked 2003 ROM, and that's where I am now, without a useable device.
Thanks for all replies!
Click to expand...
Click to collapse
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck

First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck[/quote]
Thanks, Ramram. I'm sure I'll have more success this time, but it's just odd that I went from a 2002 ROM, which was unlocked, to the Rogers 2003 ROM, and the phone was locked after that.
I guess I should stay away from that Rogers ROM then?

Linger1974 said:
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck
Click to expand...
Click to collapse
Thanks, Ramram. I'm sure I'll have more success this time, but it's just odd that I went from a 2002 ROM, which was unlocked, to the Rogers 2003 ROM, and the phone was locked after that.
I guess I should stay away from that Rogers ROM then?[/quote]
Why to worry about the Rogers Rom you know now a way to unlock your phone.
I assume the Rogers rom is based like the At&t rom which it has the sound clipping bug , so I'd rather say that you could cook a T-mobile rom 4.01.16 WM2003 and try it it does not have the sound clipping bug..

2003se upgrade for a dummy

So, ive read post after post on performing this task and it is still beyond my capabilities. My wallaby is running ppc2002, rom version is 3.20.06, radio version 4.21.01 protocol version 32s54. It's running bootloader 6.22, i havent got active sync, xdatools wont run due to missing dll's or some such thing. Have a 1gig sd and a 512mb mmc,,,,
How can i upgrade with this setup? visited rom kitchen (awesome site) and cooked up a rom, extracted NK.nbf,
Need help! Surely i can upgrade with this equipment,

http://www.romkitchen.de/ make an exe then

Rudegar said:
http://www.romkitchen.de/ make an exe then
Click to expand...
Click to collapse
So is the exe executable from an sd card?

no the exe is only for activesync upgrades
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
how to flash using sd
if the tool is missing dll's then type in the name of the dll in google and find a place to get the dll and it will work

Rudegar said:
no the exe is only for activesync upgrades
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
how to flash using sd
if the tool is missing dll's then type in the name of the dll in google and find a place to get the dll and it will work
Click to expand...
Click to collapse
Right, well got active sync which meens the dll's i needed are in system 32 or whatever. But,,, Does bootloader 6.22 cause problems?? Thanks for all the help,, sure this fone is a bit old but who cares. Massive screen, runs office, windows media, touch screen, great fone

Any suggestions? I cant be the only one without a data cable or cradle. At the end of the day i want the fone to run best as possible. I am thinking there is alot more compatable software for wm2003 then ppc2002? @ the moment im running mame and pacman,,,,,,,, Speaking of software, is the media player in 2002 meant to be slow? As far as video go's ive given up there.

what is your problem?

Problem is i dont seem to be able to downgrade from bootloader 6.22 to 5.15 so i can update the rom to 2003. doing ll this without a data cable or cradle.

Bootloader should not cause any problems.
Missing Dll´s for XDATools came as you have ssen correctly form ActiveSync. So you need to install this programm on your PC to use XDATools. Afterwards you will be able to wirte the ROM on your SD-Card and then flash the new ROM on your device.
So if you don´t have any cradle or cable, and don´t sync with ActiveSync, how did you manage your conacts,install software, exchange files, ....?
Stefan

I see the confusion
I have card reader's on the front panel of my pc. So i am using xardit to transfer the bootloader images onto either an sd or an MMC card. So i transfer the patch with the NB2 extension on to the card. Cold reboot xda and it gets to the normal screen telling me i need the keycard.
I can use either xdarit or isoimagetool to transfer the .NB1 file on to an SD.
I have no data cable, so these are the only methods i can use. Just pc with multi card card, sd car, mmc card.
LumpiStefan, the rom kitchen is a damn fine peice of work!

when i had a wallaby i only ever flashed it using a sdcard reader
was pretty easy used ositool put the nbf / nb1 on the sdcard
after which the cardreader could no longer read the sdcard(that mean it's successfully planted)
then i put in the sdcard and entered the bootloader and it autostart upgrading
and when it's don i hardreset and thats it

Hi And thanks
I have tried this with a 1g toshiba sd and a 512 sandisk mmc, neither seem to auto start an update. I have browsed the web a bit and have found different theories on bootloader being a problem. My card reader is a panel on the front of my pc, or using my ngage. tried formatting fat16 or fat32. Im sure it's currently ppc2002 as this is the first screen after the o2 water screen

I think your problems come from your card reader. Many people have reported, that the internal card reader causes problems in writing the ROMs in correct way on the cards. I would s uggest to use an external card reader/writer.....
Stefan

and those are only 10£$€'ish

Thanks guys for your help, all up and running now. I appreciate the advise. Rudegar, my problem was getting the wrong info from elsewhere, the solution was the card reader, Cost me $9.00 au to buy one. I thank you both