Database Users

Flashing ROMs is dangerous !!!

There's two type of ROM upgrades: Operating System ROM upgrades and Radio Stack Upgrades.
Radio Stack Upgrades:
Radio Stack upgrades are distributed by the devices resellers. They come in packages with names that may or may not include "Programme B" or "RSU", and they are usually about 2 MB in size. Version numbers are a mess, and lower version numbers do not mean earlier versions. There's at least three different paths of version numbering out there, and the version number on the file doesn't always match the version number displayed at boot and by 'Device Information'.
The official Radio Stack Upgrade process is a mess. We've seen way too many people wreck their devices doing nothing weird or strange. Our advice regarding Radio Stack upgrades is to get them from your own device provider (so you know it's for you type of device: 900/1800 or 900/1900 MHz), and to only upgrade if you know the upgrade will fix known issues that are bothering you.
Operating System Upgrades:
Operating System upgrades are distributed by the resellers in packages whose names may contain "Programme A" or "RUU" (to confuse things, RUU stands for "Radio Unit Upgrade", even though they do not upgrade the Radio part but the PDA part). Operating System upgrades are usually 15 MB in size, and unless you use our utility 'adaptROM', they will only install on phones sold by specific resellers in specific markets.
In this community, the OS is sometimes also distributed as .nb1 file, for use with our XDArit tool. These files are often zipped to about 15 MB, uncompressed they are 32MB (well: 32 MB minus 256 kB actually).
We've seen a number of people doing terrible things to their devices by upgrading their OS ROMs. Here's what we've seen:
- It appears someone is distributing an EXE file for the PPC2003 ROM that contains a part of the OS in the spot where the bootloader needs to be. People that use this EXE to upgrade to 2003 may experience problems immediately or later on, possible making their device unusable.
- We've observed our XDArit tool in the hands of people that should not be using it. If you don't know what a DOS box is, or think you can rename .nb1 files to .nb0, or if you generally do not feel technically proficient, do not use XDArit. It's as simple as that.
(We also blame ourselves for this: XDArit is very counter-intuitive in some parts, and is long-due for an overhaul....)
- Apart from the above, there seem to be problems for people getting back from PPC2003 to earlier versions of the OS. We've been busy doing other things, and we haven't really researched this yet.
- It seems the exe files Jeff makes are OK, and if they aren't, people would know pretty quickly. We advise against running exe-files from others until we've found what causes this 'bootloader mangling' we've observed.

Thanks for your warnings. I just checked my device information. It reads rom version 3;14.06 ENG, Rom date 10/01/02, Radio Version T313. Being not technical at all. Your advice is not to upgrade the Rom or de radio version.
But that leaves me with some problems. F.i. when I try to synchronize with Outlook on my pc. I keep losing mails. The only mails being synchronized at all are those from my inbox. A series of attachments cannot be converted and there is no way to know which mails they are in. I was also hoping that a rom-update would solve my constant memory-lack.
Are there any other solutions?

Upgrade Fails
We have been upgrading some ATEK's with success, but we have two that don't want to upgrade. The message is:
"Can not open COM/USB port...." \\Can someine help...

Re: Upgrade Fails
scalci said:
We have been upgrading some ATEK's with success, but we have two that don't want to upgrade. The message is:
"Can not open COM/USB port...." \\Can someine help...
Click to expand...
Click to collapse
:wink: it's same problem that i have but the slution is download the XDA-dev's XDAtools.exe and cook your ROM then save it on your SD-card
for me it's work 100% my Qtek provieder in Saudi Arbia said that you can't downgread ROM after you do upgread but what ?? it's work
:lol:
[email protected]

Upgrade radio fail
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.

After upgrad radio from 4.16 to 4.21, My O2 does not reset or hardreset normally. After a long process, I get a blank screen with only input icon on the lowwer right corner. How to fix it now?

problem solved.

inaccess said:
problem solved.
Click to expand...
Click to collapse
How have you done it ?

Re: Upgrade radio fail
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance

Re: Upgrade radio fail
darkdragoon said:
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Click to expand...
Click to collapse
If you push the power buttom and than do a hard/cold reset do you get a bootloader ???
If so you need a storage card and put a good rom on it.
Read more on this forum

