Database Users

rom flash crash

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.

The KEY to the White Screen / Radio Upgrade / 1% Hang

I am writing this because the previous posts were very confusing to me and I think, made it seem more complicated than it needed to be. Probably because there are so many variables to this puzzle and it sucks having a potential $300 paper weight.
My apologies if step on anyones toes by reposting this. It seemed like a very pressing issue that A LOT of people are having.
It's not that big a deal, if you have the key.
The problem:
After an unsuccessful radio stack upgrade my XDA had the white screen. Then the unsuccessful upgrade due to the 1% problem.
The situation:
I purchased an unlocked T-mobile, upgraded to the ppcpe2003 4.00.05 off the Yorch site. I am using an AT&T sim card I was experiencing some dropped calls so I thought I would upgrade to the latest AT&T radio stack. I mistakenly ran the upgrade while connected to my Active Sync/cradle connection. Needless to say, the upgrade did not take and I had a dead XDA.
After reading various forum posts I decided to go back to my original t-mobile ROM, luckily, I had saved the nb1 file to my computer using the XDA developers latest tool. After using the bootloader to install from the sd card (holding the power button during a soft reset), I got the perenial white screen. during reboot I saw only the 3.56 (I think) with the radio version indicators coming up blank.
Without that original ROM file I don't think I could have pulled off this save.
Tools:
Hardware:
(1) SD reader
(1) SD Card
(1) Direct Power cable
(1) Syncing Cradle
Software:
1. Your original ROM (I think, it might work with an upgraded one)
2. Radio Stack Upgrade Files (monitor, RSUpgrade, etc.)
The Solution: (long version)
1. I had the White Screen of death.
2. through a series of soft resets, pressing the volume button ( read that in one of the forum posts) I finally got the Today screen to appear. During the boot process I still received empty radio stack info.
3. I had obtained the REPAIR files from this website and prepared those onto an SD card, which was in the unit. The xda immediately went into T-Mobile Upgrade process. I am not sure if the unit went into repair mode because of the sd card or because it was in the start up menu (read further for explaination). DO NOT OVERWRITE THE CARD!
4. the upgrade finally started its process and I got the 1% stoppage problem. After numerous trials and tribulations I was given the solution by MrDollyMaker from this forum.
!!!! THE KEY IS THE FACT THAT YOU CAN USE THE START MENU WHILE ITS IN 1% HANG !!!!
5. While the 1% hang is on the XDA, I clicked the start menu, and got into file explorer. I navigated to the /Windows/Start up/ menu on the device. I CUT/PASTED the T-mobile upgrade program into my documents (just to be safe). And soft reset the device. Sure enough, no upgrade.
6. I put the device into the Sync Cradle and performed a Guest Partnership. Using this partnership, I was able to Explore the device from my PC.
7. Using the PC, I copied the RSUpgrade files from the new AT&T radio Stack A.20.10 from my computer to the devices Windows directory: monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUPgrade.exe
I tried to put these files on the storage card and do the compying in the device itself but I got an access error. It would not let me overwrite one of the monitor files. That's why the Sync connection to the PC is so critical.
8. I took the device off the Cradle and connected the Direct Power Cord and ran the new RSUpgrade.exe file from the device's Windows directory. Everything went swimmingly.
9. Next I re-ran the ppcpe2003 upgrade from Yorch, and I'm golden.
The Solution : simplified
Simplified Steps from White Screen:
1. get to the automatic upgrade screen by soft resetting / pressing volume button.
2. let it get to the 1% error.
3. use Start menu and file explorer and remove the upgrade from the windows start folder (I'm not sure this is required, but it worked).
4. soft reset the device and connect to sync cradle.
5. establish guest partnership.
6. copy your radio stack upgrade files to the devices Windows directory.
7. take device off cradle and connect direct power cord.
8. run RSUpgrade.exe
9. Upgrade PPC OS
Enjoy.
Comments:
- I AM NO EXPERT, just a guy with a newly fixed $300 ex-paperweight.
- You may not have to delete the Upgrade program in the startup menu. I think it makes things easier because you aren't dealing with the 1% error if your device never gets to that point.
- You may not have to go back to your original ROM
- This is my experience with my T-Mobile device purchased in the US. Your results may vary
remember the key: at the 1% error, your device is NOT LOCKED, you can use file explorer.
I would just like to thank everybody at XDA-developers, Yorch, and especially MrDollyMaker who gave me the key to unlock the puzzle.
I hope this helps simplify the matter.
Regards,
Matt
one happy guy...again.

Personally I think this one should get the sticky as it is so oftenly run into by new upgraders!
And not just because I came up with the menu function still working even with the 1% error death bit... 8)
And thanks, Matt for noting that. My instructions were given both from learning on here what to do (the RSU upgrade copying bit) and figuring out how to get past that damn 1% error bit when I forgot to copy one file over of the 4.

