Can we upgrade/downgrade using serial (LTP1)? - MDA, XDA, 1010 Software Upgrading

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?

Related

Boot Loader seems to have vanished after upgrade

I've upgraded a couple of US T-Mobile phones to the latest AT&T radio stack and v1.1 of your special edition ROM. Both work really well - however on one of the phones I no longer seem to have access to Boot Loader mode by holding the power button on reboot.
It's not a problem right now, but I imagine it could be if I needed to upgrade at some time in future.
Does anyone have any suggestions as to how I might recover this functionality. Booting with a SD card holding a ROM image doesn't do the trick.
Thanks,
Malcolm
Strange.... Very strange....
Used the 1.1 ROM from Jeff's .exe ?
Yes it's Jeff's 1.1 image in both cases.
The only thing I can think of which might cause this is the fact that the phone with the problem has the 128MB upgrade installed by PocketPC Techs.
At the bottom of your page describing the boot loader it says "When some tests fail it will load the entrypoint of CE into the PC register (and jumps there...)"
I wonder whether it's failing on a memory check then jumping directly to CE....
Any suggestions would be very welcome. Do you think I might be able to update the boot loader via ActiveSync? I'm a little apprehensive as I don't want to lock myself out altogether.
Malcolm
The phone also does not recognise the additional 64MB of RAM through the T2TDisk driver. I had assumed that this was a problem with the driver software but now I see elsewhere on this forum that for others with similarly upgraded phones the driver works correctly.
I don't think it's a hardware problem as prior to the installation of the AT&T radio stack and the SER 1.1 ROM everything worked correctly.
Malcolm
I've experimented a little and I can certainly upgrade the Radio Stack and CE ROM using ActiveSync. Does anyone know of a mechanism by which I can re-flash the boot loader using ActiveSync? I imagine it's possible.
Malcolm
malcolmct said:
I've experimented a little and I can certainly upgrade the Radio Stack and CE ROM using ActiveSync. Does anyone know of a mechanism by which I can re-flash the boot loader using ActiveSync? I imagine it's possible.
Click to expand...
Click to collapse
This is the strange thing we've noticed:
The NBF files needed by "Programme A" contain a bootloader. In fact, when we did our first experments with adaptROM we forgot to put in a bootloader once, and that toasted a unit.
But now if we put in a bootloader, it doesn't seem to overwrite the bootloader in the device, which seems to contradict the fact that we toasted a unit by overwriting it with a CE.
More experimentation is needed, but preferrably after we succeed in flashing with JTAG (which we're making good progress on, BTW)...

I always seem to find the worse level of a crash on my pda

But thanks to this forum I can Usually/so far fix it....however, this time may be different.
I have without problem upgraded, downgraded radio stacks, flashed ROM's and altered bootloaders, but this time tried everything, read every post on this, 4 different seach peramiters no luck. I think I really did it this time Here's where I'm at:
T-Mobile phone edition
bootloader: 5.15
was rom: 4.001 Radio: A.20
on: AT&T Wireless US
Was having trouble with signal realized that I upgraded the radio last time then the ROM. Under T-Mo rom you could run the RSU upgrade and it would reintall the radio stack no trouble as long as you didn't touch the device. This time with A.20 stack it froze at 13%
Where I'm at Now:
Can: get bootloader
Can: change rom's via bootloader
Changed: rom to 4.0016 via bootloader
Cannot: get it to boot past Test only screen which reads G<blank> R<blank> 4.00.16<appears at bottom>
Cannot: connect to activsync
Cannot: get to today screen (no matter how many soft resets+holding volume+power on/off+power cable/no cable or any combonation there of)
Anyone been able to beat this hang? I think this is it for my little guy :roll: unless a wise master can teach me something new to reincarnate it
Can you get anybody with a backup sd card of ce and boot from their machine and try that from bootloader. Maybe that would get you going and then you could maybe flash the radio again.
I had it too with that TMobile ROM. I posted in some threads, read virtually all methods. Nothing worked.
But I eventually fixed it by sending the unit back to the importer for service and had them replaced the main board.
Some of my stories are contained in this thread:
http://forum.xda-developers.com/viewtopic.php?p=25450#25450
You need to wait an hour or more to allow it to boot. It will eventually boot, from there you can retry the radio stack from within windows (copy the four files to your windows directory).
There is a thread on this.
Good luck.
Hal.
thanks guys I'll give it a go with the wait for an hour bit. Already am able to flash the rom so lets hope the one hour or more wait does it :shock: I search all the threads just curiouse if you happen to know where it is post a link in this thread for others. I'm also going to search again and post it..if I find it this time that is :wink:

WANTED: AT&T SX56 virgin ROM file

Can somebody please help me.
As I posted in this post, I scr3wed up my buddy's AT&T SX56.
I have got the thing past being dead, by putting a custom ROM on it.
However, I really need to get this thing back into AT&T mode, with either 2002 or 2003 on it. I will then upgrade to 2003.
Does anyone know where I can get a virgin AT&T ROM so that I can re-flash his system.
Thanks.
-=Nick=-
nickpoore said:
Can somebody please help me.
As I posted in this post, I scr3wed up my buddy's AT&T SX56.
I have got the thing past being dead, by putting a custom ROM on it.
However, I really need to get this thing back into AT&T mode, with either 2002 or 2003 on it. I will then upgrade to 2003.
Does anyone know where I can get a virgin AT&T ROM so that I can re-flash his system.
Thanks.
-=Nick=-
Click to expand...
Click to collapse
Check out Yorch.net
Okay, I'm making SOME progress.
Firstly thanks for the youch referral from kwlandry.
I had found the rom kitchens this afternoon while looking for solutions...
I'm busy flashing the ROM from SD for the umpteenth time.
It seems that whenever I flash the SX56 with an AT&T 30.09 ROM, then I get a hang on reboot.
I am currently trying the 4.00.05 ENG ppc2003 from yourch as it seemed to be non-specific (and a non-TMobile) one.
I seem to have the latest Radio stack (RA.33.02), and have been able to get a couple of ROM's to work.
Does anyone have ANY idea why the AT&T 30.09 ROM would fail in the same place every time? This is definately an AT&T unit, at is has the logo on the front. The phone was originally locked, but has been unlocked during the process.
I'm busy reading/searching the forum, but haven't seem to find this problem anywhere.
Thanks for ANY help.
-=Nick=-
I fixed many XDAs with your problem!
you could send the XDA to Siemens to repair/exchange.
Try flashing back to the original ROM via sd method then upgrading to wm2003.
You can get a copy of the 2002PPC ROM at siemens website. Cut & Paste the following link.
http://www.my-siemens.com/MySiemens...%2FMC%2FMC%2FSX56POCKETPCPHONE%2Fdesc,00.html
Extract the file to a directory, then use the XDA OSimage tool to write to SD card then use bootloader to write to ROM.
After a successful flash follow the same to upgrade to wm2003
You can also try this kitchen http://lumpistefan.dyndns.org/
BTW - the phone has to be fully charged. That might be the cause of your hanging issue.
I have posted this in answer to your other post, try using a diferent memory card for upgrade to wm2003, I had this problem when using an mmc memory card to upgrade to WM2003, it hung every time even though it seemed to complete correctly, I changed to a different memory card and had instant success.
Yes! I agree also. But, though "mmc" and "sd" cards are similar, in this case the process calls for an sd card. The size doesn't seem to matter, I use a 512mb, however some people have had issues with device detection. So, a 64mb card is recommended. Make sure it is formated before use. And again a fully charged phone is unlikely to have problems so save your battery till all requirements are in place. Also DO NOT DO A HARD RESET! untill you have a successful install. You could lose you GSM ROM.
Thanks for all the replies.
I have successfully flashed back to the original rom; I downloaded it from yorc.
Having got the device back up and running, I tried the upgrade to 2003 again; using the Siemens software in the cradle solution. Didn't work.
The battery was definately fully charged (90% or higher) at all times.
I will look to try another SD card, and see if that makes a difference, it just seems strange that the card works to restore WM2002, and either card or USB approaches to upgrading to WM2003 fail.
The card I've been using is a very generic 128MB MMC card.
Again, thanks to everyone for their suggestions.

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.

wizard_radio version-2.25.11 KILLED MY WIZARD

Bugger. It was all working so well, then, in a 'diminishing returns' attempt at upgrading to the latest radio, I flashed wizard_radio version-2.25.11 from the Ftp site.
Bugger, has completely killed my wizard.
it is now 'running' unbearably slowly, with no radio connectivity, no activesync (so I can't flash another ROM), and, bizarrely enough, seems to have reset to an earlier ROM image.
Is there any way I can do a ROM install off the SD card? or does anyone have any bright ideas... (have tried hard resets but this returns it to a corrupt state; SPB back-up doesn't seem to do any good).
It's expensive brick time. Any help very much appreciated
well you say it's running slow therefore it isn't a brick, whynot just redo the ROM? perhaps the file was corrupt or you didn't get a good install for whatever reason, if it's booting up there is hope however
no AS connectivity!
there is a link on another post I missed earlier; am following up an let you know.
First things First....
What Rom version were you running prior to flashing the 2.25.11 Radio Rom?
Is your device CID unlocked (which is different from SIM unlocked).
IF you reset your device and enter Bootloader mode, then plug in the USB cable do you see "USB" in the lower left of the screen?
no 'USB'
hate to admit, but I didn't note down which ROM version; I installed this one RUU_Wizard_1050402_101_11210_O2_ENG.exe
two weeks ago (and of course it was running fine, but I decided to upgrade the radio from a '1.x' to an AKU '2.x', using wizard_radio version-2.25.11, which wiped the device!)
I am reading a couple of other threads, and there are a few people with similar problems.
After a hard reset, I get the RGB colour bars (as per normal bootlader) but only see IPL 1.01, two 'blank' lines, then SPL 1.01. the bottom of the screen, where I would hopeto see USB, is just a blnak white bar.
I am looking everywhere to see if anyone has a backup image I can copy to my SD card to run from there.
Ahem
yes, is CID unlocked
THE CURE
ok, thanks to the tip from a99tandem.
Reset, holding down the camera button, allows you to go into boatloader, and you can flash a ROM from the PC using RUU. Bootloader comes up with 'USB' in the corner.
Thank god for that; that's 5 hours wasted...
Now I'll explain what you did wrong.
If you read the thread that had all of the Radio Roms you would have seen that 2.x Radio Roms DO NOT WORK with 1.x Bootloaders (IPL/SPL).
You could have fixed your device by simply flashing a 1.x Radio Rom (there is one listed).
If you want to use a 2.x Radio Rom you must upgrade to a full (included Bootloader, OS, & Radio) 2.x Rom FIRST.
I hope this helps...

Categories

Resources