Re: Upgrade radio fail
I got a problem yesterday night, while trying to updgrade the ROM with the XDA developers Special Edition ROM v1.2, I got the message from the tool saying it will take up to 5 min and a scroll bar appeared on the XDA and not removing it from its base.
But I accidently removed it (in fact, I caught my foot on the damn wire and everything went to the floor).
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
The screen when I hard-reset it shows the scrollbar that was displayed when I tried to upgrade it.
ActiveSync does not recognize it anymore (PC beeps when the XDA is put in craddle, but it does go further).
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
I own a SX-56 and subscribe to Rogers AT&T; I guess my config is identical to a AT&T phone, as it's written on top
Any suggestion will be welcomed
Bernard

Re: Upgrade radio fail
droletbe said:
I got a problem yesterday night, while trying to updgrade the ROM with the XDA developers Special Edition ROM v1.2, I got the message from the tool saying it will take up to 5 min and a scroll bar appeared on the XDA and not removing it from its base.
But I accidently removed it (in fact, I caught my foot on the damn wire and everything went to the floor).
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
The screen when I hard-reset it shows the scrollbar that was displayed when I tried to upgrade it.
ActiveSync does not recognize it anymore (PC beeps when the XDA is put in craddle, but it does go further).
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
I own a SX-56 and subscribe to Rogers AT&T; I guess my config is identical to a AT&T phone, as it's written on top
Any suggestion will be welcomed
Bernard
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.

Re: Upgrade radio fail
Weezer-DC said:
darkdragoon said:
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Click to expand...
Click to collapse
If you push the power buttom and than do a hard/cold reset do you get a bootloader ???
If so you need a storage card and put a good rom on it.
Read more on this forum
Click to expand...
Click to collapse
Yes, I got the Wallaby bootloader and it said GSM failed.
Pls show me where about I could get more info on the forum.
ThanX in advance.

Re: Upgrade radio fail
Weezer-DC said:
droletbe said:
...
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
...
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
...
Any suggestion will be welcomed
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Click to expand...
Click to collapse
Any place/URL to look for such thing as the ROM and the writer ? How much should I expect ?
Thanks for your help

Re: Upgrade radio fail
droletbe said:
Weezer-DC said:
droletbe said:
...
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
...
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
...
Any suggestion will be welcomed
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Click to expand...
Click to collapse
Any place/URL to look for such thing as the ROM and the writer ? How much should I expect ?
Thanks for your help
Click to expand...
Click to collapse
Now everything works ! And this accident "forced" me to buy an SD, so I will not be so limited by the 32Mb limit
Thank you very much

help needed....
i hard reseted my qtek 1010 .... its like 30mins ....and am still gettin 4 bands white red greem blue... is that normal ...that hard reset take this much time... if this si not normal ... what should i do next

Bootloader not recognising sd card image
I am having the same problem. When pressing power and reset, bootloader shows v 5.17 GSM fail.
I have an sd card which has a new bootloader and nb1 file on it. I do a reset with the card in the slot and i get the same screen v517 GSM fail. From what i have read i should be getting an option to upload the new rom.
Can some one help me out please?
If I currently turn the device on normally activesync does not recognise the device.....
The sd card I have was configured using the xdirt programme and it appears to have worked as the sd card is shows not formatted now...

Thanks for all the info and warnings, just got my XDA II today and Im not too hot with it yet so I guess I will be leaving the ROM's alone for the time being

Peter Poelman said:
Radio Stack Upgrades:
Click to expand...
Click to collapse
We have several system where the GSM rom is toast. Is there a way to get a GSM Rom to SD w/o using the PC Monitor program?
The systems will successfully bootup and we have tried loading the GSM rom using RSUpgrade, but it fails after 1%.
Is there any other way to recover the GSM Rom?

You may try speaking to Cgigate on this forum, he has hardware methods of programming the chips directly, whether it works for the radio stack as well as the bootloader and rom you will need to ask him.