Something I found after testing out this method last night several times by causing a bad RSU install and getting the 1% screen of death....
As long as the ROM installed fine, don't re-install a new rom. Simply when you get the 1% error, go to the menu and get in to your file manager.
From there go to your Start folder inside the Windows folder. From there find the link to the RSUpgrade file and delete it. (Don't worry about deleting a file, this is just a link to it and we will re-install a good copy of this file)
Now, restart your PDA. It should return to your normal desktop but with no phone connection as the Radio Stack is not installed. From here, place it back on it's cradle/usb connection.
Just as stated above by Matt, you need a copy of the RSUpgade installation or a ROM upgrade insallation that includes the RSUpgrade. Unpack this, I used Winzip to do this. Find these files:
monitor_ul_bs.m0
monitor_ul_bs.map
RSUpgrade.cp64
RSUPgrade.exe
Now, using Activesync, explore to your Windows folder on your XDA and copy those files from your Computer to there. They must over write all the old files.
Disconnect from your PC and run the RSUPgrade.exe file from file manager. It worked 10 for 10 when I did it this way so it should work for you also.
The key is like Matt stated to remove the RSUPgrade.lnk file from the Start folder in Windows when you get the 1% death screen than manually copy these 4 files over. What I found was happening when you did the upgrade and got that 1% error, one or more of those 4 files corrupted or were not copied to your device. Once it has upgraded the rom, it seems to delete these files automatically also.
Goodluck and thanks for posting all of your experiance Matt. I'm quite sure it will help others A Lot!
MrDollyMaker

I only have two things to add:
1. RSUpgrade _fails_ much more often without SIM card inside the phone;
2. Your battery should be fully charged (100%) before you start the upgrade, since if it does fail, the battery will stop charging, and the next time you attempt to upgrade, you may not be able to get past 1%, even if you have power adapter plugged in. If you happen to have another XDA, you could swap batteries, or use an extended battery, if you have one.
Good luck...

lbazil said:
I only have two things to add:
1. RSUpgrade _fails_ much more often without SIM card inside the phone;
2. Your battery should be fully charged (100%) before you start the upgrade, since if it does fail, the battery will stop charging, and the next time you attempt to upgrade, you may not be able to get past 1%, even if you have power adapter plugged in. If you happen to have another XDA, you could swap batteries, or use an extended battery, if you have one.
Good luck...
Click to expand...
Click to collapse
:shock:
I never do the RSUpgrade with a sim in my phone.... Never failed unless I tried to do it with the EXE thing. But I do agree to make sure you have a full battery, but since it already is at the 1% error, you can charge it with the charger if you do not do anything when the error comes up. just let it sit and charge.
MrDollyMaker

Strange, because at some point I've had consistent failures at 13%, 16% or 21% until I put the SIM card in. Then it worked twice in a row. Maybe just a coincidence.
Also, are you sure the battery charges when the error message is up? The led stays off, and after a while the phone won't even turn on without external power.

Не помог способ с заменой батареи.
The way with replacement of the battery has not helped.

lbazil said:
Strange, because at some point I've had consistent failures at 13%, 16% or 21% until I put the SIM card in. Then it worked twice in a row. Maybe just a coincidence.
Also, are you sure the battery charges when the error message is up? The led stays off, and after a while the phone won't even turn on without external power.
Click to expand...
Click to collapse
Hmmm, every time I plugged it in or sat it on the cradle(USB power modified as listed in this website) the LED turned yellow...
But as for the SIM, yeah, that needs to be in. I was thinking SD card. I never leave my SD card in but as for the SIM, that I never take out.
MrDollyMaker

I have same 1% flash error but no succes
Thank you guys for your effort.
I have followed all the instructions step by step and I still cannot flash the radio part. It's hanging at the 1% even the files required for flash are in the windows device folder.
I have tryed to charge the baterry from the special connector on the back cause it seems not charhing trough the normal connector but I am not sure how long and what should ne the final voltage.
Please advice what should I have to do before I declare my XDA a normal pocket PC( radio part is not working )
Thanks
Silciu C.

I am now in the same boat. I tried every step as per the instruction in this forum, but had no luck at all.'It seemed I also had more problems as I tried to flash the ROM and always got an ERROR message saying that the system could not determine the data connectivity type (this messsage was in the DOS black screen, wheneever you run the Programme A/ xdatools). However, I could back up the device and the Active sync seemed to be working fine ...
I hope someone could help us ...thanks a lot in advance..
cheers...

Re: I have same 1% flash error but no succes
codectelecom said:
Thank you guys for your effort.
I have followed all the instructions step by step and I still cannot flash the radio part. It's hanging at the 1% even the files required for flash are in the windows device folder.
I have tryed to charge the baterry from the special connector on the back cause it seems not charhing trough the normal connector but I am not sure how long and what should ne the final voltage.
Please advice what should I have to do before I declare my XDA a normal pocket PC( radio part is not working )
Thanks
Silciu C.
Click to expand...
Click to collapse
Ok, first thing you need to do is turn your unit on and let the 1% screen of death come on than stop and do not do anything!
Next click in the upper left corner where the menu comes down. It will still drop down. Find your File Explorer program and launch it.
Now, browse over the the Startup folder located in your Windows folder. Inside the startup folder you should find some file refering to install or upgrade like "RSUgrade.lnk" or something like that. DELETE IT. Now let your unit reboot.
Now it should return to your normal desktop. go in and find those 4 files that caused all this hell and delete them. They are as follows:
monitor_ul_bs.m0
monitor_ul_bs.map
RSUpgrade.cp64
RSUpgrade.exe
Now that you have deleted those files, just to make sure they are cleared from memory restart the unit again.
Download a good copy of a radiostack that works with your location from yorch.net. If you wish to get the latest one, I would suggest that unless you are with T-Mobile, stay clear of it. You can also extract these 4 files from an upgrade patch file from your provider using WinZip.
Once you have a good copy of those 4 files copy them directly from your PC to your unit through active sink and into your Windows directory.
Restart your unit to clear any programs out, plug the unit in to your ac charger (not the cradle and not connected to your pc) than using File Explorer locate RSUpgrade.exe and run it. This will restart you unit but should have no problems upgrading your unit.
If you prefer, after you get it back to desktop, stop and charge it than copy the files over.
MrDollyMaker

andhy said:
I am now in the same boat. I tried every step as per the instruction in this forum, but had no luck at all.'It seemed I also had more problems as I tried to flash the ROM and always got an ERROR message saying that the system could not determine the data connectivity type (this messsage was in the DOS black screen, wheneever you run the Programme A/ xdatools). However, I could back up the device and the Active sync seemed to be working fine ...
I hope someone could help us ...thanks a lot in advance..
cheers...
Click to expand...
Click to collapse
Safest way to upgrade the ROM is using the SD card method. It is more reliable and doesn't get Errors caused by activesync.
MrDollyMaker

MrDollyMaker:
SD method has not worked for me so far...
I am not able to patch 5.17 nor downgrade to 5.15.
I used xdarit and osimagetool to write to the SD card without any luck.
Could please share some light in this matter?
Cheers...

andhy said:
MrDollyMaker:
SD method has not worked for me so far...
I am not able to patch 5.17 nor downgrade to 5.15.
I used xdarit and osimagetool to write to the SD card without any luck.
Could please share some light in this matter?
Cheers...
Click to expand...
Click to collapse
Have you tried using the OS Image Tool to write directly to the ROM?
Also, when you used XDArit, did you select that it was 5.16+ image you were writing? (when you used/didn't use the patch)
MrDollyMaker

MrDollyMaker:
Thanks again.
Yes, I selected the 5.15 ROM image to write to the SD card.
The OSImage file only accepted nb1/ nbf file types. I was not able to write the wallaby patch tool nb2 file nor wallaby 5.15 ROM image nb0 file through Osimagetool.
As you might remember, I always got an ERROR message about activesync connection whenever I tried to flash directly to the device ROM.
The first step I believed is to patch the 5.17 then either downgrade to 5.15 or go straight with the nk.nbf flash.
Is this correct?

1% ERROR PERSIST
lbazil said:
I only have two things to add:
1. RSUpgrade _fails_ much more often without SIM card inside the phone;
2. Your battery should be fully charged (100%) before you start the upgrade, since if it does fail, the battery will stop charging, and the next time you attempt to upgrade, you may not be able to get past 1%, even if you have power adapter plugged in. If you happen to have another XDA, you could swap batteries, or use an extended battery, if you have one.
Good luck...
Click to expand...
Click to collapse
I am in situation that I still have the 1% error even I have followed all the instructions from the forum.
The power led is not lightning and I can confirm that is not charging the batery. I have tryed to charge the battery using the special hole from behind but still no success.
Do you have an oppinion?
Thanks in advance,
Silviu C.

Re: 1% ERROR PERSIST
codectelecom said:
I am in situation that I still have the 1% error even I have followed all the instructions from the forum.
The power led is not lightning and I can confirm that is not charging the batery. I have tryed to charge the battery using the special hole from behind but still no success.
Do you have an oppinion?
Thanks in advance,
Silviu C.
Click to expand...
Click to collapse
One question..... What "special" hole are you talking about?
MrDollyMaker

andhy said:
MrDollyMaker:
Thanks again.
Yes, I selected the 5.15 ROM image to write to the SD card.
The OSImage file only accepted nb1/ nbf file types. I was not able to write the wallaby patch tool nb2 file nor wallaby 5.15 ROM image nb0 file through Osimagetool.
As you might remember, I always got an ERROR message about activesync connection whenever I tried to flash directly to the device ROM.
The first step I believed is to patch the 5.17 then either downgrade to 5.15 or go straight with the nk.nbf flash.
Is this correct?
Click to expand...
Click to collapse
Ok, since you have a 5.17 BootLoader, you can't use the 5.15 image write. You have to use the 5.16+ due to it is coded differently. When you write the SD card, include the patch for the 5.17 BootLoader as well with the rom so it can bypass the security feature.
MrDollyMaker

T-Mobile/MDA/O2/yadda yadda....
You know, I feel like I should be getting paid for all this advice! 8)
(J/K!)
MrDollyMaker

thanks for the advice again.
I am getting confused, really. Just repeated the same thing over again and again the past 3 days and suddenly I managed to patch the 5.17 for the second time (after over 50 tries). THis time I kept the SD with the patch tool and got another SD card to try to write 5.15 in it. After 4 hours, I managed to got it written then eventually downgraded the wallaby to 5.15. Now, the challange is the device is stuck in the wallaby screen everytime we turned it on. I had about 10 different ROMs originals as well as cooked ones from the kitchen, but had not been able to "write" one in the SD card. I used all OS image tool as well as xdarit, without any luck. the device wont recognized the ROM in the SD. I think the Wallaby 5.15 is working fine as I tested with the other SD card with the patch tool in it, the device still recognized the card as a diagnostic card.
I cant think of any mistake that I might have made in the procedure as I had (I think) followed every step of the procedures and had read different postings over and over again. :?

SIM LOCK

HELP .. HELP .. HELP ..
I know this subject is old but I could not what I need & how can I fix it
I have bought a pocket pc with phone edition from USA, and when I tried to insert my SIM card it asked me to but my PIN code, then ask me to but the unlock code (SIM code).
Now I am in Saudi Arabia.
WM2003
ROM Versino: 4.01.16 ENG
ROM Date: 02/04/04
Radio Version: 6.25.02
Protocol Version: 324e4
NOTE: I do not have a serial cable.
Thanks,
HFN[/b]

Check this: http://wiki.xda-developers.com/wiki/UnlockWiz
Hope it help you
Edit:
You have a WM 2003, this link work only for PPC2002

SIM Lock
DariusVE
Thank you for your help, I have tried this site, but It did not work because my device using WM2003 and also has no Wireless Modem feature.
Thank you.

Unlocking Quest
Here's my quest to unlock my T-Mobile PPCPE. I think some of this information might be useful to anyone confused about getting this
done.
First I called TMobile to request the unlock code. Since my account was up to date I figured no big deal right? WRong. My IMEI (or TMFT) number was not in their database so they could not give me an unlock code so they said. They told me to call the manufacturer of the device which they said was Microsoft. Knowing full well this was crap I called anyway.
The support guy got a good laugh; MS does not make devices
like this, they only provide the OS. He recommended I call Siemens.
So I did. Real nice guy named Jack had a good laugh as well. Not only could Siemens not tell me who really made my device (a third party made them for T-Mobile) but even if they had unlock codes they could not provide them because of contracts with TMobile. So I go back to TMobile.
The support people felt really bad about the run around and escalated really high up the chain (or so they said). AFter 48 hours I decided to take my own course. Having had good luck unlocking a Treo 600 through 'alternative means' I figured time to tackle the Pocket PC Phone Edition.
This was MUCH different and much harder to figure out.
After a good 12 hours and a whole slew of reading I finally figured out some stuff. Most of this may seem a no-brainer to some of the more educated XDA people out there but for us newbies maybe it will help.
----------------------------------------------------
The PDA side of the ppcpe and the radio/phone/gsm side are two totally different animals (not a surprise to some). When you refer to the 'operating system' you're talking about the ROM
like the XDA Developers special edition or any of the ROMs from the ROM kitchen at http://lumpistefans.dyndns.org/. The Radio or RSU (for Radio Stack UPgrade) is totally separate from this. The other variable is the bootloader version (Wallaby in my case).
Now my goal was just to use the XDAUnlock program. When I ran the program right from the defaults I got 'error getting unlock code.' All the posts I read said put on the special edition rom and you'll be fine but that did not do the trick. Still got the same error message.
Here's what I started out with:
ROM: 4.01.16 ENG
Radio: 6.25.02
Wallaby booatloader: 5.22
What finally worked:
Radio: 6.24.00
ROM: 3.17.03 ENG (xda special edition)
then upgraded bacdk to 4.01.16 ENG
Wallaby boot loader 5.15
How I did it
--------------
I meandered my way through this to eventual success and since the dratted device now works fine I'm leery about putting it all back to the old way and doing it all over again. Therefore use this process as a guide only, not a definitive instruction set. Also I walked through this as a troubleshooting exercise so some steps may not have been necessary. I eventually succeeded but maybe went the long way around to do it.
References
----------
- Bootloader utilities: Get to this by holding down the power button and pressing soft reset. You may have to hit the contacts button to get into the menu if you don't see it right away (like if you see a simple GSM OK message at the bottom of the bootloader display.
- Cold boot: the reset swtich on the right side bottom of the device with a picture of a red battery with an \ through it. This disconnects the batter from the mainboard and trashes all the data on the device except the Operating System in ROM.
What I grabbed
------------------
- XDATools
- XDARit
- ActiveSync (I used 3.7.1) and connection by USB cable
- Wallaby bootlolader version 5.15 files
- XDA Developers Special Edition ROM
- RSU 6.24.00 files
- XDAUnlock.exe
- SD Card (mine is 128 MB but I think as long as it's bigger than 64MB or your current memory in the device you're OK)
- pnewbootflash_40116.exe
All of these files are available here on xda-developers.com, just
search for them.
First back up everything. Not just using the sda backup tool, from the boot loader. You can do the SDA backup if you want, consider it backing up your data. You can also do the ActiveSync backup if you want to save your data. In my case all my data is stored in Domino so I don't
give a hoot about the data on the device. Your mileage may vary!
Second I'm doing ALL of this with no SIM chip in the device. THis may or may not be necessary.
Stick your SD card into the PDA. If it complains about wanting to format it go ahead and let it format the card unless you have stuff on it you want. I'd recommend dropping anything you want from the card onto safe media and just working with it as a blank the rest of the way through because it's easier to just wipe the card in between some steps.
Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button
if when you get to the bootloader screen you see nothing more than
some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader.
Bring up xdarit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'wallaby' in the hex codes at the bottom of the XDARit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT).
Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.'
Type 'pnewbootflash_40116 nbl515.nb0' to write the wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0'
you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
Now..why did I downgrade the bootloader? At this stage I'm troubleshooting why I get the 'error getting unlock code' message running XDAUnlock. I've got three variables I know of, bootloader, ROM and Radio Stack. I chose to start with the bootloader because
some posts out there say boot loaders 5.17 and higher have some checksum that keeps certain ROMS from working properly. Perhaps if I'd started with the radio stack I'd have been done right away and saved a few hours but all the posts about possible device destruction made me start with the bootloader! Again, your results may vary!
Next I changed the ROM to the XDA Developers special edtion.
Make sure the SD card is in the PDA and cradle it.
Run OSIMagetool and load the ROM file in the first box, chose SD Card in the second box.
If you downloaded the special edition ROM you might
have some luck using the Installer that comes with it but apparently that
does not work with ActiveSync 3.7.1. I got messages that said it could not access the device or no connection etc. Instead I used OSImageTool to load the NK.NBF file included in the distribution. Note that to get to this file you DO have to unzip the EXE file you download!
Once complete pull the pda out of the cradle.
Hold power+soft reset to get the boot loader menu. This should show up as 5.15 now. It will automatically detect that the SD card contains a ROM that can be flashed to the device. If for some reason it does not automatically detect this maybe you have to hit Contacts. I did not have
to do that, it just told me to hit Action to download the ROM.
Hit Action button (aka the jog button) to write it to the device. This will take a few minutes, go grab a beer or two or three. I took the safe route and connected power to the device while writing the flash.
Once it's finished cold boot the device. I waited 2-3 minutes before re-engaging the battery.
Here's a gotcha. On the right side of the SIM there is a little switch. If the rubber door for the sim is not totally closed you can't get the device to boot. This switch is real small so it's very possible to miss it. You can see it fine if you take the back off the device (which I determined from a post here that told you how to get the battery out).
When it boots you should have the 5.15 wallaby booting the xda special edition. Follow the instructions to calibrate the screen and you're ready to move on.
Now if the radio is 6.25.02 xdaunlock won't work, it just generates the 'error getting unlock code' message. You have to downgrade the radio to have this work.
There's lots of posts around here that say don't screw with the radio because if it errors you've got a fried device. I imagine this is true so balance how bad you want to unlock the device against the possibility of totally frying the device. I've done two radio upgrades in my life on the PPCPE, both were OK but again, caution is advised.
Grab the 6.24 radio zip and unzip into a folder on your computer. Use activesync to copy the files to \windows on the device.
Execute the rsupdate.exe program to reprogram the radio to 6.24. WHen completed soft reset the device and go into start-settings-system-device info to make sure you're at 6.24 radio vesion.
Copy the xdaunlock.exe to the device and execute. It should say 'you're device appears to be SIM Locked, would you like to remedy this?" click Yes to unlock the device.
Now the device is unlocked. You can change the ROM to WM2003 now if you want (which I did). I imagine you can re-upgrade your bootloader
and radio stack if you want but I'm leaving well enough alone for now!

