Database Users

Upgraded T-Mobile to new WM2003 and stuck on boot screen!

I applied the latest NK.nbf file that was available from one of the FTPs listed in the groups and modded it w/ adaptrom. Didn't install right the first time (stuck on Upgrading screen) but I was able to get it to connect w/ Activesync and eventually did install. Seemed to go fine, rebooted and am now stuck on a screen that reads:
Test Only Not for Sale
(Microsoft Windows Powered Logo)
G324e4
R6.18.00
4.00.01
Anyone got any ideas how to get this thing working? I think my next step is to go to CompUSA and buy a PCMCIA SD adapter and start doing the SD flashes....do I have an alternative?
--Mike

Hey Mike,
Sorry to hear that your upgrade didn't go well. I have noticed that if you need to install WM2003, or downgrade WM2003, the bootloader flash method is the way to go.
I think that due to the fact that the 2003 ROM is a test/developer edition, they have not really bothered to have proper ROM Upgrade Utility support.
On to CompUSA, I guess...

Hey guys I just copied your posts with a call for help in the new version WM2003 thread. You may want to keep an eye over there if people step to the plate and list some helpful info for you mike.
I agree with you Sheran on the bootloader method being the cleanest way to do it.
Unfortunatly not eveyone has an NT based machine, or the swager to go this route so hopefully the people who have had no trouble using upgrade utility will post. :roll:
Cheers guys,
E

Have SX56 - upgrade to 2003 - now fried

Newbie here...
Got a SX56 (used) and it was working fine. Saw that there was an upgrade to 2003 and like the moron I am, I jumped in with both feet. Now the device will only go to the initial screen where it shows the rom/radio versions.
I downloaded the tool, and tried to restore from SD but it still doesn't work.
My bootloader is v5.15 it seems.
At this point, I just want the thing to work again in 2002 or 2003. If someone has some ideas or a ROM image to go back, please let me know
dbrady

