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.

ROM upgrade help

I wanted to install one of the ROMs from www.yorch.net. But before doing so I have some questions:
1. If I choose to build ROM as an installer.exe, is installing it to my device as simple as running the .exe file? (of course with the device connected thru Activesync)
2. Is my present ROM (see specs below) supported?
3. If Murphy comes to visit and I screw up, will my phone be completely unusable or can I just reinstall old ROM, do hard reset and everything will be back to how it was?
My specs:
OS: Pocket PC ver 3.0.12039
ROM:3.20.06 ENG( 07/30/03) (O2 Asia I think since I bought it here in the Philippines)
Radio: 4.21.00.
Thanks

1 as far as i know yes havent don it to my own device yet though
2 a rom dont have to support a rom since it'll overwrite it
3 of cause merphy can also show his ugly face
but if all fails a sd flash reader writer can save many a tears
also if your phone is working ok then i would not mess with the
radio stack and beware because some roms include the radio stack
and if you try to update your radio stack to a US (900/1900) and you network is 900/1800 you could be in for a world of pain

ROM upgrade step by step
OK I'm really dying to give it a go but I'm just a overly cautious bloke. So I'm gonna outline what I interpreted (after reading lots of posts I think I'm getting it but not sure) to be the way do the upgrade. Please correct me if i'm wrong:
Equipment I have:
1. My notebook (Windows XP, Activesynch 3.7)
2. O2 XDAI
3. Cradle and USB connection.
Steps that I think I should take:
1. Place XDA on cradle and make sure it's connected with PC.
2. Backup?? (not so sure what to back up since contacts, calendar, notes are synched with outlook, docs are also synched, I have copies of cab and program files since I download them to PC before installing them to XDA.) If i'm missing something please slam a frying pan (this is a kitchen right?) on my head.
3. Go to www.yorch.net, check mark on all appropriate options, then (since I have to Unix box and dont know Unix at all) just go for the easy option of cooking the .exe install file.
4. Assuming, the .exe is downloaded to my PC. This time I just run it. I expect this to be just like installing PPC apps. If not, throw a tomato on my face
5. Assuming everything worked and Murphy's in the Arctic freezing his A**e off, then all I do now is hard reset.
6. I have a new ROM and I'm singing happy-happy-joy-joy.
To the wonderful people at xda-developers, am I in the right direction or am I as lost as Bill and Ted? If I'm lost, is there a step-by-step guide for non-unix programmers? (Sorry, there was a sticky but I thought it was for people with Unix boxes)
Once again, thanks for all your help and your patience.

2. Backup?? (not so sure what to back up since contacts, calendar, notes are synched with outlook, docs are also synched, I have copies of cab and program files since I download them to PC before installing them to XDA.) If i'm missing something please slam a frying pan (this is a kitchen right?) on my head.
Click to expand...
Click to collapse
well i can think of one thing to backup and thats your current rom
so if you dont like the new rom you are getting you have the option to go back
of cause if the rom you have now is downloadble from a place you know like your isp then maybe it dont matter

Thanks for the reply. That's a good point. Question: When you back up old ROM, is it just the ROM that gets backed up or is it the whole content of the device, like how you do in PCs?
Also, since no one, besides you, has made any comments regarding the steps that I outlined, is it safe to say that they are the correct steps?
Thanks

When you backup your ROM, no stuff that you customised will be in the backup - the backed up ROM will be the same as when you received it from your retail shop, or if you upgraded, it will be the upgraded ROM without any of your stuff. Do a backup and store it on your hard disk.
DON'T use the .exe cooked ROM, use a .nb1 or .nbf, and use XDA Tools from this site to do the upgrade. It's very easy that way, and less dangerous. Don't upgrade your radio stack unless you know exactly what you're doing, or your phone supplier has made an update available just for you.
If you use a T-Mobile ROM above version 4.00.05 it blocks the XDA-Tools from updating the ROM. At that point you need to use XDARIT (from this site) to low-level write the ROM image you have onto your SD card using an SD card reader which shows the card as another drive on your computer. Once you do that you need to boot into the boot-loader (press the reset button while holding the power button) and follow the prompts to restore from an SD card. If you're unlucky and are running bootloader 5.17 (or above I think) you need to write the bootloader diagnostics patch (wallaby patch from this site) onto your SD card first before doing the boot into the bootloader thing. You can then remove the SD card, write the O/S ROM onto it with XDRIT, and put it back into your phone while it's still sitting on in diagnostics mode. Then you can restore from the SD.
It sounds complicated, but it's easy, as long as you have an SD card reader, and as long as you don't mess with trying to update the bootloader or do an unknown radio update. There's lots of info in these forums if you get stuck.
I made a thread that summarised all the steps using the new tools and ROM's at this address : http://xda-developers.com/phpBB/viewtopic.php?t=3860. It's for Asian/European users, but if you are in the US the instructions are the same, except instead of using European 900/1800 radio you use 900/1900.