Hi ALL
I did unlock my phone thank you all.
Spicial thanks to "rhodwyn".
Best regards.

Works!!!
Thanks !!! Its working!!!

help in getting all the files needed....
Hi,
I would like to try this.... but where can I get the file pnewbootflash_40116.exe? Or is this a file that I'll create?
rhodwyn,
I would appreciate some help in getting most of the files.
Thanks in advance.

It worked for me too, thanks for the great solution, rhodwyn!

Thank you rhodwyn and everybody... my 2 cents
I love this site and I think that everybody does a great job. I found rhodwyn’s post to be very comprehensive and it is the one that ultimately helped me out this time. I don’t know if anybody is even interested anymore, but since I’ve been helped, I figured that I’ll try and help someone else. I assume that you’ve already read rhodwyn’s post.
I had the same starting configuration. I did everything that he suggested except for changing the bootloader and it worked perfectly. So, as he suspected it was enough to downgrade the radio stack and to load the special edition ROM. I subsequently upgraded my ROM and all is good (although I haven’t upgraded the radio stack and I’m not sure if I will).
I’ve read other posts about problems downgrading and upgrading the RSU and the 1% problem… I had a problem the first time I tried and I became very nervous, but I looked at rhodwyn’s post more closely and placed rsupdate.exe into PPC’s \windows folder and tried it again and was successful.

