Database Users

Burning ROM - phone not working

Hi, I'm hoping to get some help with cooking and burning ROMs to my o2 XDA.
My original product specs are:
ROM Version: 3.20.06 ENG
Radio version: 4.21.01
I cooked and then downloaded 4.01.00 ENG from Lumpi Stefan's site, then ran the rom.exe file that it produced for me. Everything worked fine, and then I rebooted my XDA. Upon first boot the phone appeared to work, but after performing a soft-reset because the XDA froze, all of the phone functionality appears to be not working.
When I do a hard-reset I get: Wallaby Bootloader v6.22 - GSM OK which I think looks good as far as the phone functionality is concerned. Looks like it's the OS that's on the XDA which is causing the phone difficulties.
I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started!
I don't have an SD card, and am in dire straits about getting my phone to work. Is it possible at all to get this to work, or perhaps to go back to my original ROM (I backed it up to orig.nb1) using XDAtools. Anytime I try to burn the .nb1 file back to my XDA it fails. Or is the ONLY way to get an SD card and use the Bootloader technique? I even tried downloading the 3.17.03 ROM upgrade directly from the o2 sitebut it fails.
Any help will be GREATLY appreciated.
Thank you.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![/qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![\qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

Thanks, I will try. ActiveSync still works...
I notice you are running the same ROM version as me - sis your radio still work?

Can you verify that I am trying to Flash the ROM correctly?
1. Confirm that I have orig.nb1 - yes, it's there - backup of original ROM before I started this whole dilemma.
2. Ensure that XDA is Activesync'd - yes, as "Pocket_PC" - all working okay.
3. Right click on orig.nb1 and select "burn"
4. OSImageTool.exe then pops up and copies orig.nb1 to Programme A.
5. A DOS box then appears saying "ERROR: GetConnectionType - A
ote host. error getting connectiontype".
6. Programme A then runs and after pressing "next" a couple of times, I get an error - "Error 011: Cannot execute the remote communication program. Pleace make sure that the USB cable is properly connected."
And that's basically it.
I have tried different variances of this, but all without success.
Help!
BTW, I'm logged in to MSN Messenger now, could you let me know when you're online - or anyone else, for that matter. My address is [email protected]

This message means that the current ROM in your XDA can't be flashed through Program A ... not a big issue, for unknown reason it happened with me few times ... but now you have to use SD card to flash your ROM.

Here is an update...
I have played around some more with the XDA with no success. I have now bought a 64MB SD card and am unsure as to how the ROM image on my PC gets onto the SD card. This is how I have been doing it:
1) Insert SD card into XDA
2) Place XDA into cradle
3) XDA then ActiveSync’s to the PC
4) Run OSImageTool.exe and select the following –
a. Source: “C:\Documents and Settings\Paul\Desktop\orig.nb1”
b. Destination: “XDA SD card slot – unknown size”
5) Then I press “copy” and I see the progress bar go across to 100%. After this appears to finish, the program just sits there not telling me it’s finished. I assume that it’s all okay and I then close the program
6) Take XDA off cradle and hold power button down whilst doing a warm-reset
7) The following appears: “Wallaby Bootloader v6.22 – GSM OK” – nothing else happens, and from what I have read it is supposed to ask if I want to perform a ROM upgrade. However, I can get into the diagnostic and flash tools by pressing the action button etc, but nothing is in there to upgrade the ROM.
Does the fact the OSImageTool destination says “XDA SD card slot – unknown size” matter? I’m assuming not because when I have transferred the ROM using the above steps, the XDA asks if I want to format the card; meaning that the transfer worked okay. Do I have to have an SD card reader/writer on my PC to get the ROM onto the SD card?
I have read a little about a Bootloader patch – do I need to run this, and how do I get it onto the XDA – using the same method?
I would be very appreciative of any help that can fix this, as all I want to do is get my three-day old XDA working again!
Any other comments and help in relation to solving this hair-challenging issue would be great!
Thanks,
Paul…

