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

PW10B1's ID as PW10A1

For some odd reason my T-Mobile PW10B1 (as labeled on the back of the device) is identified as PW10A1 in Device Information. I never paid any attention to that, but I got an error 012 when trying to upgrade to T-Mobile W2003. I'm currently running 3.17.03 (the XDA-developers Special Edition ROM v1.2), so perhaps prior upgrade affected the stock ID change from B to A.
How do I change it back to PW10B1, or how do I go about installing W2003 on my messed up device.
Thanks,
Marcin

Marcin,
i have the same with my AT&T. however i'm able to upgrade it to WM2003. the only thing confusing me that after upgrade it is stuck on splash screen, no further load. i tried different methods and versions... no results...
if you find the answer, please let me know

I can fix the problem!

Marcin, all you need to do is get an sd card and reader writer, you can then do the sd method of flashing which bypasses version checking. You will need xdatools also, just pass your mouse over xdatools link and you can download it from there.

very helpful
Nice advice, cgigate...that was very helpful...

cruisin,
I am in the same situation as marcin.
Please confirm my understandingof the bootloading from SD:
1. Using the SD+card reader, I copy the W2003 NK.NBF file to the SD.
2. Insert the SD card into the XDA
3. Goto the bootloader mode (power + soft reset) and press the middle of the rocker key.
4. After the ex counter increases.. at the end, press hard reset.
5. After 60 sec press hard reset again
If this is correct then why do I need the XDATools for?

Copying the file to sd will not work, it needs to be in a special format for the xda to boot the rom burning procedure, you will need xdatools. At the end you push the unscrewed end of the stylus into the tiny hole bottome right of xda, then again after 60 seconds and you should have a working system.

cruisin-thru
Thanks cruisin-thru.
I want to be very clear before starting the upgrade, so..Do I use the OSImageTool to special format for the XDA to boot from the SD?
Thanks again for your patience!
BTW: I did steps 1 to 4 of "unlock Wiz/Wallaby/SER/Backup and
now I (like marcin, have my T-Mobile PW10B1 identified as
PW10A1). I have yet to do the steps 5, 6 and 7. If I do these
steps. Will the identification be corrected?

so..Do I use the OSImageTool to special format for the XDA to boot from the SD?
Click to expand...
Click to collapse
yes after osimagetool have copied the rom to the sdcard the card should be unreadble to anything but the xda's bootloader

Upgrade to W2003
It is my great pleasure to have great and helpful people who advised and suported me in my XDA fiddling adventures. I have now upgraded to W2003 and unlock my phone to use any provider I wish.
Thanks to all!
Melody

Help me please !!
I have a XDA PW10A1 without the instalation cd-rom where do i find the drivers for my XDA ....... please help me !!!

Valikos, the only installation you should need is activesync which is freely downloadable from the microsoft web page.

Yes but!
If i have Win98 SE my computer do not see my xda , there are not drivers for 98 ? ....

Just make sure you have the latest ActiveSync version which is 3.7.1 ... sometimes uninstall then re-install solves this issue.

ok .. another question .... i have all my contacts in to a motorola accompli 008 and like the xda i don't have the instalation cd and no drivers , where do i find the drivers for this one , because i have more that 200 contacts in this one and i wold like to transfer all contacts in the xda

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.

ROMs and getting it onto the PPC

OK I have the tmo PPC its already got 2003 on it and I know the loader is 5.15, other info that might be needed.
ROM 4.01.16 ENG
Radio 6.25.02
OK I want to get my own cooked ROM onto this, I know I know use the SD card method, well I don't have one and after getting this thing can't get one for a while either. I have the cradle that it comes with and have put software into etc, I have tried some unlock ROM software to find it didn't work etc etc. after cooking ROM and running it it tells me in a DOS window:
Error getconntiontype - An Existing connecitonwas forcibly closed by the remote host.
error getting connectiontype
so basicly I need to find a way to get this into my PPC via activesync or something. sorry for bad post a little tired but I think people will understand and be able to help me or tell me I need SD card and wait until I get one.

I think you can use xdatools to flash the rom direct from xda memory, choose the nbf file as source then choose the xda device memory as destination from the drop down box in destination section.

OK tried that but can't access the PPC with xdatools so that won't work. thats for trying though.

TMO ROMs are known to resist exe flashing ... use the SD method and you are lucky to have the boo loader 5.15