Further questions on ROM update
Thanks. It's becoming clearer and clearer. Have more clarifying questions:
1. How do you know whether or not you're including the radio stack with the ROM upgrade at yorch.net. I did not see any options there.
2. At www. yorch.net, nothing happens when I press the "Build ROM Now" command button. Is the download supposed to happen in the background or is there something wrong with my PC or the site?
3. I dont think I'm using the T-mobile ROM but how do I know if I'm runing bootloader 5.17? Is bootloader 5.17 only for T-Mobile users or all?
Once again, thanks for the help and bearing with a newbie.

2. At www. yorch.net, nothing happens when I press the "Build ROM Now" command button. Is the download supposed to happen in the background or is there something wrong with my PC or the site?
Click to expand...
Click to collapse
it should start to write some text about the progress of making the rom
and when it's finished then it should init a std download dialog

The meter down at the status bar does move, same as when you're loading a webpage, then it says Done. That's about it. Didnt see any other messages or dialogue boxes.
Can anyone confirm if it's up today or has it been down?
Thanks
PS. Tried to email using the email utility at the website but getting errors there as well.

OK, firstly to answer your question about Yorch's site... well it worked for me in getting all the ROM's I wanted, then when I went back again the download didn't work. I guess it's just on and off, so unless Yorch finishes getting married or someone else makes another kitchen it's a matter of pot luck. You can get away without using the kitchen if you can find another download source for ROM's, whether it be FTP or whatever. Just remember if you get an exe you can usually pull it apart with winzip to get the .nb1 or .nbf out of it.
Now, for Q1 :
An operating system ROM is generally just under 32MB, but when zipped from Yorch it's usually about 14 or 15MB - the operating system ROM will NEVER be smaller than that. I'm not sure about the exact radio stack size but I know it's a lot less than that. Also, doing some homework about the operating system ROM helps. eg. reading about the 4.01.00 ROM tells you that it's not a radio stack upgrade, it's an operating system upgrade - and the filename and the size of the file you receive reflects that.
Q2:
answered above...
Q3:
I think the bootloader is just pot-luck depending on when you phone was released. To check your bootloader it will reset your device completely, but I read somewhere that if you turn the radio (phone) off it doesn't hard reset. If you're worried, do a full backup first. But basically when you're ready to look, reset your phone while holding the power button and it will tell you the bootloader version. Don't be too turned off by that, I have read that SD card readers can be picked up very cheap if you look around, and that's all you need to get you out of trouble regardless of the bootloader version.
There's no real risk (but I won't guarantee anything), just make sure your phone is fully charged before mucking about with SD upgrades. Also make sure the radio (phone) is switched off before upgrading... using the bootloader/sd card method you shouldn't need to be concerned. I'm not sure what effect having your phone on and receiving a call while using XDA-Tools can have, but someone did mention it somewhere.
I'm a newbie too, but there's really not much you need to know, just a few caveats.

Yorch's Kitchen has been working OK for me the last couple of days. It takes maybe about 5 mins to "cook" before telling me that the ROM is ready. The 4.00.05 ROM gave me a lot of ActiveSync problems, so I went to the 4.00.16 ROM tonight and it looks like it's behaving better.
My SD reader is a Microtech Zio. It appears as a disk drive in windows, but the newer XDArit can't initialize a connection to write to the SD card. I used the "dangerous" older version of XDArit instead (available on Yorch's site), and it's worked OK for me (so far?).
One thing I wish I had realized before I started playing - going into the bootloader will reset your phone most (some?) (all?) of the time.
While I was flashing the ROM tonight I could see the GSM light flashing - I had the same "hope no one calls" feeling tht others must have had. Note that this was while I was flashing from an SD card in the bootloader - so apparently the process doesn't deactivate the phone while it's ongoing.

Muchas Gracias!
Ebswift, if ur a newbie then ur the god of the newbies. Thanks for all the help and for making me see the light. Much appreciated...

A quick Q:
Is the process for installing an .nbf file the same as that for installing an .nb1 file?
I have cooked a few ROMS to an .nb1 format and installed those OK, but now I have one in .nbf that I'd like to install.
So what I'd plan to do is put the nbf onto an SD card using XDArit, and then stick the card in the PPCPE and reboot to the loader. Is that it?