Maybe you´ve got the same problem than an other guy here in this forum. He have big problems to install WM2003 on his device.
Since you´re getting message of ROM AND Radio version it looks quite good.
I would suggest that you get a new ROM maybe from my kitchen (http://lumpistefan.dyndns.org and install it on your device using an SD-Card and the XDATools.....
HTH
Stefan

Thanks. I tried earlier but I wasn't sure what one to choose. I have an English Version SX56 that was sold through AT&T. It shows Wallaby Bootloader 5.15 now. It shows the correct rom/radio info for Win2003 but won't boot.
What version should I try? I'd like to get 2003 if I can, but would be willing to go back to 2002 to get a function phone again.
Thanks for all the help
P.S. - I was using Mozilla and it never actually downloaded anything when I tried.
Dean

Downloaded a new ROM - thanks - but same problem. Now the unit shows new ROM version but still never goes any further than the boot screen.
Any other ideas?

Steps please...
How did you load your new rom? Please post the steps so that we can try and figure out what went wrong.

Semi Dead SX56 Stefan, please help!!!!!!!!!!!!!!!!!!!!!!!

Hi,
I'm relatively new at this, so please I apolgize if I make dumb questions and /or statements. I have a Wallaby that just won't get pass the boot screen. My screen has a white bacakground and has the following message:
"Welcome to
T-Mobile
G324e4
R6.25.02
4.01.16"
I have already tried flashing a cooked rom by using XDATools; however, I can't get the rom into the SD card. The OSImageTool.exe doesn't show my SD cards at all, so I can't dump the rom to the SD card.
I've also tried docking the unit, but it just won't sync with my pc.
It may be irrelevant, but I have the BootLoader 5.15 on my Wallaby.
I have read several posts regarding similar issues, but nothing I've seen has worked yet. I need some help sometime soon. Thanks

Have you tried using a card reader/writer on your pc for transferring rom image?

Yup.
Actually, my laptop has an integrated SD card reader on it (I am beginning to think this may be the real issue - compatibility, etc). Keep the suggestions coming though.
Thanks for the help, but... and still in trouble :?

Have aou tried another hard reset of the device? Maybe it helps to start the ROM....
Integrated SD-Card Reader / writer do make often problems with the XDA-Tools. Best (and i think only solution) would be buying an external Card-Reader/Writer (should be available for about 10 Euro...) or borrow one.
Then you're able ro reflash your device using a SD-Card.
2nd Chance you have is making an SD-Card dump of the OS of any other XDA. And then reflash your device with this Backup.....
I don't think there is any other possibility....
Stefan

LumpiStefan,
I did try hard resetting the device several times, but nothing happened. I will try to get another card reader and go about it that way.
By the way, I did think about getting the rom from someone else, but I don't know anyone in this city with an XDA.
All in all, thanks for confirming my theory of compatibility issues. I will give that a shot...
I'll write again to tell the story of the final outcome... "Will it live to see another day, receive another call? Or will it just become another victim lost in the valley of the Death?" :lol:
Stay tunned...

egsthunder1 and LumpiStefan,
I have this exact same problem. This phone sat on my desk for several months, I powered it up and charged it everyonce in a while. Now I wanted to give it to my daughter and it just sits trying to boot up. I let it charge for several day, soft and hard resets. I used the boot loader from a second device to dump its Tmobile official ROM to SD. I then Flashed the frozen device with the SD card. It was uploading for a while, said the flash was successful. I then did a hard reset and the same "welcome to Tmobile screen with G324e4, R6.25.02, 4.01.16. Both devices had a 6.22 bootloader.
Any help would be great. There was nothing done to this device other than sittng on a desk, draining to zero, charging and then a lockup.
Thanks for any and all help.
Paul.

Hey guys, I've been having this problems for years and I've been waiting for someone to find a solution but I guess no one has the answer. egsthunder1, what rom are you currently using? I'm guessing 2003? I suggest you re-flash your rom back to 2002, I think ROM Kitchen carries the 2002 one for the T-Mobile or whatever service you're using. Just cook the rom, download it, upload it into your SD card, and use the bootloader to download the rom from the SD. It works for me if you're willing to use your PPC again w/o 2003.

Back from the grave!!!
Well,
After seeing the light , my phone turned away from it and decided that it wanted to stay in the world of the living once more.
I was right in my assertions (and Lumpi verified that), the integrated card reader on my laptop was the reason why I couldn't flash the rom into an SD card. So I borrowed one from a friend, and presto!!!
My Wallaby now runs on 2002 since I cannot get 2003 SE (from the kitchen) to get past the boot screen, just like XDAPDA88 said it would. It was twice the work, but in the end it paid off.
I guess it is for the better since 2002 was far more stable than 2003 SE ever was (at least in my experience with the Wallaby). However, I now have a BA, and I couldn't be happier (at least until I get my hands on the Universal, then I will truly be happy
Thanks to all of you for your input.

Help with charmer

Hi,
I seem to have made my MDA compact II a brick. I was having problems hard reseting it (Format FAT failed) so I tried upgrading to a different firmware.
I now have the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship-NoVendorID
firmware on it. This is not good as it is for the Prophet, although it says in the Wiki that this should work. Anyway I can now hard reset the phone, so all I need to do is flash the TmobileUK firmware back on it. The only problem is that it doesn;t let me do it. It says error:296 upgrade only.
Anyone any ideas?
cheers.

extract the contents of the t mobile package using win rar
download
ftp://xda:[email protected]/Prophet/Tools/ROMUpdateUtility-NoVendorID.zip
and put in the same directory and run.

It gets to 1% then says invalid command, not for this phone.

Latest T-Mobile ROM is at http://www.tm-phonedownloads.com/download_manager_mda_com2.html
very stable, much better than the original shipped ROM

Finally got it back.
If you have a T-mobile MDA II (Charmer), then Flash it with a Prophet ROM, the only way I could get it back was to use the following:
RUU_Charmer_100_100_049_CHS_Ship.rar
typho5 -x nk.nbf
Then created a new nk.nbf with the output using nb2nbf.
I then Flashed this with Wizard_RomUpgradeUtility_noID
And miracle it started. I quickly CID unlocked it and am now flashing with latest T-mobile.
My problem was that the Rom Update programs wouldn;t read version 2.xx ROMS.
Anyway it has just finished and looks fine. Thanks for everyones help, now I just have to get my SD wifi card working.

How do you do it
Hi I just got a MDA compact II from T Mobile UK I would like to upgade the ROM but its all very new to me since you know what you are doing can you post an idiots guide to the process.
Hope you can help

Hi, it depends what Rom you want to upgrade it to, the latest one from T-mobile is pretty good. There is an unbranded one (no T-mobile logos or suchlike) or there are Roms in different languages. It depends why you want to change the firmware and what to.

I suppose I don't really know the problem is as I just got the thing did some searching and came across this site read your post and thought i want to do this maybe you have some suggestion. Also I tried the RUU mentioned in an earlier post but it I can't update when I get to the from/to screen it tells me I will go from 2.6.2.110 to 2.6.2.110 I was expecting to move up.

daveh1171 said:
I suppose I don't really know the problem is as I just got the thing did some searching and came across this site read your post and thought i want to do this maybe you have some suggestion. Also I tried the RUU mentioned in an earlier post but it I can't update when I get to the from/to screen it tells me I will go from 2.6.2.110 to 2.6.2.110 I was expecting to move up.
Click to expand...
Click to collapse
Sounds like you are running the latest version. Is there a problem with the phone? If the phone works fine, I would just unlock it using lokiwiz02b (So you can use any network card) and then EnableRapi (So you can run unsigned code) then CID unlock it using awizard (so you can use any Brand/Language of ROM).
If you have no problem with the firmware I would leave it alone.

Hi,
Yep, I'm in the same situation, why does the prophet firmware load onto the charmer without erroring? !!!
Anyway, I have a copy of RUU.rar but I'm having problems working out what I need to do to it between unpacking and flashing the phone (i.e. the typho5 bit and then the nb2nbf).
Can someone please help me out?
P.S. The phone just sits at a black screen that says 'Dopod' across the front at the moment

Can anyone tell me how to 'force' a downgrade of firmware? I've got what appears to be the right firmware from FTP but it won't over write the incorrect version 2 installation as the uploader software thinks it's later therefore better.
There has got to be a better option from the command line surely?
HELP phone is dead

Chirpy said:
Can anyone tell me how to 'force' a downgrade of firmware? I've got what appears to be the right firmware from FTP but it won't over write the incorrect version 2 installation as the uploader software thinks it's later therefore better.
There has got to be a better option from the command line surely?
HELP phone is dead
Click to expand...
Click to collapse
Progress, but now it works only from the charger so the shipped ROM upgrade won't work as it reports the battery as being at less than 50%.
Anyone know how to force a ROM upgrade or where I can find the right ROM files to use awizard to do this?

Need help to unbrick.

Hi im sorry i had to post this as its probably been asked over and over but ive searched forum and cant seem to find a working solution for me.
I updated my HTC Touch ELF with Onyx ROM after updating SPL etc and everything went fine but couldnt get a signal etc on phone so decided to go back to old rom that i made a backup of untill i had done more research and found the ROM i wanted.
Reflashed the backup rom build i made everything looked good untill i went to boot and it just powered off after the orange brand logo.
I cant do the goldcard method as i have no other phone that can take the card i do however have a adapter for my pc for the card.
Ive treid the ubrick thread but cant get mtty.exe to use usb port.
Can somebody help me out to get this up and going again, Sorry for posting this i know its probably been asked many times but cant seem to get it going and am a n00b on this subject really.
thnx.
[EDIT]
Just managed to get that unbricking rom installed and booted so am gunna try and flash my original dump again.
[EDIE2]
Seems it some problem with my original backup as just doesnt boot after brand logo, When building with HTC Rom tool other files are green but OS file stays black does that mean the OS file is bad?

the adapter for ur card wont work, u need a WM device to make the goldcard method.
what about this: http://forum.xda-developers.com/showthread.php?t=446242

crapula512 said:
the adapter for ur card wont work, u need a WM device to make the goldcard method.
what about this: http://forum.xda-developers.com/showthread.php?t=446242
Click to expand...
Click to collapse
yeah thnx that did the job
Cant seem to get my original dump back on though
I originally just wanted to update to windows 6.1 but there isnt a official update can you recommend the best/most stable unofficial one to use?

take a look at onyx, tess, touch hd or aether. and if u feel brave, u can try letama which is WM 6.5 beta

tried the onyx and another but cant find network just keeps "searching..."

what radio do u have? try with 3.34 or 3.39

Thnx, Just noticed the updates and are going to update and retry.
thnx for help, appreciate it

Do they have them updates for the ELF, can only find those versions for ELFIN.
[EDIT] nm Noticed they are for either
Still having trouble with signal always searching, Installed latest radio version aswell.
[EDIT] whoops what a dumbass, I missed the pin entry at beginning which sometimes pops up but then boots into today screen if not enetered in time, finds signal straight away now