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.
Related
I have officially screwed up my RSU. I can boot into CE just fine, but there is no radio stack to speak of. After having many partial attempts, there's just nothing there. I've tried everything (or so it seems). I can do an activesync connection, btw.
Whenever I try to run PROGRAMME A, it just hangs. I hit the next button and *nothing* happens. That's any program a, whether from ATT or Tmobile.
Hi there,
Did oyu try installing the Radio Stack Programma A thingy from another windows installation? Another pc? Perhaps that will work.
Os course... you could be trying to install a version which is not suited for your GSM provider/GSM hardware. Look for info at your GSM provider website. It's hard is not impossible for anyone here to tell you which version should work for your device.
Cya,
Oz
Yeah...I tried it on my laptop too. The problem seems to be program b, which rewrites the RSU. It simply won't do it for some reason. This shouldn't be the case.
Come on....someone must have some stupid trick to re-flash the radio stack. I remember seeing solutions to the "1% problem," but all of those solutions were with the non-US radio stacks. :-/ I didn't buy my phone from Tmo, so I have no warrenty to speak of.
which rom and ruu were you using? seems like you were using the .exe correct? which unit/network are you on? this might help you get some help. be specific with the problem, etc.
What versions (ROM and Radio Stack) were you using prior to running the EXE upgrade?
What versions are currently installed?
And which radio stack are you trying to upgrade to?
I was using 4.00.005 and the newest ATTWS ROM before, and I was trying to go to Yorch's newest Tmobile beta, the one that includes the RSU.
Right now I have the most recent official Tmobile ROM and no radio stack on there.
Ejdmoo:
After decompressing the rar file, look for the two RSUpgrade files; one is .cp64 and the other is .exe. Copy them via Activesync to the windows directory on your TMo PPCPE. Then execute the RSUpgrade.exe file. That should reflash the new radio stack. It worked for me. Good luck!
David
I am in the same boat as ejdmoo, and had the same roms installed and all that good stuff...still no go with fixing the radio stack. One thing I noticed is that I removed the .cp64 file from the \windows directory and it still tried to update and failed at 1%. I don't think the version of the .cp64 file matters since it is not getting that far.
Another issue that popped up after the failed update is th unit does not charge, it will only run on AC, and it does not show a status in the power app under settings. Bout you ejdmoo?
Come to think of it, I am having the same power/charge problems. Also, I have tried copying the RSUpgrade.exe program to the device multiple times and from multiple sources. Also, I copied some of the other required files (something map and .c64 file), still didn't work. I think it *must* have to do with the RSUpgrade.exe, but I wouldn't know why.
FYI...I'm going on vacation this week (luckily I have a backup phone), but I expect this to be fixed when I get back! :!:
C:\Program Files\SX56 upgrade utility>adaptrom
ERROR: GetConnectionType - An existing connection was forcibly closed by the remote host.
error getting connectiontype
Click to expand...
Click to collapse
This is what adaptrom returns now, this is when the tmo is connected and browsable via AS. Anyone have any ideas why this would be happening?
Since my unit will be replaced I am willing to do some scary things with it, so if any of the xda-devolopers want me to try something let me know. I have an sd reader/writer and a usb cable but no serial cable.
ejdmoo said:
Come on....someone must have some stupid trick to re-flash the radio stack. I remember seeing solutions to the "1% problem," but all of those solutions were with the non-US radio stacks. :-/ I didn't buy my phone from Tmo, so I have no warranty to speak of.
Click to expand...
Click to collapse
Been there seen that!
Here is hope I fixed it:
First go to the below site and download and install the v4.21 ENG radio stack upgrade. Now here's the tricky part but I must warn you I did all three and really don't know which one did it, might have been a combo of all three.
1. Entered bootloader mode and selected the 900 band and re-booted.
2. Removed the SIM card and rebooted
3. Entered bootloader mode and turned off the radio.
Note you'll know when you got it right because you'll have a stable Active Sync connection. So after each of the above steps see how stable Active Sync is before trying the next step.
Reran the T-Mobile upgrade (PC install) and all went go well.
02 Radio Stack Upgrade v4.21 (1.54MB) Download.
http://www.o2.co.uk/business/productsservices/xda/romupgradedownload/0,,113,00.html
I'm not sure in which order you want me to do what...?
I had the same problem, but a hard reset fixed it for me.
David
For all of you having the same problem I have been having after upgrading to the O2 4.21 RSU here is what I have found makes the loading of the RSUpgrade files into the \windows directory work. You need to also copy the monitor_ul_bs.m0 and monitor_ul_bs.map files to the windows directory. Then when you execute the RSUpgrade.exe it works.
barjohn you are a genius!!! I can't believe I never thought of moving the other files before...you rock I am now in possesion of a fully working WM2003 T-Mobile PPC PE!!!
Thank You barjohn!!
mdavidm said:
I had the same problem, but a hard reset fixed it for me.
David
Click to expand...
Click to collapse
Boy I forgot about doing the hard reset, what step was that?
It must have came right after the Radio stack upgrade, Right!
So it appears that what works for some doesn't work for others, strange business!
I read barjohn's fix were he manually copied some missing files into the windows folder and that solved it for him, I guess we were just lucky! :?
barjohn said:
For all of you having the same problem I have been having after upgrading to the 4.21 RSO2U here is what I have found makes the loading of the RSUpgrade files into the \windows directory work. You need to also copy the monitor_ul_bs.m0 and monitor_ul_bs.map files to the windows directory. Then when you execute the RSUpgrade.exe it works.
Click to expand...
Click to collapse
So it would be save to say that one should just copy the above files into the Windows folder first before starting the initial upgrade and forgo all of the other headaches, agreed!
Qman,
That's a great idea, but then we would miss out on the thrill of thinking we have transformed a great electronic device into a $400 paperweight! What fun is it if everything works out on the first try? Have fun!
David
Well Ive officially made my tmobile ppc a $400 paper weight. I was running the Kitchen rom with ATT radio stack and I attempted to update the RSU to the latest tmobile version to see if it improved the signal meter using the method mentioned here. I copied the files suggested here via activesync to the windows folder on my ppc and ran the exe, the upgrade stopped at 13% and that was it. Unfortunately I dont have a SD reader so Im high and dry until tomorrow. I can access the bootloader and I get the GSM error and thats it.
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
any one?...my $300.00 paper weight needs help
is there anything i can do with wallaby bootloader....i dont have anything else.................
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Yes, $300.00 paper weight !
you could get it fixed (hardwire repair)
Qman said:
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Click to expand...
Click to collapse
copied the files ( monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUpgrade) to windows dir, executed the rsu upgrade...uprgade started....2%....10%....16%...16%....16%....so i reset it, an thats where Im @
(i had the I had it cradled, connected to usb & power during it all)
Yeah, that's exactly what I did. I noticed you did a hard reset, which is also what I did. That may have been the death blow.
First of all, do not do ANYTHING in the Wallaby bootloader. If you start messing around in there, you're done.
Plug your phone into the power cord (even though the battery won't charge now, the phone will stay powered if you keep it plugged in).
Try to get the RSU files for the version you initially upgraded from (6.18 for the default T-mobile, or maybe 4.21 like I had from a 4.00.05 ROM upgrade package). Load those files into the Windows directory and then try running them.
Just FYI, I did a hard reboot and changed ROMs several times. I also messed with all kinds of GSM settings in the bootloader. In the end, my phone was toast. Unrecoverable. Fortunately, I got mine from T-mobile and they did an exchange. With my new phone, I'm just gonna wait for the official RSU before I try changing it
ok...too late about the Wallaby thing, that was the 1st thing i was messin with, wen i first loadit it it said "wait" 4 a looooong time, then finally said "gsm error"....but i started playin with it, an tried every option on there, but nothing happened @ all.
2nd: i cant load any thing into windows, because the xda never boots up, just sits @ the 1st screen
so i figured im gona have to get a usb r/w and a SD card :shock:
should i use XDArit.exe or XDAtools.exe
im i gona have problems, i think i have Wallaby 5.17 :idea:
JUICEe said:
Qman said:
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Click to expand...
Click to collapse
copied the files ( monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUpgrade) to windows dir, executed the rsu upgrade...uprgade started....2%....10%....16%...16%....16%....so i reset it, an thats where I'm @
(i had the I had it cradled, connected to usb & power during it all)
Click to expand...
Click to collapse
Ok you're still in good shape just try re-copying the files over and run RSUpgrade again, but what ever you do don't install the 4.21 Radio stack upgrade!
BTW I never upgrade my radio stack while my device is connected to my PC, I always disconnect and use the AC adapter.
HTH
Qman said:
JUICEe said:
Qman said:
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Click to expand...
Click to collapse
copied the files ( monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUpgrade) to windows dir, executed the rsu upgrade...uprgade started....2%....10%....16%...16%....16%....so i reset it, an thats where I'm @
(i had the I had it cradled, connected to usb & power during it all)
Click to expand...
Click to collapse
Ok you're still in good shape just try re-copying the files over and run RSUpgrade again, but what ever you do don't install the 4.21 Radio stack upgrade!
BTW I never upgrade my radio stack while my device is connected to my PC, I always disconnect and use the AC adapter.
HTH
Click to expand...
Click to collapse
I figured that having it connected to usb was a bad idea, i just wasn't thinkn :roll: ...but how am i supposed to copy the files when i cant load up the XDA, and even when trying to connect to active sync, while the XDA is sittin, froze, on the boot screen- active sync doesnt recognize :|
Qman said:
BTW I never upgrade my radio stack while my device is connected to my PC, I always disconnect and use the AC adapter.
HTH
Click to expand...
Click to collapse
What ? I'm surprise!
JUICEe said:
I figured that having it connected to usb was a bad idea, i just wasn't thinking :roll: ...but how am i supposed to copy the files when i cant load up the XDA, and even when trying to connect to active sync, while the XDA is sitting, froze, on the boot screen- active sync doesn't recognize :|
Click to expand...
Click to collapse
At this point I suggest that if you have an PC card SD card reader reload
the OS and start over with the radio stack upgrade using the same upgrade method but this time upgrade to the AT&T radio stack because
its less likely to fail than the T-Mobile stack.
Also after the OS reload you would have to copy the needed radio stack files from your PC to your SD card then move them to your devices Windows folder.
BTW what radio stack were you upgrading from?
HTH
...AT&T radio stack because
its less likely to fail than the T-Mobile stack.
Also after the OS reload you would have to copy the needed radio stack files from your PC to your SD card then move them to your devices Windows folder.
BTW what radio stack were you upgrading from?
HTH[/quote]
IM NOT SURE BUT I THINK IT WAS 6.18
WILL THE ATT STACK WORK WELL ON MY T-MOBILE SERIVICE?
AND IM CONFUSED ABOUT HAVIN 2 HAVE TO COPY FILES TO THE SD THEN TO THE XDA...1ST, BECAUSE I NEVER USED AN SD W/R OR ANY OF THE SOFTWARE NEEDED TO USE IT, AND IF I RELOAD THE OS, CANT I JUST BOOT UP AND COPY THE STACK FILES THRU ACTIVE SYNC? OR WILL THE DEVICE STILL NOT BOOT UP ??
BTW:THANX :!:
JUICEe said:
...AT&T radio stack because
its less likely to fail than the T-Mobile stack.
Also after the OS reload you would have to copy the needed radio stack files from your PC to your SD card then move them to your devices Windows folder.
BTW what radio stack were you upgrading from?
HTH
Click to expand...
Click to collapse
I'M NOT SURE BUT I THINK IT WAS 6.18
WILL THE ATT STACK WORK WELL ON MY T-MOBILE SERVICE?
AND I'M CONFUSED ABOUT HAVING 2 HAVE TO COPY FILES TO THE SD THEN TO THE XDA...1ST, BECAUSE I NEVER USED AN SD W/R OR ANY OF THE SOFTWARE NEEDED TO USE IT, AND IF I RELOAD THE OS, CANT I JUST BOOT UP AND COPY THE STACK FILES THRU ACTIVE SYNC? OR WILL THE DEVICE STILL NOT BOOT UP ??
BTW:THANX :!:[/quote]
Yes the AT&T radio stack will work on your T-Mobile and its the one I use and recommend.
As far as reloading your OS from the SD card its what we call the SD card boot loader method and is by far the best way to upgrade your OS. Do a search on this forum for more info.
Yes your device will boot but since your radio is blown Activesync most likely wouldn't connect.
HTH
ok, thanks again...i guess im off to buy the reader/writer, and the card, from walmart, or radio shack whichever is cheaper...( DO I NEED A 64MB CARD, OR CAN I GET A 32MB?)
I'll repost after halloween, since i gota go to sum partys an release all my xda induced stress with good old friend beer
btw, lol, my girlfrien seen my xda while i was tryin to repeadidly boot it up, & as it was froozen on the boot screen, i have "rom is cooking" bootimage, an she was all " i guess u did fry ur phone" :shock: :twisted:
....so with XDAtools OSImagetool, will i be able to copy the r stack?
is the target x:\windows\
that easy?...god i hope :?
Yes you'll need at least a 64MB SD card.
BTW Fry's had one on sale earlier this week for $22.00.
HTH
re radio stack upgrade
I've been following this thread re radio stack upgrade to TMO. I have RS6.18.00 currently and see 6.24.00 at yorch.net's web site under upgrades. Questions:
1. Do you copy the 4 upgrade files to the /windows folder on the PDA to run the upgrade?
2. My phone is working fine with ROM4.00.21 and RS6.18.00, should I upgrade my radio stack to 6.24 or wait another month or two for TMO's offical build?
Kind of nervous given the threads I've read. btw, I bought a SD card reader/writer & flashed ROM via bootloader/XDATools method. Worked well.
Craig
Re: re radio stack upgrade
cshields1 said:
I've been following this thread re radio stack upgrade to TMO. I have RS6.18.00 currently and see 6.24.00 at yorch.net's web site under upgrades. Questions:
1. Do you copy the 4 upgrade files to the /windows folder on the PDA to run the upgrade?
2. My phone is working fine with ROM4.00.21 and RS6.18.00, should I upgrade my radio stack to 6.24 or wait another month or two for TMO's official build?
Kind of nervous given the threads I've read. btw, I bought a SD card reader/writer & flashed ROM via boot loader/XDA Tools method. Worked well.
Craig
Click to expand...
Click to collapse
I suggest upgrading to the AT&T Radio Stack first it has a higher upgrade success rate IMHO or just wait on the official T-Mobile lease.
As fas as how do you copy the files over, you can use Activesync Explorer or use your PC's SD card reader to copy them to your SD card then copy them from there.
HTH
back & hungover...
so i got me a sd reader & the card.....copyed 4.00.16 to it (b4 had 4.00.05 i think) loaded it via wallaby, everything looked fine (except my battery was practically dead, i had to race to get it off the charger reset and put it back on the charger) so the os was copyed fine, and wallaby told me to cold reset (that did mean a "hard", no?)...so i hard reset it, then after a few mins i stuck the pin bak in the lil ass hole, and nothing happened :evil: so i put it bak on the charger, an the boot screen appeared, with a new image and on bottom of screen it sed 4.00.16 ..........but then it just sat there, like b4 and wut i noticed, that i didnt mention b4, is wen its booting up, 1st shows the "4.00.16" then sits there for like 2 minutes, then pops up a "G" & "R" above the "4.00.16" respctivly.....
and i left the device on charger 4 a while, and tried to hard reset again and still wont boot after 2nd pin push :?: :?: :?:
and another thing i didnt mention b4, wen loadin wallaby, it sez gsm error, or did i mention that
i had an idea, maybe to install an older os 3.xx.xx??? but it seams the problem is the gsm wont load, or isnt ther, or damaged, i dont know, how can i load a working GSM on it :shock:
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...
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...
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