thanks
rhodwyn
10 minutes and done

Radio Stack Failed? HERES HOW TO GET YOUR XDA BACK ON TRACK!

(mods i would appreciate if you could make this a sticky for people... ive worked long and hard trying to get this thing working again)
Ok so heres what happened to my XDA which proberly happened to yours.
I went onto the 02 site and got the latest radio stack upgrade for my xda, but i didnt have the sim in my device so once it finshed and restarted the xda it crashed because there was no sim in it. So i hard reset it.
Causing it to hang on the boot screen showing the G & U letters on the side for about 4 minutes before booting to a blank screen with the keyboard icon in the corner.
*** Please remember at the moment my status LED isnt working showing there is no battery (but still booting etc - P.S i have installed a new battery - no diffrence) ***
Heres how to get it working...... remember that everything takes longer because the XDA lags like mad.
Ive created this guide myself ive took nothing from anyone else info ive done this from scratch, it will need to be done everytime the machine runs out of power (hard resets).
---------------------------------------------------------------------------------
* when i put " + " it means AT THE SAME TIME e.g button1 + button2 = keep pressing them at the same time.
** I refer to the directional keypad centre button as the "OK" button.
Make sure you have the correct RSU Version from here :>
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
Download it and put the files onto an SD card.
1. Boot up the device
2. keep pressing the OK button + volume button until it shows the today screen, please note there will be no titles on the screens, HENCE NO START BUTTON.
3. Then press the contacts button + THEN OK a few times, then press the OK button this should bring up the start menu
4. CLICK programs, file explorer, select the SD Card. Then Copy RSUPGRAD.exe to : my device > windows>start up.
5. Copy the remaining 3 files to the : my device > windows
6. Soft Reset Device
7. Click on start (on the upgrade util) it will then restart the device because theres no LED for the battery (hence the 1% then fail).
8. Once started it should then start up as it did when it came out the box giving you the windows setup screen.
9. Go into file explorer and delete tha flas util file from the startup.
Thats it!
- Remember if you hard re-set the device again it will need to be re-done, i dont know how to solve this problem LONG TERM, im giving my XDA to 02 to fix it...... been as its there screw up.
----------------------------------------------------------------------
Thanks Everyone
James

