Database Users

ROM Backup to MMC - Problem

I had an XDA Asia version. Bootloader version 5.17. My PC has WinXP SP1.
I want to backup my original ROM before I can load it with other intersting stuff from this excellent XDA developper site. My steps:
1. I used XDARit and write the wallaby-patch-tool.nb2 to a MMC card.
2. I put it in my XDA and do a bootloader reset. My XDA lead me to the patch menu as expected.
3. I insert another MMC Card (64MB) and dump the CE ROM to the card.
4. I inserted the MMC Card back to the card reader and click [READ FROM SD CARD] button of XDArit. XDArit told me that "in correct signature" and DID NOT write the ROM content from the MMC card to my harddisk file.
5. I looked at the XDArit window showing the card bytes and did not see "HTC$WALLABY", rather it show something "FAT". Seems that XDA DID NOT write anything to the card. But also seemed that XDA DID write something to the card as it become unformatted (can not be read by Windows Explorer, whilst before it ca read the card folders and files).
Can someone tell me somehint to back up my ROM. Because I do not dare to upgrade my XDA without backing up my original ROM.
I read thru this forum and seemed that the possible problems are:
- Incompatible driver of WinXP SP1 => XDArit can not read properly?
- Some new trick of the 5.17 bootloader with the rom patch tool can not "cheat"?
- USB 2.0 problem (but my PC used USB 1.1)
- XDArit problem (but I tried both old and new XDArit with no success)
It seems that the XDA did write something to the MMC card but XDArit can not see these.
Please someone help. :lol:
I really want to play my ROM with lot of new things on this site, but dare not until I can back up and restore my current original ROM.
Quan
PS. I used "Flash Mate" card reader (4 in 1).

Please any one advise your solutions... I really want to play with my ROM, but before I can back it up.
Quan

Dear Quan,
More detail, can you contact to me
I have been using XDA for 11 months now together Samsung i700,
Used the same OS-Windows XP 1sp, Office 2003 beta in IBM Netvista 2.4
Upgraded Diff. ROM - this moment "WM -cooked ROM 2003" :wink:
[email protected]
Regards,
Hanoi

Hi Van,
Glad to see you are from Vietnam also. I have XDA just for 15 days. I love it very much. I also had Nokia 9210, but now I throw it somewhere in my home and did not even bother to find where it is.
As noted, I could not backup my current ROM. Something wrong in the middle but I did not know why. I have just tried last night on Win2000... Unsuccessfully. The symptom is the same.
- My XDA backed-up its ROM to the card and message me that "back up successfully".
- But when I inserted the card to the card reader and use XDArit, it seems that the card was not written by the XDA as I always saw something "FAT" in the window of XDArit, not something "HTC$WALLABY..." as described in this forum for an XDA image file signature.
- That's why when I choosed "read from SD card", XDArit always tell me that "incorrect signature" and stop.
- For sure that XDA did write something to the card because after XDA writing, I could not read the card thru the OS Explorer anymore (unless I re-format it).
I have tried on WinXP SP1, on Win2000 Pro but... the same symptom.
Tomorrow I will buy a new card reader and try again. If not successful, I will buy a new SD card and try and try and try... again until I can back up my ROM
I need to back it up before I can try many other interesting stuffs from this forum. First time I saw such an open-minded forum with many high-techies who willing to help like this forum.
Share me some hints please. I can not wait longer. :evil:
Quan

Need to check:
Which version Active sync (best 3.7)
Which version XDARit (best old version)
Downgrade Boot loader version 5.17 to 5.15 better for bootloader SD method
SD Card better than MMC
Windows XP better than 98 versions
I think that
The easy way to upgrade your XDA-ROM: run .EXE file on your PC synch with your XDA
http://www.o2.co.uk/productsservices/xda/romupgradedownload/0,,170,00.html
xda System Software Upgrade
To install the upgrade (ppc2002) on your xda:
1. Download and read the upgrade instructions (528KB)
2. Download the Radio Stack Upgrade v4.21 (1.54MB)
3. Download the Radio Unit Upgrade v3.17.03 (14.9MB)
The best Option:
From JEFF you can download
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Steps:
1. Full recharged battery
2. Back up your data
3. Soft reset your XDA
4. Sync to your PC
5. Plug your AC adaptor to Cradle
6. Run ROM.EXE in your PC
7. Total time about 5 minutes
8. Completed
9. Unplug your XDA from Cradle
10. Hardreset (2 times- interval 1 minute)
I can read more detail in your PC on the process upgraded
Do not be afraid, you can do it!
Good luck!

