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

i really screwed my xda!!! help!!! Please

I have rom 4.00.16 from the kitchen, and i wanted to upgrade the radio.
I had ver. 5.15 and i downloaded the radio upgrade from xda.ie (the first one that apeared in a google "xda radio upgrade" search.
Since it didn't tell me the radio version i was going to upgrade i installed it to the xda, and as soon it finished installed the xda self-soft-reseted and asked me for mim password, i have entered it and it started to do the upgrade by itself and got stuck at 10% for several minutes and frozee there.
I have already soft-reseted, hard-reseted, but without sucess my xda wont boot the OS, only displays the "not for sale" screen with the following info:
G
R
4.00.16
Click to expand...
Click to collapse
Help please!!!!
I dont have a sd card reader!!!!
Any other possible workarounds???
you can help me here or by my msn messenger: [email protected]
I'm stuck with out a mobile phone.

You have to have a card reader to fix it. There is no other way. You have to upgrade OS (using SD card method) and then try installing radio upgrade again.

I have already done that.
Now i can boot the xda (pressing the volume button) but as soon it starts making the upgrade it says it fails (at 1%)
The worst part is that the xda isn't charging (or it doesn't assume it's charging and that's why it doesn't continue with the upgrade).
I've already tried to copy the gsm soft from a working qtek 1010 using the bootloader gsm to sd method, but no sucess since nothing happens (i insert the serial cable on the xda but mtty.exe doesn't react or recognize the xda - any possibel mistake i'm making here???).
Help most wanted, since i can't afford at this time to pay for a motherboard replacement - this is my only solution according to the qtek technical support here in Portugal (and hey, thanks a lot for your time )
Anyone can please suggest any possible solution?!?!?!?
You can feel free to use my msn: [email protected] to contact me...
I will pass some licenced software to the person that can help me solving my problem!!!!
TIA

Maybe this thread can give you any help :?: :?: http://www.xda-developers.com/forum/viewtopic.php?t=2489

Why it tries to run upgrade upon boot? When I flashed my OS there were no files under start up folder to run upgrade executable. I suggest boot your XDA and remove everything from Startup folder

My main problem is that i can't get the xda to charge (or at least assume it's charging the led is always off).
Isn't there a way to crack the rsu to avoid him to check battery status an carry on with the upgrade (cracker's welcomed )??
I think that would solve my problem
I can boot the OS by pressing the volume key (already changed to several OS's to see if one coulde handle with the charging problem.)
And i can sync with my desktop.
But i cant upgrade via programme A.
Programme B installs on the xda but when it reboot's it stop's at 1%
I now have a original o2 3.17.3 and my bootloader is 5.15
I've seen that in the bootloader we have the chance to backup the gsm rom to a SD card! But how to restore it??? If anyone can make such a backup and has a way to restore it can you please share it with me???
As i said i don't have the money to exchange my motherboard (that's the answer from QTEK'S support i've got (great guys thank's again for your time)
I've arranged a conmceptronics sd/mmc/ms/sm/etc.../etc... card reader.
So if one finds a way of backing up the gsm rom, copy it to the sd and zip it using the rom tools here available could you please send it to me???
Thanx in advance

Another thing:
with this rom installed if i go to backlight settings it wont turn off the backlight.

Hi,
I need urgent help
Qtek Support here in Portugal gave me a qtek unit for a few days to see if i find a way to recover mine without replacing the motherboard.
I have the following material:
-1 working qtek 1010
-1 damaged xda
-usb cradle
-serial cable
-sd card reader
-1 128mb twinmus sd card
-charger
-etc...
What can i do to solve my problem
Please help
TIA

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.

Unlock SIM (Pocket PC Phone Edition)

Hey Guys,
My friend gave me a pocket pc with phone edition. When I tried to insert my sim card it asked me to the unlock code. My friend used this mobile for T-Mobile sim card in US.
Here is the ROM Versino: 4.01.16 ENG
ROM Date: 02/04/04
Radio Version: 6.25.02
Protocol Version: 324e4
After typing my PIN code it asks me to unlok the sim.
What can I do to resolve this problem
Thanks,
bm_t

Try the XDA unlock tool. You can find it on the website.
I have unlocked tmobile using that tool. However if it gives you problems unlocking.... I would suggest installing the xda rom and then try.
I am going to unlock a new Tmobile on tuesday. If this does not work you can get in touch with me on any chat and I will walk you through the process.
lemme know if you need anymore help.
Cheers!
Diki :lol:

Thanks Diki for your reply.
I have tried XDA Unlock and XDA2Unlock but failed.
When I tried XDA2Unlock it reports some error like COM2 0X..... (Hex #)
You have seen my ROM version and Radio version. How do i install new xda rom .
I only have the USB cable. Do I need a serial cable?
thanks

As much as i know, it will not work for you to unlock your device.
xda2unlock is only for the second Version of XDA (MDA II, MDA II,...), so you have to use the xdaunlock tool.
there are several postingsa, that unlocking will fail with your radioversion.
Maybe they have changed the code in this version.
There is a guy (cgigate) that promise he is able to repair and unlock all devices, but personal i don't believe this.
i believe changing ROM will not change anything. But you can try it. Look for the XDA deelopsers special ROM 1.2 or use the 3.17.03 ROM and the unlock tool.
But flashing a device could be dangerous.
Changing the radioversion is also possible, but the risc to end ata paperweight is very high...
Stefan

Hello LumpiStefan,
Where do I found 3.17.03 ROM. I have tried in your site(Romkitchen) but I couldn't able to download.
http://lumpistefan.dynsdns.org
After selecting the ROM and some additional softwares, I clicked the 'Build Rom Now' Button but nothing comes.
Can you help me with this?
thanks
bm_t

bm_t said:
Where do I found 3.17.03 ROM. I have tried in your site(Romkitchen) but I couldn't able to download.
http://lumpistefan.dynsdns.org
After selecting the ROM and some additional softwares, I clicked the 'Build Rom Now' Button but nothing comes.
Click to expand...
Click to collapse
Cooking process works well for me.
Maybe you have to wait a few minutes more.
Cooking process can be up until 5 minutes.....
Otherwise try again the Build Rom now button....
HTH
Stefan

Hello LumpiStefan,
I have tried serveral times but I couldn't able to download the ROM.
Do I have to register or download some other application to download your ROM.
Here is what I did to download the ROM
After Entering ur site LumpiStefan, http://lumpistefan.dynsdns.org
I clicked PPC 2002 and select 3.17.03 with XDA developers (Default ).
and clicked 'Build Rom Now' button.
When I clicked 'Build Rom Now' button, the only thing that changes is the graphs (right hand side of the page). I have tried many times but only the graphs changes.
Did I miss something (some procedures or .....)
thank you for ur time

After clicking cook rom you should have the option to specify where to download it.

Hello,
I have 128 kbps line but couldn't able to download the rom for the site.
http://lumpistefan.dyndns.org/
It doesn't respond the site except changing the cpu ... graphs
Is there any other site to download 3.17.03 Rom for XDA-I.
thanks

bm_t said:
I have 128 kbps line but couldn't able to download the rom for the site.
http://lumpistefan.dyndns.org/
It doesn't respond the site except changing the cpu ... graphs
Is there any other site to download 3.17.03 Rom for XDA-I.
Click to expand...
Click to collapse
You can try http://xda.weblink.net or use http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe to download the xda developers ROM based on 3.17.03 including the unlock tool....
I think you're the first guy that has problem to download a rom from the kitchen.
What for browser are you using? Have you ever tried another ROM?
HTH
Stefan

Hi LumpiStefan,
Thanks for ur reply.
I have checked both sites (i.e http://lumpistefan.dyndns.org/ and http://xda.weblink.net)
I have tried also another rom but the same problme. I have tried to download the rom from Linux and win XP pc.
I have aslo downloaded http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
but when I executed this file from my win XP machine ( I have connected my XDA through USB cable and installed ActiveSync 3.7.1) it reports error (something like Unable to find the XDA Please connect Serial/USB cable)
I'm really really stuck with this phone
thanks

it seems that you don't followed the correct procedure.
This link it's a wizard and could help you: http://wiki.xda-developers.com/wiki/UnlockWiz

Hello Folks,
I have seen a post in form.xda-develpers.com that this file http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
will not work because my phone (i.e PC2003) (the adaptROM is not compatible with PC2003)
He said the only option to Unlock the SIM is only using this xdarit.exe application. Since my SD is 8 MB, I can't load the ROM with this space.
As far as I have seen the situation, my only option is getting the serial cable.
Do you have any suggestions?
Thanks

bm_t said:
As far as I have seen the situation, my only option is getting the serial cable.Thanks
Click to expand...
Click to collapse
Get the serial cable.

SIM Lock
Hi,
Every time I run "XDA-developers-SER-v12.exe" I get a message, error getting data, and then the program close.
plz advise. thanks

'error getting data'
I had the same error. I read somewhere on one of these posts that
there was some capatibility between Programme A.exe and Activesync 3.7.1.
Apparently you could downgrade your activesync version or use XDATools to push the nk.nbf file down to an SD card and flash from there. Use winzip or something else to extract all the files in the SER installation exec. In the English folder you'll find the NBF file to use.
In XDATools put this as the Source, target is the SD card in the device. Go to bootloader utilities (power+soft reset and maybe press contacts) and depending on your bootloader version it may detect you have a flash image on your SD card. Follow the instructions on the pda to flash the rom.

Hi rhodwyn,
Thank you for your support, but still I cannot downgrade my "BootLoader" to "5.15" with every boot I'm geeting "5.22" even after loading the spocial edition ROM.
Also, I cannot find (XDArit & Wallaby bootloader version 5.15 files) in the neet.
Please advice.
Thanks.

Hi ALL,
I did unlock (SIM LOCK) my phon.
Thanks you all for help & support.