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!

PLEASE HELP Failed ROM update - Gives me blank screen

During the flashing process my Qtek complete gone, no ROM available I just get blank screen, my question is, could I use other Qtek to back-up ROM to the SD card or hard disk (with new program), after then I can use this back-up to restore my ROM? Or What I can I do to restore the Qtek to a factory default state?
Thanks

im sure u can, atleast I did on my t-mobile ppc.
if u cant write to SD card... take the card to a dealer or
show room display, insert the card, boot to bootloader (reset +push on)
and write urself a boot image on your SD card...
i know it worked for me !

What ROM you are talking about CE or GSM ?
hello
please find some information about Flashing your Qtek ROM using the 'SD Card' or 'Bootloader' Method
http://www.xda-developers.com/forum/viewtopic.php?t=1717
i hope this could help to recover your device back to normal but if it was GSM or Radio upgrade there's another method you can use the search tool here to get it and how to fix it
best regards and good luck
Othman
www.pocketpc4arab.com

Thanks
I was away some time I just come back. Let me to try, hope I could do it
What ever result of course I will let you know, this my help others too,

Clear instructions, please!

Hi,
I have a TMobile pocket pc, Rom version: 3.08.10 and Radio Version: 6.02, I want to upgrade it to WM2003, the problem is that I don't have a tmobile phone number, I saved my ROM on a sd card with the Wallaby Bootloader, I downloaded the "XDA OS Image Tool", could I put the "T-mobile ROM Windows Mobile 2003 upgrade 4.00.21" from Yorch and if it doesn't work just reload the old version with Wallaby?
Could I cook a Rom in the Kitchen and install it or I need PHP support?
Thanks

Yes to all, also you'll need to upgrade your radio stack to get the always on GPRS.
BTW where are you located?
HTH

How do I upgrade my radio? I'm in NY but I need the phone also in Europe.
when you said yes you mean also for the kitchen I need PHP support, does that mean a server like Apache installed on my computer?

btw in Wallaby I saved with the first option to the Sd, I think it was CE ROM TO SD, is that ok or I need to do something else?

mml770 said:
How do I upgrade my radio? I'm in NY but I need the phone also in Europe.
when you said yes you mean also for the kitchen I need PHP support, does that mean a server like Apache installed on my computer?
Click to expand...
Click to collapse
Yes on the kitchen!
The best way to upgrade the radio stack is to copy the needed files to
your devices Windows folder and install it from there. If you send me a PM with your email address I'll send you the needed files.
You lost me on the needing PHP support, why do you need that?
HTH

what are all these instructions at http://xda-developers.com/ROMkitchen/, is it for someone that wants to run the kitchen on his computer?
should I use the kitchen version .16 or it's more secure the .21 from yorch with XDA OS Image Tool?

mml770 said:
what are all these instructions at http://xda-developers.com/ROMkitchen/, is it for someone that wants to run the kitchen on his computer?
should I use the kitchen version .16 or it's more secure the .21 from yorch with XDA OS Image Tool?
Click to expand...
Click to collapse
Yes those instructions are for setting up your own kitchen.
I'd go with .21 cause thats what I'm using.
BTW you can also get ROM version 4.0021 from http://www.yorch.net
under Software.
HTH

I have the 4.00.21 version from Yorch my last question is what I need to select in Wallaby?
1. CE ROM TO SD
2. BOOT TO SD
3. CE+BOOT TO SD
4. GSM ROM TO SD (I guess not)
5. CE + GSM TO SD (also probably not)
Thanks...

Pick door number three and make sure that you have loaded onto the sd card only the nbf file from Yorch's site.

valheru said:
Pick door number three and make sure that you have loaded onto the sd card only the nbf file from Yorch's site.
Click to expand...
Click to collapse
you got my a little confused... I thought of backing up to the sd the actual rom and then writing the nbf file to the device, but now you said to load the nbf file to the sd... could please explain...Thanks