Well glad to know that my boot loader is a good one, now to find a SD card I can borrow to do this with, should I use a 32 or 64 or does it really matter as long as it holds the file.

64 megabytes is needed really, I have had a problem with 32 meg, it looks like it is programmed but when i flash it there is always a problem.

macgyver33 talked about having a 2003 version. Can anyone tell me where to get it? I mean european one (900-1800 MHz). Or at least the PDA part of it? And yet haven't found quiet an exact explanation of "SD method" - any suggestions? Thanx a lot!

Bootloader v.5.17 locked
BL v.5.17 + TMO ROM. I am not able to downgrade the bootloader or change ROM.
I've tried using:
Cooked ROM.EXE - No way
(Error: GetConnectionType - An existing connection was forcibly closed by the remote host. Error getting connectiontype)
XDA OS Image Tool - No way
(Error: Same as above)
ITSTools - pnewbootloader - No way
(Error: Unable to find flash info offset, cannot disable bootloader writeprotect)
SD Method - No way
In bootloader mode (soft-reset while pressing on/off button), I have no options: Even with an SD card with OS image inside, there's no way to start ROM download as there is no option to choose...
Any idea?
Thx

Check this thread

Thanks Biso007.
No way. My XDA doesn't load the bootloader in a proper way:
1. Inserted th SD card in his slot
2. Answered "No" to format the card
3. Soft-reset while pressing on/off button (so to enter in bootloader mode)
4. Display turns off
5. No Wallaby Bootloader screen, so no action to take...
6. Wait... Nothing.
7. I've also tried to press the "Action" button so to start the SD downloading... Nothing
8. Wait... Nothing.
6. It needs another soft-reset to exit this state (a not working bootloader mode, I suppose)
7. It turns on "normally".
Any further idea? :-(
Thanks

if I'm not wrong, I couldn't see that you ran the 5.17 patch first ... without it your device will never detect the SD file ... chech the thread again

Stuck on bootloader menu after error upgrading ROM

Help,
Is there a way to get the OS and boot img for my o2 XDA to put on my SD card so i can recover it?
I'm stuck on the boot-loader screen (version 5.22) i can not use active sync as it comes up as unrecognized device, im at my wits end, i just want to get my phone working again. is there any place i can get the O2 ROM file from? or anything that can be done, or do i have a useless brick now?
i tried upgrading with the developers ROM using the auto install, it got to the "it will take 5 mins to upgrade" screen then active sync lost connection, there was nothing showing in the progress bar, when i tried to restart, active sync could not connect. now im stuck with the boot-loader menu after a soft reset.

Sorry for the double post,
Right sorted the problem out, got a cooked ROM from a different site as no link i clicked on here was still active.
I found out that if you Format the SD card to Fat32 when in bootloader it doesn't recognize the ROM, so a format to just FAT under windows XP sorted it out, and now I'm back up and running again, though now i cant get my phone unlocked to Vodafone as the XDAunlock returns "error getting code" message. here are my Device info
Rom version 3.17.03
Radio version 4.21.X1
Protcal version 32S54

problem resolved by updating the Radio stack to 6.24 (placing the files onto the device and upgrading from there) once that had done, i had no signal, so downgraded it back to 4.21 and now I'm fully functional

Where did you get the ROM?
I have a similar problem with an XDA which failed whilst being flashed via active sync and now will not start apart from via bootloader. Where did you get the ROM that you mention please?
Thanks
Geezer

use this ROM from http://www.romkitchen.de/ choose one that u will use to cook, PC2002 or WM2003/SE, (WM2003SE cannot use SD Card, only can use activesyn) then downgrade bootloader from v5.22 to v5.15,
using MMC (flash SD) continue to special rom 1.2, Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button if when you get to the bootloader screen you see nothing more than some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader. Bring up XDArit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'Wallaby' in the hex codes at the bottom of the XDArit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT). Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.' Type 'pnewbootflash_40116 nbl515.nb0' to write the Wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0' you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
for the complete, read this web :
http://www.romkitchen.de/
http://www.romkitchen.de/tools/
http://www.romkitchen.de/tools/manual_unlock.htm
*read careffuly and try it, you can read my post, almost similiar problem but i can solve it by read one by one,hehehhe.. never give-up, ok ^_^V

any help with magician rom?

OK I found this thread and this is what I need to do but I don't follow any of this. what is the ROm image and how do I cook? I'm totally lost and My phone is wrecked or bricked as you say???