Ok ... from what you wrote it seems your doing it correctly. However, I have doubts on the file orig.nb1 you are using ... maybe it wasn't copied properly.
Try to cook any ROM (TMO 4.01.00 is good) at Stefan kitchen and you can cook it as .nbf or EXE then extract the .nbf file using winzip or winrar.
Follow the same steps and let me know.
Good luck ...

Is bootloader v6.222 okay - will it allow me to overwrite my current ROM with this new ROM that you are suggesting? I have read that I may have to downgrade my bootloader to do the SD ROM writing thing.

I can't confirm that my self ... I used SD with 5.17 and 6.22 without problems but maybe it's my luck
Cook the 4.01.00 as EXE and try it as is or extract the .nbf file and use the SD method.

Okay I'll give that a go now... Will let you know how I go...

Nope - didn't work. I'm not getting a screen in the bootloader to update the ROM via SD - if I press the action button I get into dignostics...
Is this a bootloader issue, and if so, how do I downgrade?

Also just tried the following:
C:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
And got the following error message:
Unable to find flash info offset, cannot disable bootloader writeprotect
Any ideas?

I don't get it ... you cooked and downloaded and tried a new nbf file for TMO 4.01.00 in less than 15 minutes ??!!!!
what is the nbf file size ??

Yes, I used Winzip to extract NK.nbf. It is 31,745kb.
I am now cooking on Lumpi's site a zipped NK.nbf file and will try that too...

XDA-Developer DOES not work, why?

I have a SX56 and the carrier is AT&T USA. The following is the device information:
Rom Version: A.20.17 ENG
Radio Version: A.20.10
I needed to unlock this phone so I could switch carriers to T-Mobile, the rest is a waste of time, the following is what I have expereinced:
1- I read about a dozen articles in the forum with different problems, so that I get the hang of things before even I proceeded with anything
2- I then read the material under XDA-developer and downloaded two files:
-- XDAunlock.exe which does not expand, the error message from XP pro is as follows:XDAunlock.exe is not a valid win32 application!
-- XDA-developers-SER-v12.exe; I executed this file, it established a connection through my USB cradle and proceeded to upload the new image.....!!!!
This is where things are stock; the message on the screen is Loading while the commiunications has stopped. So here is what I did:
1- Back to the forum and found a document on the similar problem, I tried the Softreset+On button and I do get GSM ok an Versin 5.15, My screen is distorted with line going through it, just like the article that I found
2- Downloaded XDAtools-jeff.exe to see how I can rebuild this bootloader on the SX56, epanded the contents and run:
pnewbootloader.exe bl515.nb0 in a dos window, the window is non-responsive.
Bottom-line: The Sx56 has lost communications with the PC, its screen is frozen while updating and is totaly distorted. Is there help avaiable on this site is with instruction that I could follow if any!!!
Where do I go from here? Please help.
Thanks

Xdaunlock is a pocket pc app and does not run on the desktop, it should have been copied to your xda and executed from there using explorer to find it then double tap. There is nothing wrong with your bootloader so the bootloader patch does not apply to you. You need an sd card and sd reader writer, you then need to use xdatools to write a rom to the sd card, once you have done this you need only put the sd card in the xda, push the stylus in reset hole while holding power, you will be asked to press action key to program rom, you will then have a working xda.

If I'm understanding you correctly, then the reason the not valid win32 app. is because you need to install this to the phone by copying to the device. It cannot run from the desktop computer.
Also as far as the bootloader part, I'm not well versed in the bootloader but in my experience whenever I've updated my sx-56 to a new rom I've had limited success with the computer run updates. I suggest you get a secure digital card reader and search this board for the step by step instructions on how to use xdatools.jeff to copy the new rom to the sd card and then enter the wallaby boot loader to update directly from the sd card not from the computer. I hope this helps a little.
Mike

i want to downgrade from the wm2003 upgrade to the o2 rom