Okay, get the os toolset, an sd card reader/writer, an sd card of at least 64mb and do the following:
-install the os toolset
-put device in cradle
-run ostoolset and backup your ROM to your hard drive. Name it something like ppc2002-10-13-03 or something similar. This will backup your ROM only, not any installed programs
-remove your device
-insert the sd card into the reader/writer
-open os toolset again and select the new rom you downloaded from the internet
-select the sd card as the installation drive
-once its done copying put the sd card into your device
-run the wallaby bootloader and have it install the os to your device.
-hard reset when done as directed and BINGO
*** I will point out that it seems you have not read very many of the posts here. DO THIS BEFORE YOU DO ANY OF THE ABOVE ***

I'm actually going through this forum for a week till I decided to ask, since nobody wrote clearly how to do it, Thanks!
Now since I don't have a sd card reader, before I get it, is it possible to upgrade directly without having to do it with the sd card?
Another question, with which extension do I save the backup of my ROM, nb1, img, bin.
Thanks again

what's the difference if I copy the .nbf file to the SD reader or if I just copy it to the sd through the device?

Once again, please read the posts. You can't copy the file to the sd card while in the device for it will only copy the file as a file instead of copying it as a bootable interface. If you don't understand this then you should definitely read more posts. No offense.
You can, if you wish, just us the OS toolset to overwrite your device ROM with any ROM you choose. Just go to the ROM TOOLSET forum to download and follow the instructions there. It is very easy but be careful. I just believe in the aforementioned method for it forces you to take steps to prevent a total loss. I wish you the best of luck.
Oh, if you really want to update your ROM, etc., invest in a card reader. It'll cost you less than $30 which is less than 6% of what you paid for your device most likely.
No matter what you do make a backup of your current ROM!

valheru, thank you very much for taking your time, belive me that I really read allot of posts, if you could direct me in a thread that speaks about this I'll be very happy instead of using your time!
Now I just copied the nbf file to the sd card with OSImage Tool, and when I went in Wallaby it gave me the option to upgrade the ROM, is that ok? or I still need a sd reader,
Thanks again for all your help!

That sounds alright but make sure you make a backup of your current ROM first!

Great!!! It works, now one last question the Radio Version is 6.02, Qman what version did you send me and how do I upgrade?

ok here are the istructions to upgrade to ROM 4.00.21 for a TMobile Pocket Pc Phone Edition.
You just need a sd card of at least 64MB (maybe 32Mb will also work).
Download the OSImage Tool from http://www.xda-developers.com/XDAtools/ and install it.
Download the Upgrade to 4.00.21 from Yorch.net http://www.yorch.net/downloads/ROMS/T-mobileROM40021.rar.
-put device in cradle
-run osImage Tool and backup your ROM to your hard drive. Name it something like ppc2002-10-13-03 or something similar. This will backup your ROM only, not any installed programs
-open osImage Tool again and select the new rom you downloaded from the internet
-select the sd card as the installation drive
-run the wallaby bootloader and have it install the os to your device.
-hard reset when done as directed and BINGO
(as you could notice some lines where copied from a previous post of valheru, sorry for not giving credit in the begining... :wink: )

@ mml770
When cutting and pasting someone else's post it is polite to quote them or at least give credit to them....hint hint 8)

mml770 said:
Great!!! It works, now one last question the Radio Version is 6.02, Qman what version did you send me and how do I upgrade?
Click to expand...
Click to collapse
Boy you guys sure have been having fun, I see! 8)
Its radio stack 6.24.
To upgrade just unzip then copy the four files to your devices Windows folder then run RSUpgrade.exe from there.

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..

Definitive instructions for ROM Backup/Update.

Sorry to ask this question which I know has been covered in so many other topics - but thats the problem - the topics are scattered and the answers are varied.
I have a Wizard derivative - an O2 XDA Mini S.
I have run the unlocking wizard and it is now unlocked.
I now want to
a. Backup the exisitng ROM
b. Backup the External ROM
c. Load an updated ROM.
I have tried the 'Unlock EXT ROM Wizard' - but still can't see the External ROM (in Total Commander for example) to back it up.
Can someone post a precise set of instructions for the step by step process for doing a. to c. above.
I am sure that others will find it useful as there still appears to be many posts from confused 'novices' to PPC (like me) who are trying various procedures on a hit and miss basis with varied success.