Does this actually flash the gsm radio? If it does then why does it need reflashing following a hard reset?

No it doesnt re-flash it.............
All i know is that it fixes it and many people have had the same problem but had no replys so id thought id help them out :roll:

Where are he diffreneces to the instrucions on wiki????
Stefan

huh? so your saying someone has already written the instructions?
Do you have a link? it will be intresting to find out how i can get my LED working again so the system will be able to work once more.
EDIT: IF THE BATTERY LED/STATUS IS UNKOWN (as in my case)
"Maybe the upgrade will stop again at 1%, this may occur when you have an empty battery. "
Does not apply to you............... hence why my guide overcomes the one on wiki.
If you have had the situation happen to you, then you would undertsand.

would it be possible to use the xda developers 1.2 special edition ROM instead of the 1.1 version for this procedure?thats the only rom i seem to have found.

Boogie, I think you need only the radio stack not the rom if I read the post correctly. The special edition rom contains NO RADIO STACK.

That´s not 100% correct. I´ve noticed, that some ROMs wouldn´t boot up so that you can follow the procedure.....
Stefan

hey guys this is my 1st post to this forum, but for the last year or so I've found it very helpful.
I was experiencing this same issue it would just boot up and hang on the welcome screen for what seemed like an eternity. I gave up and just left it booting up and finally the today screen came up. This is what I tried and it worked. All of this was after a hard reset when I tried to upgrade the radio stack and it fell into this infinite loop of 1% and fail and reboot. I had read a couple of the procedures for doing a radio stack upgrade but here is some of what I did.
In one of the procedures it says to copy the files to ur ppc windows directory and to copy the exe file to ur windows startup directory. I figured I would bypass that in some way. After I finally got to the today screen and used my pc to copy the files to the sd card, I copied all the files to the windows directory on the device and ran the exe file from the windows directory. It worked like a charm and my ppc was back to life. It no longer took for ever to get passed the welcome screen. I hope this helps some of you that have this issue