Hi Van,
To reply:
- I am using ActiveSync 3.7.
- Can you send me XDArit old version. By email to [email protected]
- Yes, I tried both SD and MMC. But no results.
- Never use Win98.
My questions:
- How can I get bootloader 5.15 image (.nb0 file, right?) to downgrade
- Or the EXE upgrade from O2 UK site include this 5.15 bootloader?
- I have also made 3.17 ROM from Jeff's kitchen. Do you know that this Jeff EXE include the 5.15 bootloader?
- Your advice is to upgrade using EXE from O2 UK? Or from Jeff's kitchen?
- Have you ever tried backup/upgrade using the bootlader way, any experience? Please share.
I am just afraid I did something wrong and can not revert my XDA back to the original status!!! A bit scared.
BTW your XDA original bootloader is 5.17 or 5.15? If 5.17 then please tell me how you downgrade it from 5.17 to 5.15?
Thanks very much for your helps
Quan

@ Quan
Fist time upgraded ROM I have the same feeling
For PPC 2002 no problem (6 times upgraded)
For WM 2003 Test ROM 4.00.01 some bugs- my XDA had loosed phone function 3 days :evil: but in the end everything is OK (advice from this forum)
http://www.o2.co.uk/productsservices/xda/romupgradedownload/0,,170,00.html
Try it and you can say so easy! :lol:
Anyway you can call me before...

Can someone confirm XDAtools does not work with WM2003

I am trying to test out XDAtools and using the WM2003 AT&T rom but keep encountering problems trying to load my rom via programmeA I have had some help from others (see below) but it seems that XDAtools cannot manipulate WM2003? Can this be confirmed and if so I'll abandon this test.
Thank you Cgigate and ebswift maybe this is why I am encountering problems with my download and restore of my ROM. I inadvertently choose a WM2003 AT&T rom to practice with. Maybe I should have chosen a PPC 2002 ROM to test??
I thought I had a problem with XDAtools and that I did not have all the correct links/files in place. Maybe I should dump my ROM and try restoring a PPC2002 and then re try my test. Thanks again guys.

it worked for me
For your info, I used XDATools and Program A to burn AT&T latest ROM. I then flashed back to XDA Developer's SE ROM in order to unlock my phone. When that was done, I reflashed the AT&T ROM. All without hasle.

Did you use bootloader or ProgrammeA ?
Thanks viERJA when you say flash do you mean copied to the SD/MMC card and used the bootloader to load ??

i had 4.00.05 before and used XDAtools to upgrade to 4.01.00 without problems.

well since if you copy the rom to a sdcard and upgrade the rom using the bootloader then xdatools cant really be incopatible with mw2003 since it's the bootloader which do the updating and xdatools does the same thing to the sdcard if you are updating to 2002 or 2003 to and from 2002 and 2003

Good point Rudegar
Good point Rudegar, therefore XDAtools is not being used in the context of elimination of the SD/MMC method. John

Burning ROM - phone not working

Hi, I'm hoping to get some help with cooking and burning ROMs to my o2 XDA.
My original product specs are:
ROM Version: 3.20.06 ENG
Radio version: 4.21.01
I cooked and then downloaded 4.01.00 ENG from Lumpi Stefan's site, then ran the rom.exe file that it produced for me. Everything worked fine, and then I rebooted my XDA. Upon first boot the phone appeared to work, but after performing a soft-reset because the XDA froze, all of the phone functionality appears to be not working.
When I do a hard-reset I get: Wallaby Bootloader v6.22 - GSM OK which I think looks good as far as the phone functionality is concerned. Looks like it's the OS that's on the XDA which is causing the phone difficulties.
I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started!
I don't have an SD card, and am in dire straits about getting my phone to work. Is it possible at all to get this to work, or perhaps to go back to my original ROM (I backed it up to orig.nb1) using XDAtools. Anytime I try to burn the .nb1 file back to my XDA it fails. Or is the ONLY way to get an SD card and use the Bootloader technique? I even tried downloading the 3.17.03 ROM upgrade directly from the o2 sitebut it fails.
Any help will be GREATLY appreciated.
Thank you.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![/qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![\qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

Thanks, I will try. ActiveSync still works...
I notice you are running the same ROM version as me - sis your radio still work?

Can you verify that I am trying to Flash the ROM correctly?
1. Confirm that I have orig.nb1 - yes, it's there - backup of original ROM before I started this whole dilemma.
2. Ensure that XDA is Activesync'd - yes, as "Pocket_PC" - all working okay.
3. Right click on orig.nb1 and select "burn"
4. OSImageTool.exe then pops up and copies orig.nb1 to Programme A.
5. A DOS box then appears saying "ERROR: GetConnectionType - A
ote host. error getting connectiontype".
6. Programme A then runs and after pressing "next" a couple of times, I get an error - "Error 011: Cannot execute the remote communication program. Pleace make sure that the USB cable is properly connected."
And that's basically it.
I have tried different variances of this, but all without success.
Help!
BTW, I'm logged in to MSN Messenger now, could you let me know when you're online - or anyone else, for that matter. My address is [email protected]

This message means that the current ROM in your XDA can't be flashed through Program A ... not a big issue, for unknown reason it happened with me few times ... but now you have to use SD card to flash your ROM.

Here is an update...
I have played around some more with the XDA with no success. I have now bought a 64MB SD card and am unsure as to how the ROM image on my PC gets onto the SD card. This is how I have been doing it:
1) Insert SD card into XDA
2) Place XDA into cradle
3) XDA then ActiveSync’s to the PC
4) Run OSImageTool.exe and select the following –
a. Source: “C:\Documents and Settings\Paul\Desktop\orig.nb1”
b. Destination: “XDA SD card slot – unknown size”
5) Then I press “copy” and I see the progress bar go across to 100%. After this appears to finish, the program just sits there not telling me it’s finished. I assume that it’s all okay and I then close the program
6) Take XDA off cradle and hold power button down whilst doing a warm-reset
7) The following appears: “Wallaby Bootloader v6.22 – GSM OK” – nothing else happens, and from what I have read it is supposed to ask if I want to perform a ROM upgrade. However, I can get into the diagnostic and flash tools by pressing the action button etc, but nothing is in there to upgrade the ROM.
Does the fact the OSImageTool destination says “XDA SD card slot – unknown size” matter? I’m assuming not because when I have transferred the ROM using the above steps, the XDA asks if I want to format the card; meaning that the transfer worked okay. Do I have to have an SD card reader/writer on my PC to get the ROM onto the SD card?
I have read a little about a Bootloader patch – do I need to run this, and how do I get it onto the XDA – using the same method?
I would be very appreciative of any help that can fix this, as all I want to do is get my three-day old XDA working again!
Any other comments and help in relation to solving this hair-challenging issue would be great!
Thanks,
Paul…

