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.
Related
I was curious. I've noticed people said that if you put the 4.00.16 ROM on, the only way you can downgrade it, is if you reprogram the ROM from the SD card and not by the EXE method.
I was curious as to WHY? What does that .16 ROM do to the XDA to prevent you from doing an EXE rom reprogram?
So far, we lacked time to look into this one. Tell us, and we'll see if we can fix it.
Downgrade unseccesful using SD method from 4.00.16 ver
Sorry if this is OOT: I'm a non techie person so please somebody explain me how to use the SD card reflash metod to downgrade from 4.00.16 bact to 4.00.11 version. If write the new rom to sd using XDAtools it's done. after it I put it back the SD card back to the XDA. I enter the wallaby 5.17 screen by pressing power+ soft reset button. It said wait and then GSM ok after that freezze.
What I'm missing?
The why, I can't say as I have not investigated in detail, I just said to heck with it and bought a SD writer.
What happens after you load 4.00.05 and 4.00.16 is when you try to run and upgrade/downgrade/re-install from Prgramme-A or the newer programmer that came with the 4.00.x installs it fails saying it can't connect to the device, please check to make sure it's plugged in (even though there is a active connection with Activesync).
Using the SD card there is no issue with running the upgrade.
-rich
but what is it that .16 has that .11 doesn't that stops you from changing ROMs via the EXE method?
Also, after putting on .16 and you go back to say .11 via the SD boot method, are you able to use the EXE method to change ROMs after that?
Currently I use the AT&T A20 radio stack and was thinking about trying out the Tmobile 6.24 to see how it works out. Haven't decided yet.
Investigating the no reflash .EXE method
Ok I have found a roundabout method to resolve this only using the .EXE method.
I used the rom kitchen to generate me a 4.00.11 ENG WM2003. After flashing my phone and wanting to make sure i could revert I tried my origonal o2 provided flash upgrader "Radio_Unit_Upgrade_v31413.exe" and the latest downloaded one from the o2 website "Radio_Unit_Upgrade_v31703.exe" neither of which would let me flash them - i get the error "this rom is not for this device" (or some such).
I went back to the rom kitchen and built myself a 3.17.03 ENG O2-Euro rom image and flashed that onto the phone. this suceeded where the o2 stock .EXE failed and I was nearly back where I started.
Now that I had my rom kitchen 3.17.03 back on I tried to install the latest "Radio_Unit_Upgrade_v31703.exe" file again and was greeted with sucess once more!
The question this begs is the same as the origonal however, ok we can get the stock provider rom back on - but why will it let me flash the rom kitchen 3.17.03 back on and not my o2 downloaded rom? Hopefully the developers will be able to spot whats going on and sort it out in the kitchen (hopefully removing what ever right protection the new rom installs).
Hope this helps, shout if you want me to test with a specific rom version (for uk / europe phones) and ill give it a whirl for ya
I think the "official" rom checks for versions, whereas the roms from the kitchen use a modified bit of code called "adaptrom" to fool the software. I wish I had a tenth of the capabilities of the guys on here that work out all this stuff.
cruisin-thru said:
I think the "official" rom checks for versions, whereas the roms from the kitchen use a modified bit of code called "adaptrom" to fool the software. I wish I had a tenth of the capabilities of the guys on here that work out all this stuff.
Click to expand...
Click to collapse
I'm not sure about this, but i will give you some hint, ok :?
The T-Mobile Rom has a protection to it that you can not upgrade any ROM except T-Mobile ROM's other than that if you have a version of rom that is not T-Mobile ROM you can use the adaptrom to normally update any kind of ROM because adaptrom ignores the Version like PW10A1:007, the explanation of this versioning is in this forum(some kind of country and GSM band 1800/900, 1900/900).
Now why we have to use SD card after we update T-mobile ROMs, if we want to change to another kind of ROM's, because if we use "exe" or sometimes we called it "Program A" it checks the version of the ROM's, since the adaptrom can ignore only the version of the ROM's it can ignore the Type of ROM's, if it is T-Mobile or other ROM's, now for SD card it doesn't check for any version or type, and it goes directly to updating the ROM's in the Bootloader way or we can call it forcely updating the ROM'
s.
Hop this help.
Hi Guys,
I need your help .
I've downloaded the 4.00.16 ROM by mistake, it really didn't tell the ROM number, so now I want to revert to a earlier one and I can't.
I've got the following message: "ERROR: GetDeviceData - An established connection was aborted by the software in your host machine.
error getting devicedata"
and then
"ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR. Cannot execute the remote communication program. Please make sure that the USB/Serial cable is properly connected."
Stupidly, I haven't got a SD card. :evil:
PLEASE HELP ME, I'M REALLY STUCK NOW AND DON'T KNOW WHAT TO DO...
Read the above post that starts like:
"Ok I have found a roundabout method to resolve this only using the .EXE method"
HTH
Qman said:
Read the above post that starts like:
"Ok I have found a roundabout method to resolve this only using the .EXE method"
HTH
Click to expand...
Click to collapse
Hi Qman,
No matter which ROM I cook, when I try to install it using the .EXE it gives me the message I posted before.
Would you explain to me, idiots guide, how to flash not using a .EXE?
or, have you got any sugestions?
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 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.
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.
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