I just did the backup bit today.
Download aWizard 1.3b2
Run it, run the RAPI server using the 'e' command, wait till it starts, unlock the CID using 'u', then you can backup using the 'b' command, give it a name to backup to, and wait 15 or so minutes and it'll backup your GSM, OS, and Extended roms.
As for flashing, you can use the aWizard tool if you have the .nba rom files.
Or you can use one of the pre-packaged roms + flashers like the iMate one... but, that's where it gets a little perilous. AFAIK, the latest iMate rom will flash a locked Extended rom onto the device, which you can not edit any longer. So until someone figures out how to unlock the Extended rom, be careful.
My other idea would be to take the iMate full rom and break it up into the GSM, OS, and Extended roms. Once you do that, instead of using the pre-packaged flasher and rom, use aWizard to flash the GSM and OS roms and do the Extended part manually. Then you can keep an unlocked Extended rom (of your stock image) incase you ever want to revert to stock (since you backed up the stock GSM and OS roms in the first step).

Where is the aWizard 1.3b2. The unlocker I have is called lockiwizo2b and there is no u option.

Read the upgrading portion of the wizard forums, its all over the place there.
PS, be absolutely sure you want to upgrade, once you change, there is no going back, I did mine, I'd like to go back, but cannot.

jvanbrecht said:
Read the upgrading portion of the wizard forums, its all over the place there.
PS, be absolutely sure you want to upgrade, once you change, there is no going back, I did mine, I'd like to go back, but cannot.
Click to expand...
Click to collapse
Sure you can.
If you have an SD image you can go back to the T-Mobile original US load with no problem at all. You DID make an SD image of the ROM before you screwed around, right?
The SPL will not downgrade (you probably can do that by running the RUU for the "hacked-up" earlier Imate version with the 1.x SPL/IPL) but I've found no particular reason to.
I have verified that an SD image restore to the original T-Mo US firmware works from the Imate shipping RUU.

Genesis.
What is the best method for making the SD Image?

I would also like to know.
I would also like to know if the original Extended rom can be backed up after the iMate rom overwrites it.

pewe said:
Genesis.
What is the best method for making the SD Image?
Click to expand...
Click to collapse
You need:
1. A terminal program that can speak over the USB port. Terraterm has a patched version out which can do this.
2. A CID-unlocked device (it will NOT work if its not CID-unlocked!)
3. A SD card of 128MB or larger (buy a 128MB for just this purpose, as its a great backup device)
To use it:
1. Get into the tri-color screen (hold CAMERA, reset) and plug into the USB port.
2. Kill wcescomm.exe from Windows XP (this is the ActiveSync driver for the USB port)
3. Start your terminal porgram
4. Hit "return" to insure you have a command prompt.
5. Make sure your 128MB SD card is in the slot.
6. Type "r2sd all" and hit return.
The loader will dump the entire ROM (including extended ROM) to the SD card.
Note that this is NOT a file on a FAT filesystem - its a RAW data dump with a signature and checksum. As such you CANNOT read it onto your computer using a copy - you need a tool like "psdread" to read it from the card to a file on your PC.
If you use a NEW card, you can search for the end of valid data or do what I do and dump the entire 128MB (which is larger than the dump file for certain) and then just compress it - all the trailing zeros will compress to basically nothing.
Stick the card somewhere safe.
To RESTORE from the SD card, insert it with the power off in the Wizard, then power on while holding the CAMERA button. With the older ROMs the backlight will be OFF; with the new IMATE one it will be ON. It will tell you to press the VOICE key to load from the SD card. Do so, it verifies the integrity of the dump and loads it.
Note that the prompt only comes up for a few seconds and if you're using a 1.x release of firmware when you do this the backlight is OFF so its hard to see - but its there. Grab a flashlight if necessary.
Once you load something else on your unit from stock of course you can't go back unless you did this FIRST. This was the first thing I did when I got my MDA, so I have a copy of the T-Mobile "base software" on the SD card in case I pooch my device and need to go back to the OEM firmware.