Newbies, ROM 4.00.05 -> 4.01.00, Wallaby 5.17 (Oceania/As

Hi All,
After a LOT of reading and mucking about, I've been able to update my ROM, get full use of GPRS and revert back to the manufacturer's ROM. There are a number of instructions, some of which are pretty dangerous. The following forum topic is the invaluable guide you need to read if you wish to revert back from a T-Mobile installation :
http://xda-developers.com/forum/viewtopic.php?t=3274
The place to get your ROM's is http://www.yorch.net, from the ROM Kitchen. Use the XDA Tools from the above forum link to burn ROM's you download from Yorch's onto your beloved XDA (use the .nb1 format, NOT the .exe method and burn using XDA Tools through your USB cradle).
I happen to have the 5.17 Wallaby bootloader which means that it will not let you simply whack in an SD card with a new O/S and burn off a backup ROM, it won't happen. Don't try to upgrade your Wallaby bootloader. The safest method is to use the Wallaby bootloader patch which can be downloaded from a link at the top of the forum topic link I posted above. That allows you to do a simple O/S restore from your SD card, providing you have an SD reader which presents your SD card as a new drive on your computer. The instructions are simple, just use xdrit as per the instructions in the forum topic link above.
So, from my experience I backed up my original ROM using XDA Tools and stored it on my hard disk in .nb1 format. I then downloaded the .nb1 for 4.00.16 and installed it using XDA Tools without a hitch. Everything worked fine, but I wasn't comfortable until I knew I could revert back to my original ROM. So my next step was to write the Wallaby Patch tool onto my SD card using xdrit using the instructions as laid out in the forum topic link above (take note, use the 1K header option in xdrit). The SD card reader I used was an X-Drive that you normally use for digital camera style stuff. Once written, I put the SD card in the XDA and did the bootloader boot (hold the power button whilst pressing the reset button), and was then given the option to press the Action key to go into the diagnostic mode which is where the patch program resides.
I then took the SD card out, leaving the diagnostic screen still open, put the card back into the X-Drive, formatted it using default options in Windows XP, then wrote the ROM backup I had (you can use any ROM here) onto the SD using xdrit, selecting the 3.5K header option (because we are still using Wallaby 5.17 regardless of patching). The last major step was to place the SD card back into the XDA and select Restore SD and accepted the risk notices. The restore appeared to go fine, but at the end it said Incorrect CRC. That in itself is a worry, but I had at least restored to a point where I could burn whatever ROM I like using the simple XDA Tools method, which is exactly what I did after reviewing the connection info (once more), going to 4.00.05.
Before I originally went to 4.00.16 I recorded all my connection details, including proxy info. When I went to 4.00.16 and re-entered all the gprs info, I found that the internet worked, but MSN Messenger would not connect, stating that the proxy info was incorrect - even though the values were exactly as originally setup. That was one major reason for wanting to go to another ROM. However when I ultimately got 4.00.05 on, I kept getting exactly the same error message with MSN Messenger. The answer came from a hint in another forum topic where someone (with AT&T I think it was) said not to put anything in the proxy info. That did the trick. Un-ticking the proxy option allowed the internet and MSN Messenger to work perfectly.
For Telstra GPRS (I think this is universal) the access point name is : telstra.wap.mnc001.mcc505.gprs
GPRS Authentication method is PAP authentication.
Hopefully this info might help someone out there, because I spent close on 8 hours sweating over trying to get my original ROM back up and running.

Oh yeah, thanks to the XDA Developers, Yorch and the whole XDA community. ROM updating really is easy when you've got the right info, and I can tell you it's really worth upgrading to PPC 2003 (WM2003?), it seems so much more stable, my GPRS has never stayed on as long and it's fun! You can get creative in the ROM kitchens (such as http://www.yorch.net), adding the software you like.
Just a piece of advice, search the threads for problems with any ROM you want to try out first so that you know the traps before it's having a party on your XDA at your sanity's expense.

I have some more observations now that I'm getting more comfortable with doing ROM updates. There are some advantages in going from the 4.00.05 ROM to 4.00.21, such as button lockout while off.
When I initially did the 4.00.21 upgrade I happened to go into the "band" option in phone settings and left the options unselected. Unfortunately setting this to nothing defaults to USA which is totally incompatible with Australia. The result was the phone would not synchronize and I could no longer go into phone settings. The fix for this scenario can be found in this thread : http://xda-developers.com/phpBB/viewtopic.php?t=2893&sid=1e7be62705d2831332c7f0bd5a75e364. It's standard stuff to the die-hards, the scariest thing in the world for us newbies.
Once you set the band for Australia (same as Europe - 900/1800 I think it is) you then get a signal, can synchronize and start customizing your settings. You can get rid of most of the T-Mobile garbage, so far everything is working fine.

Thanks for that buddy, i'm about to do the same downgrade tonight (once Yorch's kitchen is back working properly). You saved me many many hours of pain!
Thanks to all who add to these wonderful forums.
Steve