So what I'd plan to do is put the nbf onto an SD card using XDArit, and then stick the card in the PPCPE and reboot to the loader. Is that it?
Click to expand...
Click to collapse
You can do it that way (onto the SD card), or if you're not already using a T-Mobile ROM you can use XDA Tools which is easier. Basically the capabilities are spelled out for you with the available file types in the drop downs when you select a source.

Problems after Start HimaClearJumpCode.exe

Hello,
i do something wrong,
i start the HimaClearJumpCode.exe on my XDAII, and now
the XDA always in the USB/Serial V1.01 mode and any
reset or remove battery don't restart.
could someone have a idea how to reset it?
Regards
Markus

Why do you start this file ????
AFAIK this file is used during the update-process by the
HimalayUpgrade and should never be used manually.
And AFAIK it definitly thrashes your as it jumps into the bootloader.
Try to describe what you want to do !!!
Alex

you can restore your device by running the HimeUpgradeUt.exe with the xda2 cradled. it will take a minute orso before it starts.
by running the HimaClearJumpCode.exe you have erased the first 256k of your rom.
normally this is done by the upgrade tool, which first makes a backup of this part of the rom ( 80040000-80080000 ) to the top 256k ( 81fc0000-82000000 )
then runs HimaClearJumpCode.exe, then resets the device, to enter the bootloader.
and after it is done flashing other parts, it copies back the saved rom part.

itsme said:
you can restore your device by running the HimeUpgradeUt.exe with the xda2 cradled. it will take a minute orso before it starts.
by running the HimaClearJumpCode.exe you have erased the first 256k of your rom.
normally this is done by the upgrade tool, which first makes a backup of this part of the rom ( 80040000-80080000 ) to the top 256k ( 81fc0000-82000000 )
then runs HimaClearJumpCode.exe, then resets the device, to enter the bootloader.
and after it is done flashing other parts, it copies back the saved rom part.
Click to expand...
Click to collapse
hi, I am one of those stupids who did this **** again. In the restoring method, u mentioned that one has to run the HimeUpgradeUt.exe with xda2 cradled. U didn't mention if i need to have the Extended ROM in the same folder where HimeUpgradeUt.exe resides. Do I need to do place the Extended ROM image(.nbf) to that folder. If so, please suggest me a appropriate English Extended ROM name. I have searched at the ftp but unfortunately I could hardly understand by the naming of the ROM on the ftp. I want my XDAII back. please help.

upol said:
hi, I am one of those stupids who did this **** again. In the restoring method, u mentioned that one has to run the HimeUpgradeUt.exe with xda2 cradled. U didn't mention if i need to have the Extended ROM in the same folder where HimeUpgradeUt.exe resides. Do I need to do place the Extended ROM image(.nbf) to that folder. If so, please suggest me a appropriate English Extended ROM name. I have searched at the ftp but unfortunately I could hardly understand by the naming of the ROM on the ftp. I want my XDAII back. please help.
Click to expand...
Click to collapse
extROM is different part. You can update without extROM

HELP !!! Radio 1.13.0 SD Card upgrade failure

Radio 1.13.0 SD Card upgrade failure
Error :
SD Download
=========
Section =1
Not Allow
Update!
Right now when the PPC soft reset the right of botton corner display NO GSM
Please Help me Thanks a lot.

didnt you save your origional radio?
or just try again??
it worked for me first try. what did you do??

You should have overwritten the first 444bytes of your 1.13 ROM with 444bytes a SD card backup of an older Radio ROM!

thanks your adivse let try again

416 bytes would be ok, I have done and works fine.

What software do you use to replace the bytes?

Hex Editor, you could find it at the ftp server of xda-developers.
/Magician/Tools/Backup_tools1/

rjtd said:
What software do you use to replace the bytes?
Click to expand...
Click to collapse
I am usng the Hex editor

gradius44 said:
416 bytes would be ok, I have done and works fine.
Click to expand...
Click to collapse
Be very carefull with that. This is NOT a full ROM backup, so the layout is different. I would strongly suggest copying all the bytes, or you could end up with that dreaded paperweight.

what if you don't do the 444 bytes things ?
can you just copy the radio as is ?
thanks

I have no clue, and I would never try to do it. Far too big a risk to take, just to save 1-2 minutes...

i say this because I don't understand this part (overwriting the 440 Bytes from 1.13 Radio with the 440 bytes of my older radio 1.12 )
is that this way or vice versa ?
When you open an hex editor ? What do you see ? how can you see this is the first 440 bytes ?
thanks man if you can help me

Those first few bytes, in this case 444 of them, contain an unique device ID. That ID is needed to 'authenticate' the ROM-image when being flashed to the device. I've tryed to flash my Magician without patching my new ROM with a number of bytes from the older (backup) ROM. The device gives my some freaky error, but nothing else happens, since the bootloader detects a 'bad' ROM.