Thanks Genesis. Very helpful guide.
I did another search on the forum using different search words and I found this post:
http://forum.xda-developers.com/viewtopic.php?t=37386&postdays=0&postorder=asc&start=0
and it looks like this is does the same thing - but without having to use other programmes like Terraterm.
Am I right?

Genesis3 said:
pewe said:
Genesis.
What is the best method for making the SD Image?
Click to expand...
Click to collapse
You need:
1. A terminal program that can speak over the USB port. Terraterm has a patched version out which can do this.
2. A CID-unlocked device (it will NOT work if its not CID-unlocked!)
3. A SD card of 128MB or larger (buy a 128MB for just this purpose, as its a great backup device)
To use it:
1. Get into the tri-color screen (hold CAMERA, reset) and plug into the USB port.
2. Kill wcescomm.exe from Windows XP (this is the ActiveSync driver for the USB port)
3. Start your terminal porgram
4. Hit "return" to insure you have a command prompt.
5. Make sure your 128MB SD card is in the slot.
6. Type "r2sd all" and hit return.
The loader will dump the entire ROM (including extended ROM) to the SD card.
Note that this is NOT a file on a FAT filesystem - its a RAW data dump with a signature and checksum. As such you CANNOT read it onto your computer using a copy - you need a tool like "psdread" to read it from the card to a file on your PC.
If you use a NEW card, you can search for the end of valid data or do what I do and dump the entire 128MB (which is larger than the dump file for certain) and then just compress it - all the trailing zeros will compress to basically nothing.
Stick the card somewhere safe.
To RESTORE from the SD card, insert it with the power off in the Wizard, then power on while holding the CAMERA button. With the older ROMs the backlight will be OFF; with the new IMATE one it will be ON. It will tell you to press the VOICE key to load from the SD card. Do so, it verifies the integrity of the dump and loads it.
Note that the prompt only comes up for a few seconds and if you're using a 1.x release of firmware when you do this the backlight is OFF so its hard to see - but its there. Grab a flashlight if necessary.
Once you load something else on your unit from stock of course you can't go back unless you did this FIRST. This was the first thing I did when I got my MDA, so I have a copy of the T-Mobile "base software" on the SD card in case I pooch my device and need to go back to the OEM firmware.
Click to expand...
Click to collapse
You, sir, are my new hero. You win 3 internets for this post.
Although, what would happen if I used my existing 512mb minisd card with apps already on it? Will it dump to a file and I can compress at that point? You mentioned it was non-readable on the card if I did that. I've already backed up the stock ROM using the aWizard tool, but if I used your method with a miniSD that had files already on it, would it blindly write to it, clobbering files, or write something to the card that was unreadable via a PC (basically not as a file on the filesystem), and if I put more stuff on the miniSD like apps or media, it'll overwrite the backup of the image?

If you do this to a card with data on it you will pooch all the data - it will scribble right on top of the FAT tables and destroy them.
Second, you won't know where the data you dumped ends. To be safe you should save 128MB of the card (from the front) to your file on the PC. This will result in a larger-than-necessary file, but that's ok.
You need tools like "psdread" and "psdwrite" to read and write the SD card in "raw" format - it is NOT a file that gets dumped, but just a RAW image of the ROM (with checksums)!
The only other "gotcha" is that depending on the EXACT configuration of the data you dump the SD card may refuse to reformat to its original capacity when you're doing doing this and/or refuse to reformat at all!
That's fixable by writing a block of zeros (e.g. 10kb or so worth) to the front of the card, which will clear what's confusing Windows (and the phone).

Genesis3 said:
If you do this to a card with data on it you will pooch all the data - it will scribble right on top of the FAT tables and destroy them.
Second, you won't know where the data you dumped ends. To be safe you should save 128MB of the card (from the front) to your file on the PC. This will result in a larger-than-necessary file, but that's ok.
You need tools like "psdread" and "psdwrite" to read and write the SD card in "raw" format - it is NOT a file that gets dumped, but just a RAW image of the ROM (with checksums)!
The only other "gotcha" is that depending on the EXACT configuration of the data you dump the SD card may refuse to reformat to its original capacity when you're doing doing this and/or refuse to reformat at all!
That's fixable by writing a block of zeros (e.g. 10kb or so worth) to the front of the card, which will clear what's confusing Windows (and the phone).
Click to expand...
Click to collapse
interesting. if I got a $10 128mb minisd, though, I wouldn't really care to use it in anything else other than this phone. I have a 512mb already for daily usage, so the 128mb would be for a backup incase I want to revert to the standard OOB rom from T-Mobile.
As long as the rom is written to the card and will read from if I choose to restore, I don't care if windows ever reads from the card again.

