Database Users

T-Mobile Rom.... Can't do anything else... Help

Since updating to the T-Mobile Rom for my XDA, nearly everythiung has gone wrong.
And when I tried to downgrade it.... Nothing happens.
I used to use a modified Program A to upload it to my phone but it continues to say that the USB devide gets remotely stopped. the only thing that I can think is that my phone is cancelling the upgrade/downgrade.
I have also tried using a copy of the XDATools program to try and:
Upload another Rom.
Copy the rom to an SD card so I can use the bootloader method.
Change the Bootloader so I can use the SD card method.
None of there are working.
Help :-(
I really want to go back to the ATT rom, it might have the annoying thing with the sound but at least it doesn't mess up as much, doesn't format my SD/MMC cards and lets the alarms actually work for me.

if i'm not wrong, it seems you upgraded using the TMO exe file which updated both ROM & RSU.
check ur boot loader version, if it's 5.22 or higher, i think you need to dowgrade to 5.15 ... use the exe file that comes with the XDAtools in the binaries directory .. its name is fixbootloader.exe .. it should update ur boot loader to 5.15 by which you can use XDAtools or the SD method.

Tried that. I do have XDA tools on my machine and used that program but my CDA still has the bootleader of 5.22
And both of my machines don't like trying to update my XDA :-(
This Rom is the most annoying one I have tried mainly becaise now I can't go back to even my original one that I backed from the XDA when I got it.
Am I stuck with this ROM?

omg, i think i am having the same problem. In my case, since ive installed the new rom, i cannot sync with activesync, well very slow anyway. Activesync on my pc stops responding for a while and suddenly it says connected. However when i then run the executable created by the kitchen, it just flashes a command line window for a second.
When I try XDA-toolz with an nbf file, i get the following message:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
Click to expand...
Click to collapse
Please someone help, because i am really stuck now.

I checked, my bootloader is 5.14, so that shouldnt be the problem, perhaps i need to reinstall activesync, or perhaps lumpistefans kitchen cooks up bad roms. :?:

Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!

Biso007 said:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Click to expand...
Click to collapse
I dont understand how i can have a wrong rsu? I didnt update it , as far as i know , i just updated the pda part. I only saw programme A.
Activesync does recognise my xda, because i can synchronize and explore my device. It does however take a long time before activesync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling activesync, this didnt help.

prowling said:
ActiveSync does recognise my XDA, because i can synchronize and explore my device. It does however take a long time before ActiveSync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling ActiveSync, this didnt help.
Click to expand...
Click to collapse
If there is something wrong with the RSU it will defeinitly slow the USB performance, not neceassary by wrong RSU flashing ... otherwise, check the pins of your cradle or the 22-pin connector of the XDA ... maybe one or more pins are bent or weared.

Tried upgrading the radiop stack and although the reception is slightly better... It still won't let me upload,
and its a new cable too :-(
Oh well looks like I am stuck with it.

Another way to upgrade firmware
Are there other ways to upgrade the bootloader from SD card from within the device or even to upgrade the OS from within the phone itself?
You know... as a last alternative?

You can use SD reader/writer from the PC using XDAtools ... once the .nbf file is on the SD card, use the normal SD flashing method.
Or you can use another XDA device from a friend to copy the file to your SD card

I am having the same problem. I have TMO 4.01.16 and since I installed I can't down/upgrade my ROM through EXE or XDA tools, it says my device isn't connected, but I can still connect with Active Sync and all that jazz

ha ha
I can fix all your problems!

How?

Finally got it to work, Although it was a little bit of effort to do so.
I went back to the kitchen and downloaded a NB1 cooked rom with the "B" Signature. Then I basically ran the TMobile Setup again...
Once the setup files were on my computer I overwrote their .NB1 file with the one I just cooked.
But.... I forgot to change the file for the Radio Stack.
The machine worked except for the phone and as something is still stopping me. *it was my first reboot* It wouldn't let me use a new radio stack.
Ended up that i kept on going in to the bootloader and eventually turned my radio off altoghether before trying an update.
Now I am back to a decent rom... (Cooked and modded version of the ATT Wireless rom) and I am almost really happy.
Now to figure out how to stop the annoying sounds starting off really low.
But til then... I'm 90% happy

Thespus2002 said:
How?
Click to expand...
Click to collapse
Use the Sd Method flashing!!
Tmobile roms won't let you upgrade from the usb, here's the link and it will guide you how to flash your device from the SD good luck
http://forum.xda-developers.com/viewtopic.php?t=3274

The way I described.. I had to use the USB method.
my current bootloader (6.22) will not allow me to boot from an SD card.
And XDATools will not allow me to downgrade it... Yet

on ur PC at \xdatools\binaries run this command: pnewbootloader.exe bootloader_5_15.nb0

Wish it was that easy. The phone still appears to be locked in the rom so I can't update the Bootloader. I keep getting a message that says.
Unable to flash in to offset, cannotg disable bootloader write protect.

ROMs and getting it onto the PPC

OK I have the tmo PPC its already got 2003 on it and I know the loader is 5.15, other info that might be needed.
ROM 4.01.16 ENG
Radio 6.25.02
OK I want to get my own cooked ROM onto this, I know I know use the SD card method, well I don't have one and after getting this thing can't get one for a while either. I have the cradle that it comes with and have put software into etc, I have tried some unlock ROM software to find it didn't work etc etc. after cooking ROM and running it it tells me in a DOS window:
Error getconntiontype - An Existing connecitonwas forcibly closed by the remote host.
error getting connectiontype
so basicly I need to find a way to get this into my PPC via activesync or something. sorry for bad post a little tired but I think people will understand and be able to help me or tell me I need SD card and wait until I get one.

I think you can use xdatools to flash the rom direct from xda memory, choose the nbf file as source then choose the xda device memory as destination from the drop down box in destination section.

OK tried that but can't access the PPC with xdatools so that won't work. thats for trying though.

TMO ROMs are known to resist exe flashing ... use the SD method and you are lucky to have the boo loader 5.15

Well glad to know that my boot loader is a good one, now to find a SD card I can borrow to do this with, should I use a 32 or 64 or does it really matter as long as it holds the file.

64 megabytes is needed really, I have had a problem with 32 meg, it looks like it is programmed but when i flash it there is always a problem.

macgyver33 talked about having a 2003 version. Can anyone tell me where to get it? I mean european one (900-1800 MHz). Or at least the PDA part of it? And yet haven't found quiet an exact explanation of "SD method" - any suggestions? Thanx a lot!

Bootloader v.5.17 locked
BL v.5.17 + TMO ROM. I am not able to downgrade the bootloader or change ROM.
I've tried using:
Cooked ROM.EXE - No way
(Error: GetConnectionType - An existing connection was forcibly closed by the remote host. Error getting connectiontype)
XDA OS Image Tool - No way
(Error: Same as above)
ITSTools - pnewbootloader - No way
(Error: Unable to find flash info offset, cannot disable bootloader writeprotect)
SD Method - No way
In bootloader mode (soft-reset while pressing on/off button), I have no options: Even with an SD card with OS image inside, there's no way to start ROM download as there is no option to choose...
Any idea?
Thx

Check this thread

Thanks Biso007.
No way. My XDA doesn't load the bootloader in a proper way:
1. Inserted th SD card in his slot
2. Answered "No" to format the card
3. Soft-reset while pressing on/off button (so to enter in bootloader mode)
4. Display turns off
5. No Wallaby Bootloader screen, so no action to take...
6. Wait... Nothing.
7. I've also tried to press the "Action" button so to start the SD downloading... Nothing
8. Wait... Nothing.
6. It needs another soft-reset to exit this state (a not working bootloader mode, I suppose)
7. It turns on "normally".
Any further idea? :-(
Thanks

if I'm not wrong, I couldn't see that you ran the 5.17 patch first ... without it your device will never detect the SD file ... chech the thread again

XDA 1 not working

Hi,
I was upgrading the software upgarde on my device. I successfully upgraded the Pocket PC software on the O2 XDA, but when I tried to upgrade the GSM radio/GPRS software of the O2 XDa, it gave some error and after this my device is not starting at all. The only mistake I did was that "I did not remove the SIM card before upgrading the GSM radio/GPRS software" The device does not start even after cold booting the same. When I start the device, the O2 screen comes and after a quite long time the main window does come but I cannot do anything. I tried to tap on contacts, time, tasks but nothing happens. I can see the windows logo wall paper but cannot do anything. Please help on how I can restore back my O2 as a cold reset also does not work. :?
Thanks and Regards
Jinesh

There's many topics about your question in the forum. Search it! Try to search with this keywords: 1% error, repair.zip

There's many topics about your question in the forum. Search it! Try to search with this keywords: 1% error, repair.zip

Hi,
I have tried all the available options but it still does not work. To restore the ROM how do I get access to the O2 cause niether serial nor USB is detecting it.
Please help.
regards
Jinesh

SD card install guide
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

Thanks Chief, I will try out and let you know.
regards
Jinesh

Hi Rudegar,
I tried the procedure given by you. I was able to write to the flash successfully. After writing to the flash it gave a message "Checksum OK, Please cold reboot to reset".
I did a cold reboot. After starting the O2, it showed the O2 logo screen and after quite a long time, it asked me wether I want to format the SD card or not. After that it took me to the default screen of XDA wher eit showed options like "Add today's date, Contacts, Schedule etc etc. but upon tapping any of the options the O2 behaves erratically. If I tap on today's date it takes me somewhere else. Inshort it does not work.
I again did a cold reboot and now the device is in its original position i.e not going after the O2 logo where it gets stuck up.
One thing I would like to mention is that all these activities have been done putting the O2 on the cardle only as the battery is totally discharged and the device turns on only after putting it on cradle. Even after the cold reboot it does not start unless I put it on the cradle whichis connected to the mains. Is it Ok with this or am I doing something wrong? The battery does not charge and hence I have to do it in this way.
Please suggest what wrong am I doing? Any suggestions from anyone will be welcome.
regards
Jinesh

Hi,
Someone posted the original O2 ROM on this site and I downloaded the same after which I was partially succesful in flashing the ROM and reviving my dead O2 back to half life. :roll:
I burned the ROM on
to my SD Card and flashed the ROM on to my O2. After
successfully flashing the ROM I rebooted the device.
The device now starts Windows but it takes atleast 15
minutes to start. I get the today screen. WHen I cick
on start the start menu appears after a delay of 10
seconds and all applications run normal, however all
this happens only on the Cradle only.
When I go into the Battery Settings it shows "Battery
Status Unknown".
Also none of the phone functions work. The SIM card is
not recognized and in device information it does
dispaly the "IMEI number" and the "Protocl Version"
I am only able to use inbuilt phone applications.
Is there some problem with my battery cause it is not
charging even on the cradle.
Device Information does not show Radio Version, Protocl Version & IMEI number at all.
Can anyone please help me?

hello all,
it means that your radio stack are dead. Currently, We don't have any real method to fix this problem. When the radio stack is error, you can not upgrade it or do anything to make it work. We can only upgrade or downgrade the radio stack if it works. Also if you try to upgrade the radio stack, we realy need to flash the chip using a speceial tool or need the sd card which build in radio stack with we can only flash in bootloaading mode. Howerver, in some case, we can fix it but .... I think it is just lucky or the xda error when battery problem.... in this case, just disconnect the battery few minutes and connect it again by pressing the battery hole.
Regards,
Hoanghon
p.s. I have dead xda. I killed it when I upgraded the RADIO STACK. Therefore, if you are really need to upgrade the radio stack, I recommend use the official upgrade for secuirity. or just upgrade the rom only.
Note:
To eliminating the error, you need to upgrade the rom or the radio stack, you need to check if the rom fix the radio stack or the stack you are trying to upgrade it fix the rom or not.(ie, Tmobile Rom have to use it radio stack built for Tmobile pocket pc...... I know that in some case when we mix between the radio stack and OS it works but I don't think it work propertly. Anyhow the mixing bettween radio stack and OS is very dangerous if it doesn't suppport then you have to reflash the radio stack or rom(the OS is Okay but the keep upgrading the radio stack may cause the radio stack killed)

WE NEED SERIAL CABLE FOR PDA ANY HELP PLS!!!
Hi Jineshd we
have the same problem and we are sure that the only way is to do SD uptade
and U said U have a serial cable to Yours device. With that we can be able to download flash gsm rom from working device and put it back via SD card to ours. Pls tell me where can I get a serial cable or some schema how to prepare it and I will try to repair ours dead pdas. Its our only chance
rgds
Lukasz

Hi,
Thanks all for the replies.
Can anyone tell me how doI repair the radio stack?
Regards
Jinesh

no way without having special RSU rom update on SD card and run it from bootloader or dissembling the device and reprograming GSM rom on special rom/bios programing socket. (Here on forum is user Cgigate from Toronto CA who can do it but I cant contact him)

Wallaby Upgrade Blues

AS I sit here staring at my cute little Wallaby in it's cradle with a nice desktop, I long for 20/20 foresite. I can sync with my PC and and do anything I want as long as I don't want to make a phone call or take it off its cradle. I have been all over this web site and the web in general looking for a solution to the 1% GSM Failure Upgrade problem. I have tried every written idea and approach with no success. I am sharing my conclusions here with no particular hope of an answer.
It seems a low battery may cause the error in the first place. The first upgrade attempt got me to 16% and hang. I reset and got to 6%. Third time it was 1%. Once the battery is low the GSM processor shuts down. The GSM processor controls the battery charge. You can not upgrade the Radio Stack if the GSM processor is shutdown Even a new battery does not seem to reset the GSM as there is a software switch that seems to have been set. I have read some vague reference to a serial cable and hyperterminal used by TMobile techs to "reset" but no real details.
I am moving on with my life as Wallaby is dead.... I miss you, baby.

Have you tried this method?
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError

cruisin-thru said:
Have you tried this method?
Yes I saw this solution straight away and have tried it and several variations, but now that I review it I have a question. The wallaby's battery is completely dead so after the reset I must put it in the cradle for it to start up. It then produces the 1% again ala step 8. Now what am I supposed to do? Take it off the cradle and put it back on? That would cause AS to start. Are you suggesting the GSM upgrade will take place WITH the error message right on screen?. That would be super! I'll try it right now.
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
Click to expand...
Click to collapse

Blues Redeux
One other note. The developers ROM v1.1 will not active sync with my PC. Neither will v1.2. All the other STD roms I've tried will though. Any idea about that?

getting the image to run from the SD card
problem: radio stack upgrade failed (using the siemens upgrade) and now I get a GSM error and eventually a partial pocket pc desktop with no start menu or access to an explorer window.
OK, I used xda tools to copy the rom to the SD card (1GB card), inserted in the wallaby, held the power and soft reset the device, I get the boot loader v5.15 and then a GSM Error. From there, nothing. Any suggestions as to what I am doing wrong? Does the SD card need additional files or should it be formatted a certain way? Any help would be greatly appreciated.

Getting image to run from SD card
Charles,
If you search this site you will find many descriptions of how to load an image from the SD card. Sounds to me as if you did not get a valid rom image on the the card cause the boot loader should rcognize it and ask you if you want to copy it.
The bigger problem is the PDA rom does NOT fix the GSM rom, which is the one that is hosed.
I am now in week three after I killed my Wallaby and I am having severe withdrawal pains. I did not realaize how much I depended on it. Can anyone tell me where I can sent it to have the GSM/Radio stack fixed?

I have found how to flash radio via rs232 cable, but i need program monitor.exe (pc monitor ver 6.5.7) to do this. I can't find it. Does anyone have this program or know where i can download it?
Sorry for my english, I'm from Poland

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???