Just to keep this info updated for the Aussies (and same applies for Asians, and Europe too I think), basically the same applies for 4.01.00 as I explained for 4.00.21 further back. 4.01.00 seems much the same as 4.00.21 at the moment.

Hi guys,
I have a similar set-up as yours, ie I am in Australia nd I upgraded my rom to a 4.00.16. I would like to downgrade it to the original O2 one as I have to return the phone to my company (I am being made redundant).
I tried the method you described but I failed. Basically, I can write the patch on the SD card and when I put it back into the device nothing changes...
Could you please be more specific as to what you did ? Typically, did you switch off the device then put the card then stop/soft-reset or else ?
As well, I only have the NBF version of the O2 rom that I got from the update on their site. Do you think it works or should I try to find a "pure" NB1 rom (I think there's one on Yorch's website).
Thanks a lot in advance for your help.
Bob.

Hi Bob,
Sorry to hear you have to give up your XDA, hope you have replacement work for your redundancy.
Once you have written the Wallaby Patch onto the SD card using XDRIT you reset the device using the stylus and hold down the power button at the same time (with the SD card with the patch in place). That will load into bootload mode, and you press the action button at that point to actually go into the patch.
Once the patch has loaded you leave the device on, and remove the SD card, write your ROM image onto it using XDRIT, and place the SD card back into the phone. On the patch screen select "Restore from SD" using the little directional arrows button below the phone screen. It will then ask you to confirm, then you will see the progress - it takes about 5-7 minutes.
The details on how to write the patch and write ROM's are further up in this thread. I think you can use the NBF file but I am not certain. If you don't want to risk using an NBF you can use the same method above, but revert to the 3.17 ROM from Yorch, then you should be able to use the ROM upgrade from O2 to get a clean install of the manufacturer's ROM.
Let us know if you have any problems.