Device extremly slow[Solved]

Hi all,
When i used my device this morning i could not start messenger or any other program. The device is also unable to connect with active sync. I haven't got anything installed over the last days.
It just happend. Windows is extremly slow, i don't have contacts anymore, no pim's or anything. The phone did remeber my last calls and such. My email accounts are also missing.
I have done some soft resets and now the device is stuck on the windows mobile splash screen (the green screen with windows logo and name).
I don't know what to do How can i get my device to work again?
Edit
The device has started after 20min at windows screen. Touchflo 2D has not loaded and i can not make calls. I can't start any program, it gives an error that the program can not be started because it has not been signed with a certificate or some component is missing.
Thx in advance for reading.

If you have an SD card inserted I would try removing it and see if that improves things!
I had a similar problem with an Xda Zest which turned out to be a corrupt SD card. Once it was formatted again everything was bach to normal.

I removed the SDcard, tried another one (also 4GB), then used the old one again (formatted) .
But no luck.
I will try again removing some software if the device allows it. Will update.

dont put any SD card in the device
and try
Start/configuration/sistem/Erase memory
and there just put 1234 and press yes
This metod erases everithing from your device leaving it just how it came from the factory

You may also perform a hard reset as you have mentioned to receive a message "some component is missing". Hard reset should fix any software (or Operating system) issues with your phone.
WARNING: Hard reset will erase all your data and the customizations you have made to the phone.
Refer to the following for instructions on how to hard reset:
http://forum.xda-developers.com/showthread.php?t=453324

I have done a hard reset without the SD & sim card. It solved all the problems. I was able to recover my contacts with ActiveSync.
Thx all for helping