Database Users

Can we upgrade/downgrade using serial (LTP1)?

I was running ROM 3.20.06 and Radio 4.21.00.
I read everything on here about upgrading to ROM 4.00.05 and figured that I was ready to upgrade. Many others experienced no problems when upgrading from 3.20.06 to 4.00.05.
The upgrade procedure was complete and I hard reset.
The XDA turned on and a white screen with "Test Only", "Not For Sale", A Microsoft Windows Powered logo and the Platform information appears and that is all that happens. In other words, it is ****ed and won't do anything.
Does anyone know whether ROMs can be installed via, LTP1 seeing as though the USB will not communicate? Will I get the same problem?
A reply would be nice.

Forgot to mention...
I forgot to mention that I will be connecting my USB cradle to a USB-2-LTP1 cord. If that helps anyone reply then sweet.

Get yourself an sd card reader writer and an sd card of 64 meg or more. Use the tools on the forum to program the rom to sd card, then you enter bootloader mode and your phone will burn the rom from there. As for the lpt port, no way that I know of.

Bootloader mode?
:roll:
Is it possible to change the XDA into bootloader mode if the XDA is not functional? (I cannot do anything, just a white screen is what I see)

Give it 15-20 minutes
I know that this sounds stupid, but don't mess with it for about 15-20 minutes. It seems that if the radio stack is screwed, the OS takes forever to boot. I have been doing OS installs for several months, both directly and via an SD card, so I was comfortable with the process. I had NOT ever done a radio stack upgrade as I had the latest (& only one) that AT&T had released. With the "official" rollout of WM2003 by AT&T, I decided that I liked my custom 2003 ROM that I had cooked a couple of months ago, but I did want to try the newer radio stack. Well, all hell broke loose. At first, I had a PPC that would not boot. So, I did a new flash of the OS via SD chip. It seemed that it too was locked (ie the initial splash screen with OS info at bottom and then it seemed to freeze). Then I read in another thread that someone had noticed it took about 15 minutes for the thing to reboot after a failed radio stack upgrade. And so after giving it time, sure enough, my PPC did finally boot.
The bad news is that I have NOT been able to get the radio stack reinstalled. I have followed all the tips and suggestions, but no luck. If you find that yours finally does boot, then goto start, settings,system info and see if there is info about the radio stack. If it is blank, then you have not radio stack and that is why the long boot cycle.

Radio stack
Ok, when I performed the upgrade, I believe it was only the ROM that upgraded. The radio version is the orignial XDA upgrade which was released to the public as a genuine radio (B) upgrade. I'll look into the SD boot load. Will it automatically install from the SD card? Anyone got any idea?

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?

Did i brick my Tmobile MDA? HEEELLLLPPP

Hey guys i tried flashing my rom using the Shelltool. I loaded the two cabs on the device and put it back to Tmobile 2.26. While i was in the shelltool it told me to do a hard reset and i think the phone was frozen (it didnt go to the normal colorful screen like usual) so i took the battery out of the back and powered it on. I left the software running like it said but it just froze up.
Now my MDA wont move past the Tmobile screen. I REALLY need a hand with this because this phone keeps my life in line! I dont even think ill be able to get up tomorrow because all my alarms go off my phone
Let me know if theres anything i can do otherwise im looking at a Motorola A1200 :-(
kind regards,
Eddy

Hi there,
Not familiar with Shelltool. I do most of my flashing using ActiveSync. Have you tried forcing the phone into Bootloader Mode (hold the Camera button while turning it on). Worth a shot.

If t-mobile was the original ROM on the phone, then just flash it again using the exe (or RUU if you extracted the files from the exe) instead of using shelltool and see if that brings it back to life.

well its stuck on the tmobile splash and shows no actual connection to the machine would it still work?

If you can get into bootloader mode then you should be fine. Just put your device into bootloader and flash wizard love rom or the rom that your device came shipped with.
Good Luck

looks like its working guys but its most likely still going to look and be WM5. Im still willing to try and get WM6 on it tho. I have the roms but its just not working any ideas?

Well, if you're flashing the t-mobile ROM right now then it is going to be WM5. Since you now know what to do if the ROM your loading doesn't stick, try flashing the ROM you were trying to flash again. By the way, what was your IPL and SPL before you flashed it the first time where it didn't work? If it was less than 2.xx then that was your problem most likely. If you're now updating to the latest t-mobile ROM the way I told you to (using the exe or RUU) then your IPL and SPL now should work fine with WM6.

Well I just finished upgrading my MDA to WM6. Here's what I did. First off I
fould out that you need the phone CID Unlocked for it to accept the WM6
ROM. Follow the instructions on this thread by Dr. Puttingham.
http://forum.xda-developers.com/showthread.php?t=285435
This should get your MDA ready provided it is a G3 (thread will tell you how
to tell the difference.) Then follow the directions on mfrazzz's thread:
http://forum.xda-developers.com/showthread.php?t=324632
I had problems with my MMS after the update but after re-installing the WM6
ROM and installing the CAB files by Lurch anf FZZF I got that problem
squared away. Believe me when I say I know what you are going thru. I
was fiddling around with this for about a week. Luckily I am on vacation and
I had plenty of time to read and decipher alot of the info I found. Good luck
and remember to READ, READ, READ. BTW, props to all that contributed to
these fine tutorials and for this awesome ROM. I have it running on my MDA
for three days now and am very happy with it. I am also using the 3.08
IPL/SPL which seems to give me better reception, which my wife seems to
appreciates