Thanks Mate.
I have tried once again to patch my Wallaby 5.17 (funny name, isn't it...). It failed. Once I go into the bootloader and press the OK button, I get to the diagnostics screen and nothing else is happening.
Could you shed some light on this ?
Thx.
Bob.

Re-reading your posts...
Would it be possible for you to send me the wallaby patch tool you used ? I tried the one from here (http://xda-developers.com/XDArit/wallaby-patch-tool.nb2), as is and renamed to nb0, but it seems to be the key.
Basically, even though I get the following message : "Successfully copied image of 514 blocks", after having chosen the 1k header, as it's explained in the very detailed post you mention, I still get to the diagnostics screen instead of the patch one...
Thx again in advance for any help.
Bob.[/img]

I tried the one from here (http://xda-developers.com/XDArit/wallaby-patch-tool.nb2), as is and renamed to nb0, but it seems to be the key
Click to expand...
Click to collapse
Hmm, I had no problem at all with the bootloader... one thing though is that you don't rename the .nb2 to .nb0, you use the file as-is. In XDARIT you should be able to select the .nb2 file to write to SD.
It is a diagnostics screen that you get to, that is the purpose of the patch. In that diagnostics screen should be options such as backup ROM to SD and restore ROM from SD. If it still doesn't work for you then maybe I should send you the versions of the patch and XDARIT that worked for me.

Hi,
I am using the O2 3.20.06 ENG ROM and 4.21.00 Radio. Do you think I can upgrade to 4.00.21 ROM directly?
Should I just run the exe file from the Yorch.net? Is it that simple?
What about the radio? Do I have to install a new one or is the 4.00.21 ROM included the radio?
Also, why people need to upgrade bootloader to higher version? I am using bootloader 5.15.
Thanks very much in advanced.

Well, I wouldn't use an exe for upgrading, and I wouldn't try upgrading the radio unless it's an official one posted by your supplier.
Use a .nb1 ROM from yorch and use XDA-TOOLS to do the ROM upgrade. Remember that if you go to a T-Mobile ROM you will need to use the SD card method to change to a different ROM.
Don't try upgrading your bootloader, 5.15 is fine. It's the higher versions that can be problematic and require the patch.

Thanks very much for your reply.
I am about to upgrade my device.
Just a few more questions,
1. Is this 4.00.21 ROM worked okay with the 4.21 Radio in Asia?
2. Also, other encounter a problem with SD card with this new 4.00.21 ROM, have you find any? (every 48 hrs the device wipe out the data in the SD card!)
3. It seems to me when using SD card method to change ROM with bootloader 5.15, the procedure is the same as upgrading or downgrading, isn't it?
4. The file from Yorch.net "upgrade" is only nbf file. It's not nb1. Is it the same?
Cheers,

Hi Chris
1. Yes, 4.00.21 does work fine with the 4.21 radio. I've touched on moving from 900/1900 to 900/1800 band if you should strike that problem.
2. Funny thing that, but I just checked and my SD card is erased after some 3 weeks of no problems.
3. Yes.
4. I do know that if you make a ROM in Yorch's kitchen you can choose .nb1. If you download an 'upgrade' I'm not quite sure what you get.

Not successful with the upgrade
Thanks so much for your reply.
From Yorch.net "upgrade", I can only get the 4.00.21 nbf file which is not nb1.
I can't use xdarit to burn that rom to SD card, an error occurred. But when I use the new OSImagetool, I can burn the ROM to the SD card and I can even change the name to nb1 file.
For both cases (nbf or nb1 file), I put the SD card in my device and press to the bootloading mode, nothing happen!
The device can't detect there is a ROM upgrade there. How can I do that?

Chris,
You need to download the .nb1 from the Rom Kitchen link on Yorch, not from the upgrades link, if all you are getting is a .nbf. With .nb1 you can use the osimage tool or xdrit with the sd method.
The bootloader will not restore from sd unless you have a correctly written image. In Yorch's kitchen you will see that .nbf is tagged for advanced users, that's a strong hint that different methods need to be used to install those.

I see....
Thanks v much.

Sorry for the delay in reply but I had gone back to Europe for Christmas.
I would be happy to use your wallaby patch file as mine doesn't seem to work. You can mail it to me on [email protected].
Thanks in advance for your help,
Bob.

Ok Bob, I'll send it in a few days when I get back to a PC. But I can guarantee it's the same patch that I linked back to in this thread.

Software to unlock Wallaby Siemens SX56

Hi I know the site had lost lots of posts and lots of links arent working. Can someone provide me with a link to download the software and instructions to unlock my phone. I have a Seimens SX 56 from AT&T
Both USB and serial cables
256 MB SD card
Thank you

http://lumpistefan.dyndns.org/tools/manual2_unlock.htm
http://lumpistefan.dyndns.org/tools/manual_unlock.htm
http://lumpistefan.dyndns.org/tools/special_rom_1.2.exe.zip
HTH
Stefan

Thanks for the info. But i thought there was a simpler way. I have a serial cable and SD card. Is there a simpler way without going through all this ?

You can try dragging xdaunlock to your pda, execute it there and see if it works, if not you could try xda manipulator. If both fail you will need to burn a rom based on 2002 and you need to include the xdaunlock.

Im sorry but do you have links to the mentioned software with detailed instructions. I tried doing forums searches and it seems every link with those software and instructions are dead. I would appreciate it.

http://wiki.xda-developers.com/index.php?XDAmanipulator
http://wiki.xda-developers.com/index.php?XDAunlock
HTH
Stefan

LumpiStefan you have been of great help. Just more thing if you dont mind. In the first link it said I needed XDA ROM Image tool v1.2 and bootloader_v5_15.nb0 again I have tried to search and no avail. If you can link me to those I would be most happy. Thanks again [/quote]

Should be all in there:
http://lumpistefan.dyndns.org/tools/XDATools.zip

Thanks!
I've unlocked the phone now, can I re-install the old operating system, or will that kill the unlock?
I love the GSM band selector, but the other programs I prefer on my old operating system. Is there anyway to reinstall my other operating system, keep the phone unlocked, and keep the GSM selector program?

CrazyPale said:
Thanks!
I've unlocked the phone now, can I re-install the old operating system, or will that kill the unlock?
I love the GSM band selector, but the other programs I prefer on my old operating system. Is there anyway to reinstall my other operating system, keep the phone unlocked, and keep the GSM selector program?
Click to expand...
Click to collapse
The phone will stay unlocked.
You can get he bandselector from here:
http://wiki.xda-developers.com/index.php?pagename=BandSwitchTool
HTH
Stefan

Do I just use the OS Image tool and point it to my saved NB1 file loading it
back into the Device Memory? Is there a better way to do it?

How to create Wallaby patch with OSImageTool?

Dear All,
I've tried to create a Wallaby Patch.nb2 for my Wallaby Bootloader 5.17.
I tried XDArit but failed with "Failed to open device \\.\PhysicalDisk23"
Can I do it with other tools such as OSImageTool?
Thanks in advance.

Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim

Thanks goldendel. You are my man. Now I've finally entered the so called diagnostic mode and playing around with different ROMs!
Rgds.
goldendel said:
Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim
Click to expand...
Click to collapse

Doi.Doi. said:
Thanks goldendel. You are my man. Now I've finally entered the so called diagnostic mode and playing around with different ROMs!
Rgds.
goldendel said:
Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I couldn't get into the bootloader any more. Hence, I did everything you say above e.g getting XDARit 1.0 and instruction from Negatong, however, XDARIT could't run on my computer. Every time I run it, I get the message: "XDA ROM Image Tool has encountered a problem and needs to close. We are sorry for the inconvenience".
Do you come up with any different solution? Tks

Doi.Doi. said:
Thanks goldendel. You are my man. Now I've finally entered the so called diagnostic mode and playing around with different ROMs!
Rgds.
goldendel said:
Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I couldn't get into the bootloader any more. Hence, I did everything you say above e.g getting XDARit 1.0 and instruction from Negatong, however, XDARIT could't run on my computer. Every time I run it, I get the message: "XDA ROM Image Tool has encountered a problem and needs to close. We are sorry for the inconvenience".
Do you come up with any different solution? Tks

Hi Nghiem,
I haven't had this problem before. There are several posts about people not being able to get into the bootloader any more. By the sound of it, most people manage to get in eventually by constant hard reseting. Alternatively, you could try the bootload fixer if it's definately stuffed. I haven't tried this, but again, there are guidelines in the forum.
Good luck.
Tim

http://lumpistefan.dyndns.org/tools/wallaby-patch-tool.nb2
other useful things,
http://lumpistefan.dyndns.org/tools/

Doi.Doi. said:
http://lumpistefan.dyndns.org/tools/wallaby-patch-tool.nb2
other useful things,
http://lumpistefan.dyndns.org/tools/
Click to expand...
Click to collapse
Or all here:
ftp://xda:[email protected]/Wallaby/Tools/
and
http://wiki.xda-developers.com/index.php?pagename=Wallaby
Stefan

Roms on the FTP

Hi all,
I uploaded all roms + extended roms I have for our beloved HTC Wizard.
You can find them here:
ftp://xda:[email protected]/Uploads/HTC_Wizard/
Maybe a (FTP) administrator can move them to the main FTP index so we have a folder like all other HTC phones.
Any new roms can ofcourse be uploaded to the same folder.
Have fun!

Hey
why you don't have an german rom ?
regards, Peter

Because I dont have any German roms myself.
I uploaded all roms I found myself...
If you can provide me any links than I can download it and upload to the XDA FTP.

Has anyone managed to make a ROM dump of the UK T-Mobile ROM?

I would be interested in an o2 UK rom also.
Would be nice.

Yeah, would be good to get an archive of all the roms, good work on getting this started.
If i wasn't in such a hurry to flash my Rom i would have waited until i got a Mini SD card and backed my UK T-Mobile ROM up first, im just too impatient! :lol: Wish i had waited now, as now i am after it again!!
Anyone?... :?

Thanks Panja
can anyone upload the TW_Chinese ROM? Thanks

mattstroud said:
If i wasn't in such a hurry to flash my Rom i would have waited until i got a Mini SD card and backed my UK T-Mobile ROM up first, im just too impatient!
Click to expand...
Click to collapse
How i can do this? Is there any proggy which backup the rom?

To backup your rom you need to do the folowing...
First:
Your phone needs to have the bootloaded unlocked ,so use the following unlock tool lokiwiz - HTC Wizard Unlocker UPDATE Version 0.2a created by machinagod which can be found here, and when you run the PC app choose 'C' for SuperCID (this will unlock the bootloader) Version 0.2a is the latest and it worked great on my phone, instructins are on the page - Thank you machinagod for all your work here, its a great tool!
Second:
To backup the ROM, download the two files attached to This Post written by arnoldl - Thanks for this info arnoldl, very helpful. Follow the instructions in the post.
Third:
Which ROM is it by the way? T-Mobile? O2? is it a UK ROM?
When you have it saved can you upload it to The FTP area and post here to tell us what it's called and where it is so it can be catalogued with others to help build a good archive of them.
Cheers and Hope this info helps

Second:
To backup the ROM, download the two files attached to This Post written by arnoldl - Thanks for this info arnoldl, very helpful. Follow the instructions in the post.
Click to expand...
Click to collapse
you can restore the image only, when you leave the image on the sd-card.
when you write it on your harddisk with ntrw and write it back to sd-card with ntrw the restore won't work!
Nobody here has confirmed, that the image (here on ftp) are working!
regards,
Peter
Update: The image "germany in qtek.rar" (size 50mb) was deleted from ftp

you can restore the image only, when you leave the image on the sd-card.
when you write it on your harddisk with ntrw and write it back to sd-card with ntrw the restore won't work!
Nobody here has confirmed, that the image (here on ftp) are working!
Click to expand...
Click to collapse
Cheers greddy - i was just about to post that!!
Can the image on the SD card be coppied to a Zip or Rar file directly and NOT using NTRW? Maybe this can be tried and extracted back onto a mini SD card by someone else, im very willing to try it, then we will all know if this works.
So for now bill_viper - Backup your ROM to MiniSD card but do not use NTRW!! Just keep that Mini SD card safe and do not delete it until a safe way of backing up the image to a distributable file or archive has been found.

I've just done a bit more reading and it looks like you can use NTRW to create a backup file of the ROM from the SD card image.
The problem experienced is with loading ANY rom onto the device using the 1.06 bootloader (the one with the K-JAM rom) so in order to put a Rom onto a device with the 1.06 K-Jam rom - the 1.06 bootloader) you first have to put the prodigy rom on or something like this using the *.exe file as it has a different bootloader (1.01)
So bill_viper please do use NTRW to backup the ROM image on your MiniSD card, and please post it on the FTP for archiving.
Cheers

First of all i would like thanq mattstroud for your time.
The info u've posted are very helpful. I have a Qtek 9100 English Version.
I will read the thread u specified above and i'll backup my rom and upload it.

Hello mattstroud
i have try Booloader 1.01, 1.03 and 1.06!
No luck and not the reason, why ntrw makes **** when read and
wrote images.
We will see 8)
regards, Peter

..

Hi greddy,
did you not have a damaged image file wasn't that the reason for your problems?
----------EDIT----------
Seeing sun75's post proves that the problem does lie with the 1.06 Bootloader and not the NTRW image, so greddy i think your image file was damaged which caused problems regardless of which bootloader was being used.
Cheers for this info sun75, good to get some definite proof after all.

Hey mattstroud,
did you not have a damaged image file wasn't that the reason for your problems?
Click to expand...
Click to collapse
at the moment i am not sure. Since 2 hours i am testing with
backup/restore from sd-card and it works, also with 1.06, all bootloader
versions are working, but nothing with restored ntrw images.
I am using ntrw 2.00 from here, is this right ?
regards

Hi greddy,
Hey mattstroud,
did you not have a damaged image file wasn't that the reason for your problems?
Click to expand...
Click to collapse
at the moment i am not sure. Since 2 hours i am testing with
backup/restore from sd-card and it works, also with 1.06, all bootloader
versions are working, but nothing with restored ntrw images.
I am using ntrw 2.00 from here, is this right ?
Click to expand...
Click to collapse
Ok, i didn't know this. Looking at sun75's post it worked fine for him when he loaded a rom with the 1.03 bootloader. Maybe this problem is specific to your device? :?

2 new roms added:
K-JAM_Italian_1030902_102_ship.exe
K-JAM_Norwegian_1040902_104_10910_ship.exe

Excellent, nice one.
Any one able to add a T-Mobile UK ROM?