Ok, i konw there's already been several threads here about downgrading from the wm2003 rom (4.01.16ENG from the rom kitchen to be precise) but i can't seem to get this thing anywhere... as i said i upgraded the rom to the one specified above and found it far slower and unstable than the ppc2002; I wanted to flash the xda with the old rom but there's this strange communicate saying that the connection has been suddenly closed and the "programme a" stops. i tried to flash the old rom directly to the device using the xdatools but also with no success... it keeps on saying that it couln't communicate with the remote application... well then i thought about this bootloader fix (still unsure what bootloadre i have because i can't get the info anywhere) and it said that the memory on the device is write protected.... :/ well, and as for now i am waiting for a sd card to try that, but.... tell me, will the xdatools prepare the card if i insert it into the device? (i have no card reader for my pc) i am woried because each action i take (except normal device usage - activesync, copying and moving files, installing appz) that messes with the roms, shuts down the connection and i have to unplug the device from my pc and plug it again... please help me, i'm in dire need!

I am having a similar problem with the same rom version. I wish i never used that version! I did an update to wm2003 earlier and i could go back and forth with no problems, but this one is a real nasty one!!
the message i get when using osimagetool:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype

I am having the same problem ..
and when i power on/off the device it says (Unrecognized Card)
Enter the name of the device for this card. For information, see the card manufacturer's documentation.
and there is a place where i can write something (Unknown card in socket 1)

m112a said:
I am having the same problem ..
and when i power on/off the device it says (Unrecognized Card)
Enter the name of the device for this card. For information, see the card manufacturer's documentation.
and there is a place where i can write something (Unknown card in socket 1)
Click to expand...
Click to collapse
YES!!! Same here!!
How about the phone? I cannot seem to turn it on. When the pin screen comes up it says i should turn on the phone, but i cant dothat anywhere..

Hi All,
The best option for ROM upgrade is always the SD method ... it's much easier and safer. XDAtools doesn't work with some ROMs because of the boot loader version not the ROM itself.

So what do you say guys? will i be able to downgrade it from the sd card? - and first of all, prepare the card having it inserted into the xda itself and using xdatools? i also wish i had never used it, the newest ppc2002 rom from o2 is just soo cool comparing to the wm2003 one i'm stuck with right now...

ROM Upgrade

Hi,
I have a T-Mobile Pocket PC Phone 2003.
Rom version: 4.01.16 ENG
Rom date: 02/04/04
Radio version: 6.25.02
Protocol version: 324e4
Wallaby Bootloader: V5.22
I am in a GSM 1800Mhz region while the phone has only 900/1900Mhz. I have read various reports that with a Firmware upgrade I can make the phone Tri-Band capable meaning 900/1800/1900Mhz. There have also been reports that this is a hardware feature which will not be effected by software upgradation. But I wanna still try. Firstly the phone was Simlocked by T-Mobile which I managed to unlock with a code given by their SimUnlock dept. believe it or not.
The problems / issues I am facing with this phone are:
1. Downloaded the XDAROM.exe with adaptROM.exe Program A.exe etc in it but it always stops at the dreaded -
ERROR: GetDeviceData - An existing connection was forcibly closed by the remote host.
error getting devicedata
For the above I have tried all the suggestions on this forum like hard booting (battery off/on), Select GSM900 in Wallaby Mode then reset, Remove Sim Card then Reset, Switch off Radio (which I presume is GSM) in Wallaby then reset. All options lead to the same error.
2. Tried backing up the current ROM in Bootloader Mode which it does and asks me to press the Action key. But when I reboot the device or remove the SD Card and plug it into a PC it says Card not formatted. The SD card
works under normal conditions transferring data to and fro and storing data.
3. Read that I can copy the .NB1 (update file) onto a SD card and on rebooting it should ask if I want to Flash the device with this new data but it never asks and reboots completely.
4. Wallaby mode is also supposed to Flash the device via USB if I press the record key I tried but the computer and device never connect.
5. Device does not ActiveSync always on docking very often I may need to reboot the PC and or the Device for them to talk.
6. Tried XDAUnlock. exe which gave me 'error getting unlock code'.
Any ideas people? Any help would be greatly appreciated.
Andrew with no clever lines

In no particular order:
(1) 1800 MHz is a hardware feature. At best, playing with the firmware will make the phone think it can operate at 1800MHz, but it really can't without hardware changes. But hey, you already know that.
(2) When you dump the ROM to an SD card, it is dumped as an image, which overwrites any FAT formatting on the card. This is why you're getting the "Card not formatted" message on the PC. You need special PC software (XDATools -- available on this website, or XDArit) to access the ROM image on the card with the PC.
(3) In order to upgrade the XDA with an SD card, the firmware needs to be placed on the SD card as an image (the same format as #2 above). If you just did a PC file copy you used the wrong method. XDATools also does this function.
(4) Why are you trying to use XDAUnlock.exe when you've already unlocked your phone with the code from T-Mobile?

Hi,
Thanks I did finally realise what every one took for granted in this site that the ROM dumps on the SD were written in a proprietory image format not FAT format.
Am trying the entire exercise coz have read at enough places on the site that the phone can be cracked to be tri-band which is what I need for it to roam India. We have only 900Mhz at select locations and the rest is 1800Mhz. Can only but be hopeful.
The chronology for the unlock bit was off on my mail.
Basically I cant perform any updates to the phone via the adaptROM method because I feel Wallaby 5.22 has protection built into it and shuts down the connection. If I try to Downgrade the Wallaby to V5.15 using the bootloaderfix included XDATools I get the error listed below.
'C:\bootload\pput.exe' is not recognized as an internal or external command,
operable program or batch file.
ERROR: ITReadProcessMemory - Unspecified error
Unable to find flash info offset, cannot disable bootloader writeprotect
If I use XDArit V1.02 route to write via SD I get Failed to open Device \\.\PhysicalDrive7
Anyone got the older version of XDArit ??
Help people.
Thanks,
Andrew

I'm not as familiar with Bootloader version issues. My (old) unit was Version 5.15. I just got a replacement for it after I busted the screen, and the new one is Version 5.22. Maybe I'll learn more about bootloaders...
But LumpiStefan says he hasn't had problems using the SD card method with 5.22. I haven't played with the new phone yet, since it came with WM03.
Wouldn't it be easier for you to spend $100 (or so) on an unlocked 900/1800 phone?

Stuck on bootloader menu after error upgrading ROM

Help,
Is there a way to get the OS and boot img for my o2 XDA to put on my SD card so i can recover it?
I'm stuck on the boot-loader screen (version 5.22) i can not use active sync as it comes up as unrecognized device, im at my wits end, i just want to get my phone working again. is there any place i can get the O2 ROM file from? or anything that can be done, or do i have a useless brick now?
i tried upgrading with the developers ROM using the auto install, it got to the "it will take 5 mins to upgrade" screen then active sync lost connection, there was nothing showing in the progress bar, when i tried to restart, active sync could not connect. now im stuck with the boot-loader menu after a soft reset.

Sorry for the double post,
Right sorted the problem out, got a cooked ROM from a different site as no link i clicked on here was still active.
I found out that if you Format the SD card to Fat32 when in bootloader it doesn't recognize the ROM, so a format to just FAT under windows XP sorted it out, and now I'm back up and running again, though now i cant get my phone unlocked to Vodafone as the XDAunlock returns "error getting code" message. here are my Device info
Rom version 3.17.03
Radio version 4.21.X1
Protcal version 32S54

problem resolved by updating the Radio stack to 6.24 (placing the files onto the device and upgrading from there) once that had done, i had no signal, so downgraded it back to 4.21 and now I'm fully functional

Where did you get the ROM?
I have a similar problem with an XDA which failed whilst being flashed via active sync and now will not start apart from via bootloader. Where did you get the ROM that you mention please?
Thanks
Geezer

use this ROM from http://www.romkitchen.de/ choose one that u will use to cook, PC2002 or WM2003/SE, (WM2003SE cannot use SD Card, only can use activesyn) then downgrade bootloader from v5.22 to v5.15,
using MMC (flash SD) continue to special rom 1.2, 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
for the complete, read this web :
http://www.romkitchen.de/
http://www.romkitchen.de/tools/
http://www.romkitchen.de/tools/manual_unlock.htm
*read careffuly and try it, you can read my post, almost similiar problem but i can solve it by read one by one,hehehhe.. never give-up, ok ^_^V

any help with magician rom?

OK I found this thread and this is what I need to do but I don't follow any of this. what is the ROm image and how do I cook? I'm totally lost and My phone is wrecked or bricked as you say???