pewe said:
Thanks Genesis. Very helpful guide.
I did another search on the forum using different search words and I found this post:
http://forum.xda-developers.com/viewtopic.php?t=37386&postdays=0&postorder=asc&start=0
and it looks like this is does the same thing - but without having to use other programmes like Terraterm.
Am I right?
Click to expand...
Click to collapse
That's the tool I was talking about. This will dump the roms to a file on your PC that is readable. You can edit stuff, rewrite it back to the device, etc.
But what I haven't gotten a definitive answer on is whether you can flash the iMate extended rom and then overwrite it at a later date with the original t-mobile extended rom, since the iMate one is locked or something. Genesis' method involves using a miniSD to create a raw image of a newly booted phone, GSM/OS/Extended rom and all, which you can keep somewhere safe incase you ever want to revert. Apparently, even after flashing the iMate rom with the locked Extended rom, he was capable of re-flashing the device with the original rom from the miniSD.
This is exactly what I am looking for. I want to switch to the iMate rom, and know the order all the cabs in the extended rom need to be installed for it to work properly, but I was afraid I could never revert to the OOB experience. This fixes that, and I will be ordering a 128mb card tonight.

I downloaded Tera Term from http://hp.vector.co.jp/authors/VA002416/teraterm.html is this the right one? It only has COM ports as options to communicate.
Can someone please provide a link to a terminal program I can download which works over USB?

Hi,
I followed your instructions for making a backup of my ROM to an SD Card. I have a small problem, I don't have a card reader for my PC, is there any way to get the ROM image onto my PC via my Wizard? Also since the Wizard doesn't think the MiniSD card exists anymore, is there anyway to raw write those 0's to the card from the Wizard.. perhaps using terraterm? Or have I just killed my MiniSD card and I'm going to have to buy a reader for my PC ?
Thanks!

zan5hin said:
Can someone please provide a link to a terminal program I can download which works over USB?
Click to expand...
Click to collapse
download this one: http://arisme.free.fr/hacks/binaries/TeraTermPro_WinCE_USB.zip
its in the bin folder of the zip.

koniosis said:
Hi,
I followed your instructions for making a backup of my ROM to an SD Card. I have a small problem, I don't have a card reader for my PC, is there any way to get the ROM image onto my PC via my Wizard? Also since the Wizard doesn't think the MiniSD card exists anymore, is there anyway to raw write those 0's to the card from the Wizard.. perhaps using terraterm? Or have I just killed my MiniSD card and I'm going to have to buy a reader for my PC ?
Thanks!
Click to expand...
Click to collapse
You need a card reader in your PC (or a friend's PC) - I do not know of a way to write it directly in the MDA.

Genesis3 said:
You need a card reader in your PC (or a friend's PC) - I do not know of a way to write it directly in the MDA.
Click to expand...
Click to collapse
Ok thanks, I've got one from a friend now, so all good I was looking at http://wiki.xda-developers.com/index.php?pagename=HimalayaBootloaderCommands to see if there were any bootloader commands for writing to sd card, but it appears you can only copy the ROM to the SD, besides, this is for a different phone anyway.

Ok I may have found something: http://wiki.xda-developers.com/index.php?pagename=XdaUtils/psdwrite.exe claims to be able to write raw to the SD card on a WinCE device... I'll investigate.

I'm currently reading the image raw from the MiniSD card using the command "psdread -1 0 0x0F140000 sd.img" using a 256MB MiniSD and it appears to be working, albit slowly. I'll keep you informed of whether I can succesfully recover my SD card using the writer after this read finishes.