Ok ... from what you wrote it seems your doing it correctly. However, I have doubts on the file orig.nb1 you are using ... maybe it wasn't copied properly.
Try to cook any ROM (TMO 4.01.00 is good) at Stefan kitchen and you can cook it as .nbf or EXE then extract the .nbf file using winzip or winrar.
Follow the same steps and let me know.
Good luck ...

Is bootloader v6.222 okay - will it allow me to overwrite my current ROM with this new ROM that you are suggesting? I have read that I may have to downgrade my bootloader to do the SD ROM writing thing.

I can't confirm that my self ... I used SD with 5.17 and 6.22 without problems but maybe it's my luck
Cook the 4.01.00 as EXE and try it as is or extract the .nbf file and use the SD method.

Okay I'll give that a go now... Will let you know how I go...

Nope - didn't work. I'm not getting a screen in the bootloader to update the ROM via SD - if I press the action button I get into dignostics...
Is this a bootloader issue, and if so, how do I downgrade?

Also just tried the following:
C:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
And got the following error message:
Unable to find flash info offset, cannot disable bootloader writeprotect
Any ideas?

I don't get it ... you cooked and downloaded and tried a new nbf file for TMO 4.01.00 in less than 15 minutes ??!!!!
what is the nbf file size ??

Yes, I used Winzip to extract NK.nbf. It is 31,745kb.
I am now cooking on Lumpi's site a zipped NK.nbf file and will try that too...

T-Mobile Rom.... Can't do anything else... Help

