Related
hi folks tried to update special rom and upon where the XDa comes up with upgrading takes 5mins the software crashed out telling me to remove from cradle and do soft reset well did all that but cant get active sync to recongnise the XDA and the XDA is still on that upgraing 5 minute screen HELP
If it will not resume when you restart the upgrade program on the PC, then it's time to upgrade via the bootloader method. You need (access to)an SD-card reader/writer for the PC, and to read around on this forum a bit.
thanxs I guess thats the conclusion I came to however just to make sure do u know the steps involved in installing the special rom I have the download exe file someones put on the forum
****. I cooked a second ROM (based on testing the first one - and removing utils I didn't need)
Flashing started - but this time, ActiveSync dropped out and I was left with the 5 minutes screen.
I have tried hard reset but only the "upgrading' screen appears. Now I'm wishing I had never messed with it.
I can get the Wallaby Boot loader screen to come up (GSM OK) it says.
But I have no clue about this other "bootloader" method mentioned on this page. Can anyone please advise where can I find details of the fix? Is the ROM really wiped out and no longer recoverable?
I have the same problem as the first person who posted.
Then you will need to restore the OS using an SD card. (Min 64mb).
Probably easiest to cook a ROM at Jeffs Kitchen to your taste:
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Save it as .nb1 type (bottom of that page).
Then get XDA Tools (yes I know its starting to sound complicated but its not really). http://xda-developers.com/XDAtools/
That program allows you to copy the .nb1 file you cooked to be loaded onto the SD card.
Once you have transferred the OS (.nb1) file to the SD, stick it in your XDA.
Turn on the XDA pressing simultaneously the on switch and sticking the stylus in the SOFT reset hole.
You should get a white screen saying something like flash ROM from SD. Press the JOG (navigator) big switch at the bottom to start the process.
Make sure you have mains power to XDA during this process.
When it finishes, REMOVE the SD card and press HARD reset.
Should be back to normal!
p.s. It goes without saying that you need an SD card reader !!
p.p.s I hope yours is better than mine. Try to get the latest version with drivers that can deal with big SD card sizes...
It does not say hard reset it say cold reboot to reset. So I did a soft reset and it worked after about 7 tries.
I really like what they did with this ROM Kitchen. I would think that if they can get this really stable then they should offer a service to create your own ROM's allowing the user to select what programs they want to include in the ROM.
Er, if you read other areas on this site you will notice that this is run by enthusiasts, who are making their work available to others.
So a little please and thank you will ease your way.
Rather than... "they should" maybe "it would be nice if...."
:idea: If you really want to DIY - then follow all the instructions, get yourself a Unix platform and MKROM.
Bye
ps sorry I got one detail wrong.
pps Sorry I bothered actually
Ariel said:
Er, if you read other areas on this site you will notice that this is run by enthusiasts, who are making their work available to others.
Click to expand...
Click to collapse
Believe me as the owner of www.pocketpcminds.com I understand this. Back in the days of carrying a Palm OS device there a program that allowed you to add and delete things in your ROM.
What I was suggestion is a service that users could pay for that would inlude a list of Pocket PC programs that the users could choose what programs they want loaded in the ROM. From what I have seen of Pocket PC users each person has a list of programs that they find useful and use regularly.
I onlt suggest this because the people running this need to cover thier cost. Otherwise they may use intrest and stop it all together.
We're all too busy with other things to turn the ROMkitchen into a commercial thing. But if anyone else wants to do so, please contact us.
Pro:
- It would be a great sales platform for software (spb gprs monitor, PIMs, etc.)
Con:
- Available space shrinks as OS grows
- No idea how this works out on XDA II yet
Can't burn the Wallaby Patch to the SD
When I try to burn Wallaby Patch to SD the following error appears
Failed to open device \\.\PhysicalDrive8
Anyone help with this.
hi I did all that but when the XDA is being flashed it finishes but comes with achecksum error now I know I am doing everything right as I managed to reload O2 original .nb1 file and my xda is still as was however I want the forums version rom so can unlock many thanx for the previous how 2 instructions
SD card flash - 5 min screen
Ariel said:
Then you will need to restore the OS using an SD card. (Min 64mb).
Probably easiest to cook a ROM at Jeffs Kitchen to your taste:
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Save it as .nb1 type (bottom of that page).
Then get XDA Tools (yes I know its starting to sound complicated but its not really). http://xda-developers.com/XDAtools/
That program allows you to copy the .nb1 file you cooked to be loaded onto the SD card.
Once you have transferred the OS (.nb1) file to the SD, stick it in your XDA.
Turn on the XDA pressing simultaneously the on switch and sticking the stylus in the SOFT reset hole.
You should get a white screen saying something like flash ROM from SD. Press the JOG (navigator) big switch at the bottom to start the process.
Make sure you have mains power to XDA during this process.
When it finishes, REMOVE the SD card and press HARD reset.
Should be back to normal!
Click to expand...
Click to collapse
I have a similar 5 min screen, and I tried as told, that is bought a card reader, cooked ROM, downloaded and transferred the nk.nb1 file to sd card using xda-tools, and entered into bootloader. But all I get is WAIT and then GSM OK message. Not the one that gives me option of flashing the ROM. How exactly to transfer the ROM image to SD card?
Rom Flash Crash
Just in case
I found that getting the XDA going initially by putting across the O2 installer programmeA onto the SD card rebootting with soft reset which installs the standard O2 locked phone system however this allows your XDA to be seen by the PC
all I did then was using the Kitchen Rom is double clicked it then goes into install mode through Programme A and does a PC to phone install.
I found I reinstalled twice and the phone now is working unlocked as required
I tried many times to do the soft reset install as instructed on the forum but it just crashed everytime
I guess the WBL version 5.15 does not identify nk.nb1 file as a rom image. it needs the rom image in raw form, the same as it is copied by bootloader that is WinCE to SD. I think the old XDArit writes it in the required format. dont know how the XDA-Tools does it.
ROM flash crash - solved!
It finally worked. With help from ntabikha, a member of this forum, I got it going. I plugged it in the cradle after hard reset. Activesync kept announcing that it can not connect to the device, and I kept clicking "Retry" (perhaps "disconnect com port" might as well have been all right, but I didn't do it. I thought it might disconnect the com port and stop the Program A from connecting to the device).
I then ran the Original Qtek Upgrade installer, and it did not connect on the first attempt. But it asked me to soft reset the device and run the program again. I did so, and whoa! it worked! It worked great! However, I don't understand why the cooked version 3.17 from Jeff's kitchen was installed instead of Qtek Upgrade Version 3.16.52. I care the least though, since I now have a working xda! Thanks to the guidance from ntabikha.
I have a dead XDA (died while reflashing - some problem with the USB connection) !
I believe that I -may- be able to recover via an SD card. I have read what I can find, but I am not clear about this.
The instructions for flashing the ROM "bootloader" way assume that I can dowload my existing ROM to the SD card and then (I suppose) boot from the SD card?
Since the ROM is trashed (I assume) due to the flash failing, I also assume that I have no viable ROM image to load onto the SD card...?
Is there a URL I can inform myself about this? I've browsed all over this site but can't find anything that seems to address my situation.
I use MSN Messenger if that is easier: [email protected]
I'm really depressed...
Mtks
There's a set of tools here for writing a ROM image to SD-card. Click here to read more.
Using this tool you can write an any ROM image file to an SD-card. The only drawback is that you'll need an SD-card reader-writer attached to your PC, or access to another XDA with functional ROM to do the writing.
Pain in the ass, but if you're willing to accept the current geo-political situation as it is, then this is really nothing to get depressed over...
Hi.
Well I have a card reader, but since my XDA screen is a mess I don't have access to another XDA.
Ariel said:
Hi.
Well I have a card reader, but since my XDA screen is a mess I don't have access to another XDA.
Click to expand...
Click to collapse
AS far as the ROM goes you can build your own just make it a .nb1 file. visit: http://cuba.calyx.nl/~jsummers/ROMkitchen
The screen being messed up shouldn't be a problem just put the SD card into the XDA and hold the power button while doing a soft reset. You’ll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
HTH
Qman:
Many thanks, I needed this spelled out. Hopefuly last question for now:
Which is the ACTION key? CONTACT or CALENDAR button? (there is no such named key on the XDA)
cheers,
Justin
Well what a performance... dodgy card reader, problems over the maximum memory size of the media, not working then working after re-boot....
I'm surprised i cracked it, but I did.
I eventually found the right combination of device and file and cooperative card reader to finally see the ROM (which was cooked at Jeff's Kitchen amd selected as an .nb1 type file rather than an EXE file) copy over to the 128mb SD card.
On insertion into the XDA and re-boot I got the dialogue you described.
I decided that the ACTION key is the navigator key at the bottom of the unit pressed that and the restore began.
I even seem to have managed to RESTORE from an STG backup once I made sure that the personal details (device name) were renamed to the original machine (not Pocket_PC)
Well thanks -very-much for the help. (I only wrote the above to maybe help someone else in the future, who may have the same questions as me).
Now I can go back to playing with the ROM set-up.
I suppose I am right in saying that the ROM version currently at Jeff's Kitchen does not include XDA DEV v1.2?? It certainly doesn't behave as described (the start up tutorial is still there). Also the keyboard option makes the space bar disappear...!!
Thanks to Peter Poelman and Qman.
Cheers
Ariel said:
I suppose I am right in saying that the ROM version currently at Jeff's Kitchen does not include XDA DEV v1.2?? It certainly doesn't behave as described (the start up tutorial is still there). Also the keyboard option makes the space bar disappear...!!
Click to expand...
Click to collapse
I think you may have checked 'Large keys' and 'use gestures'. See the keyboard options to set it like you're used to. (Althoug I prefer 'large keys' and 'use gestures').
Yes, you're right. I will have to get another copy as I don't like it.
Do you happen to know whether v1.2 is being used at Jeffs Kitchen? he first option)
Cheers
Ariel said:
Yes, you're right. I will have to get another copy as I don't like it.
Click to expand...
Click to collapse
Or just turn it off once after cold-boot...
Do you happen to know whether v1.2 is being used at Jeffs Kitchen?
Click to expand...
Click to collapse
Special Edition ROM v1.2 is just the last ROM we built before offering everyone the option of cooking their own ROMs in the ROMkitchen. So I guess you could look at ROMkitchen as a continously evolving "Special Edition ROM 2.x", if you will.
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.
I got MDA from T Mobile with:
ROM : 3.04.00 GER
Radio Version : T302
Protocol Version : 32S54
Pocket PC 2002
The Operating system is in German , I need to change the same to English .
Can someone guide me please .
I am not a techie guy and hence request someone's Help.
I would be exteremly thankful .
Thanks and regards
I do my ROM updates using the XDA's bootloader and an SD card. This seems to work a little better with less chance of things getting messed up. There's also a way to run an installer program on your PC but my observation is that a lot of people who have had problems have used this other method.
a few questions first:
Who is your carrier now?
Do you have an SD card 32MB or larger? (If you don't you'll need one.)
Does the phone/Internet work satisfactorily (even though it's in German)?
DISCLAIMER: I am an idiot. I've probably forgotten some crucial detail or two here. It's up to you to figure out where I'm full of sh*t before starting.
Spend an evening or two reading all of the threads in this 'ROM Updates' forum. It's good to understand the ways something can go wrong and how to avoid making that happen.
Back up all of the data on your XDA before starting. This includes your contact/calendar/task data (normaly these sync with Outlook on your desktop PC when you run Activvesync) as well as any documents that you have saved to device RAM.
Some people do a full backup of their XDA, but it's tricky to restore from this backup when you're not restoring to the same OS version that you backed up from. So I don't bother - I just make sure my outlook data and documents are stored away somewhere safe on my PC.
Back up any data that you've stored on your SD card. You'll end up erasing the SD card as part of the process.
Go here:
http://www.xda-developers.com/XDAtools/
and download XDA tools. You'll use this program to move ROM images to the SD card in your XDA to update the ROM.
Go here:
http://www.romanweb.com/yorch/
and in the "ROM Kitchen" section choose the elements you want to have installed in your XDA along with the OS. The XDA has leftover space in the available ROM memory after the basic Operating System is in there, and the kitchen allows you to put other stuff in here (so it won't take up RAM unless you're actually using it). You can choose a European O2 image or a US T-Mobile image. As long as the bar at the top of the page doesn't read "Overload" you can make a ROM image with what you have selected. Make sure that "Zipped NK.nb1 (SD-Card flashing)" is checked, and press "Build ROM Now" The kitchen will go work for a few minutes and finally will indicate that it's ready to download. Make a note of what your choices were for this image (this is more important after you've been playing and you have downloaded a few different ones), and download the ZIP file to your PC.
You need some software like WinZIP to extract the nb1 file from the ZIP file. If your version of Windows (XP, 98Plus, etc understands "compressed folders" this will work. Use whatever method to extract the .nb1 file from the ZIP file that you've downloaded.
(NOTE: You CAN'T just rename the extension of the file to .nb1 if it's something else like .zip or .exe. Sounds obvious that this won't work but people try it anyway)
Put your SD card into your XDA (you've backed up the SD card, right?) and press the soft reset button on the bottom while holding down the power switch. This will put you into the "Wallaby Bootloader" of the XDA. Read about it here: http://www.xda-developers.com/bootloader/ Press the Contacts button on the upper left of the front to the XDA, and use the joypad to highlight CE+BOOT TO SD. Then press the middle of the joypad to start the copying of your machine's Rom to the SD Card. The screen will count up the progress until it indicates that it's done. Remove the SD card and reset your XDA again.
Put the SD card back into the XDA - it will detect that the SD card is no longer formatted (the ROM image overwrites the formatting) and will ask to reformat the card. Select Nein (German for No). Put the XDA in the sync cradle, and use XDA tools to move the ROM and Boot files from the SD card to your PC for safe keeping. IF you've backed up both the ROM and boot files there should be an .nb1 (ROM) and an .nb0 (boot) file to transfer
Now use XDATools to move the new ROM image .nb1 file that you cooked up in the kitchen onto the SD card. When this is done, remove the XDA from the cradle.
Make sure your battery is fully charged. Don't want to run out of juice during the next step.
You might want to turn off the phone part of the XDA next. I haven't, but people always wonder what will happen if someone calls you while you're in the middle of an upgrade.
With the new ROM image on the SD card in the XDA, soft boot the XDA with the power switch held down. This time the XDA will recognize that there is a ROM image on the card and will offer to install this image.
If you don't get the screen offering to install the image, make sure that you installed the ROM image to the SD card using XDATools. Just copying the file to the SD card using activesync or Windows file copy won't work.
When you do get the offer to dowload the ROM image, press the "Action" button to do so. Again the counter will count up, and when it is done the system will do a checksum (to make sure it got loaded right). If the checksum is OK, it will tell you to Hard reset the XDA. Remove the SD card, and press the button inside the tiny hole on the right bottom. This will turn the XDA all the way off. Wait a couple of seconds, and then press it again to Cold Boot the XDA.
If you've been good, the XDA will boot up with a new, English ROM version installed.
***
Some other notes:
If your bootloader is Version 5.17 the above process won't work (the bootloader version is shown on the first bootloader screen). Read the xda-developers page about the bootloader for info on what to do if this applies.
Need help
THanks for a very explained reply .
Infact since I did not had SD card and I tried to run the upgrade utility and guess I had screwed up .
Now when i power up i only see a progress Bar and try to connect the cradle to laptop it does not sense the device as well .I tried soft and hard reset couple of time .
Bootloader is working and its v5.15 .
I am totally helpless .
Is there anyway out from here .
I would be thankful . Please help
Hi ...
Seems the upgrade files have been corrupted. Whenever you make a soft or hard reset it trys to flash the ROM. The safest option here since the bootloader is working fine is to get a ROM backup on SD card from any other working device (it doesn't matter what ROM version), but it should be the ROM only. Make sure it's NOT the RSU backup.
Insert the SD card into the device and go to the bootloader screen. It should sense the ROM backup and will flash your XDA.
Good luck ...
Thanks to Cooperative people !
THanks !! ,
Thanks for your help .Especially to Qman and Ronin !, who went out of the way to help me fix my XDA problem .
People like them make this world a little better !
Cheers to them .
Finally after lot of struggle with Ericsson Parallet MP3 Burner which had glitch with windows XP and then XDRIT problem with windows 98 ( XDRIT does not work with 98 ) and then when i used XDRIT with windows XP thru a parallelt port ROM burner it read but declined to write . Even ROM image tool when wrote to the ROM , XDA refused to accept it a CE Rom .
Finally with right leads , I got my XDA working again !!
Thanks for your help and lead to right threads !!
Have a nice weekend and thanks for your timely help .to all who have contributed to this place called XDA forum ...
cheers to all of you ! and keep it up !!
I love this forum! (first off)
HOWEVER, there is certainly a whole lot of info here. Too much to effectively sift through; I know becuase I keep trying. I have a T-mobile Pocket PC 2002, and it works fine. I do however want to be up to date screwing around with new progs and stuff. SO, my question is this..... What is the latest OEM ROM update for Tmobile USA, does it have problems, and is it worth the upgrade? Also, what is this warning about not being able to change your rom to any other rom after updating to 4.x.x? Thanks!
AND how does lumpistephan's kitchen know if you are trying to burn for an MDA I or II? Is it the same image for both? Thanks..... AGIAN!!!! :mrgreen:
Lumpis kitchen is for xda 1.
The warning about not being able to change your rom to any other rom after updating to 4.x.x is partially true.
I made a WM2003 ROM for my XDA I in LumpiStefan's kitchen.
When I upgraded to WM2003, I could not use the SER 1.2, also on this site, to revert back to PocketPC 2002.
I had to use the SD card flash methode to flash back my original XDA OS.
So flashing the ROM the cradle way is not possible, flashing the SD way is
HTH.
i once found this guide in this forum it explain it all in laymans terms
Ok here you go, its a little outdated but its what I still use:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you're going to use a .nbf file you'll have to manually change the "Files of Type" to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
Click to expand...
Click to collapse
You guys (ladies too) are the best! So, I can change my rom after an upgrade to 4.x.x, but not with the cradle; I would have to use the SD method.
One more question?????
Can I back up my existing ROM using my PC/ActiveSync, and leave the image on my PC??? Just in case I need it? I have no idea how to do any of the cradle flashing/backing up, but i'm sure I remember seeing some good threads about it.
THANKS YA"LL
interestingfellow said:
One more question?????
Can I back up my existing ROM using my PC/ActiveSync, and leave the image on my PC??? Just in case I need it? I have no idea how to do any of the cradle flashing/backing up, but i'm sure I remember seeing some good threads about it.
Click to expand...
Click to collapse
Yes, use XDAtools to generate NK.nbf file of your current ROM stored on your PC and later you can use it to re-flash your ROM in case needed ... but if you use 4.xx ROMs you will have to use SD card
So, I've been looking around the web for user reviews of the 2003 Rom from T-Mobile. Apparently it sucks for a lot of people. I wanted to know....
Has anyone had a personal experience with it?
Does someone have a copy I could get from them, if need be?
Does anyone know if the radiostack is good/bad to upgrade to latest version? (I konw it is dangerous, but specificly the latest update)
What would be thought of if I go to the Tmobile store and backup the rom from a PPC 2003 off the shelf, and flash my device with it's image?
Was the malfunctions with the upgrade released by T-mobile related to serial #/ batch, or just Idiot error?
Anything else you can think of?
Thanks again!
about radiostacks then if you dont have any issues with the gsm part dont mess with it
it's a bit sensitiv imho
i used to run the 4.01.00 beta back when i had a xda1 and i never had any issues with it with sd card erasures or anything else
but then nor did i with the 2002 rom i had before
What about grabbing an image off of a 2003 at the store?????
Do you actually know of a store that has a WORKING model for you to get a hold of? The T-Mobile stores here only have empty cases out where the public can see them (and potentially steal them or mess them up). Getting them to allow you to actually touch a working model requires a credit card - of course then you can do whatever you want with it . . . because you own it!
I sell cell phones. I know all the T-Mobile people in this area (the important ones at least). So actually getting my hands on an operational model in a retail store wouldn't be too hard. Even then, Comp USA let me play with a unit once or twice already. SO THERE! But in reality, for most people, in most places, what you said does apply.
I'll let the forum know if I get the image.