Since updating to the T-Mobile Rom for my XDA, nearly everythiung has gone wrong.
And when I tried to downgrade it.... Nothing happens.
I used to use a modified Program A to upload it to my phone but it continues to say that the USB devide gets remotely stopped. the only thing that I can think is that my phone is cancelling the upgrade/downgrade.
I have also tried using a copy of the XDATools program to try and:
Upload another Rom.
Copy the rom to an SD card so I can use the bootloader method.
Change the Bootloader so I can use the SD card method.
None of there are working.
Help :-(
I really want to go back to the ATT rom, it might have the annoying thing with the sound but at least it doesn't mess up as much, doesn't format my SD/MMC cards and lets the alarms actually work for me.

if i'm not wrong, it seems you upgraded using the TMO exe file which updated both ROM & RSU.
check ur boot loader version, if it's 5.22 or higher, i think you need to dowgrade to 5.15 ... use the exe file that comes with the XDAtools in the binaries directory .. its name is fixbootloader.exe .. it should update ur boot loader to 5.15 by which you can use XDAtools or the SD method.

Tried that. I do have XDA tools on my machine and used that program but my CDA still has the bootleader of 5.22
And both of my machines don't like trying to update my XDA :-(
This Rom is the most annoying one I have tried mainly becaise now I can't go back to even my original one that I backed from the XDA when I got it.
Am I stuck with this ROM?

omg, i think i am having the same problem. In my case, since ive installed the new rom, i cannot sync with activesync, well very slow anyway. Activesync on my pc stops responding for a while and suddenly it says connected. However when i then run the executable created by the kitchen, it just flashes a command line window for a second.
When I try XDA-toolz with an nbf file, i get the following message:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
Click to expand...
Click to collapse
Please someone help, because i am really stuck now.

I checked, my bootloader is 5.14, so that shouldnt be the problem, perhaps i need to reinstall activesync, or perhaps lumpistefans kitchen cooks up bad roms. :?:

Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!

Biso007 said:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Click to expand...
Click to collapse
I dont understand how i can have a wrong rsu? I didnt update it , as far as i know , i just updated the pda part. I only saw programme A.
Activesync does recognise my xda, because i can synchronize and explore my device. It does however take a long time before activesync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling activesync, this didnt help.

prowling said:
ActiveSync does recognise my XDA, because i can synchronize and explore my device. It does however take a long time before ActiveSync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling ActiveSync, this didnt help.
Click to expand...
Click to collapse
If there is something wrong with the RSU it will defeinitly slow the USB performance, not neceassary by wrong RSU flashing ... otherwise, check the pins of your cradle or the 22-pin connector of the XDA ... maybe one or more pins are bent or weared.

Tried upgrading the radiop stack and although the reception is slightly better... It still won't let me upload,
and its a new cable too :-(
Oh well looks like I am stuck with it.

Another way to upgrade firmware
Are there other ways to upgrade the bootloader from SD card from within the device or even to upgrade the OS from within the phone itself?
You know... as a last alternative?

You can use SD reader/writer from the PC using XDAtools ... once the .nbf file is on the SD card, use the normal SD flashing method.
Or you can use another XDA device from a friend to copy the file to your SD card

I am having the same problem. I have TMO 4.01.16 and since I installed I can't down/upgrade my ROM through EXE or XDA tools, it says my device isn't connected, but I can still connect with Active Sync and all that jazz

ha ha
I can fix all your problems!

How?

Finally got it to work, Although it was a little bit of effort to do so.
I went back to the kitchen and downloaded a NB1 cooked rom with the "B" Signature. Then I basically ran the TMobile Setup again...
Once the setup files were on my computer I overwrote their .NB1 file with the one I just cooked.
But.... I forgot to change the file for the Radio Stack.
The machine worked except for the phone and as something is still stopping me. *it was my first reboot* It wouldn't let me use a new radio stack.
Ended up that i kept on going in to the bootloader and eventually turned my radio off altoghether before trying an update.
Now I am back to a decent rom... (Cooked and modded version of the ATT Wireless rom) and I am almost really happy.
Now to figure out how to stop the annoying sounds starting off really low.
But til then... I'm 90% happy

Thespus2002 said:
How?
Click to expand...
Click to collapse
Use the Sd Method flashing!!
Tmobile roms won't let you upgrade from the usb, here's the link and it will guide you how to flash your device from the SD good luck
http://forum.xda-developers.com/viewtopic.php?t=3274

The way I described.. I had to use the USB method.
my current bootloader (6.22) will not allow me to boot from an SD card.
And XDATools will not allow me to downgrade it... Yet

on ur PC at \xdatools\binaries run this command: pnewbootloader.exe bootloader_5_15.nb0

Wish it was that easy. The phone still appears to be locked in the rom so I can't update the Bootloader. I keep getting a message that says.
Unable to flash in to offset, cannotg disable bootloader write protect.

Using XDATOOLS on SX56

To unlock my device I installed the XDA Special Edition ROM on my SX56 by running the executable. My device is a PW10B1 (printed on the back of the device). Unfortunately, after installing the XDA ROM, my device information says the device is a PW10A1. Now this seems to be causing a problem. I want to get WM 2003 back on the device but running the AUTO update tool (Executable with the Wm20003 update) errors out saying that my device is a PW10A1 and not a PW10B1. First signs of panic.. Ok. So I decided to search for the original PPC2002 ROM for At&T and I found it. But its a .nbf file. So I downloaded XDATools hoping to write the image to the device memory or to the SD Card. However I cant seem to access the device from the Destination Browse Button of the XDATools App. The browse dialog that comes up does not include the "Mobile Device" listed under "My Computer". In my windows explorer I can see it listed. How do I get XDATools to wite it to the device rom directly?
Any help would be appreciated

If I cannot flash the XDA directly using XDAtools, are there some PPC 2002 ROM Executable Updates (At&T 2002) available that will bring my SX56 back to PW10B1?

Try using adaptrom.....
http://wiki.xda-developers.com/wiki/adaptROM
HTH
Stefan

Adaptrom will let me put the Wm2003 update on the phone but the problem is, it will leave the phone as a PW10A1 and not convert it to a PW10B1...I need to convert the ROM back to its original state.. I will try to put the original Image on an SD Card and see if I can boot off that..