JasonLP
28-03-2004, 01:20 AM
I am having problems with my XDA (T-Mobile Phone Edition). Here are the symptoms:
- The system runs extremely slowly (it takes several seconds for the start menu to come up, for instance).
- So, I soft-reset the device.
- The T-Mobile splash screen comes on with version info (4.01.16), but with an *empty* R and G above them. (No radio version displayed, and no whatever-G-stands-for displayed).
- I wait.
- I wait some more.
- After waiting about 20 minutes, the Today screen finally comes on. Again, the system is extremely slow, and the phone part does not work at all.
- If I try to boot into the Wallaby boot loader, I get the dreaded "GSM Error".
A little more info:
I had upgraded to 4.01.16 at a ROM kitchen about a week ago, as well as upgraded the radio stack to the latest T-Mobile (6.25.02 I believe.). The system was running fine until yesterday.
When I first discovered the issue yesterday, I tried several attemps to reboot, then finally had to resort to a hard-reset.
The hard-reset succeeded, then I reinstalled all my applications, settings, and data. I did a couple of soft-resets to be sure it was working. It was.
This morning, I noticed the extreme slowness issue again, and soft-reset the device, and the same thing happened.
So, I happened to be near my local T-Mobile retailer, and explained the issue. He played with the device for awhile and was on the phone with a technician from T-Mobile. He hard-reset the phone and declared it fixed.
He did say he had to change the internet settings from internet3 to internet2. My internet had been working fine all week, and I'm sure I was on internet2, but in his words, "If you are on the wrong internet setting, you can't connect to the internet, the phone, or anything." Now I know he's either full of it, or misinformed, although he was extremely helpful and pleasant.
So....the question is: What *is* going on with my phone? I saw a reference on this board to something called repair.zip, but I didn't see it associated with any particular symptoms, so I'm hesitant to try it yet.
I'm 90% sure that my phone isn't permanently fixed, so I'm putting this out to the gallant men and women of xda-developers for insight.
Thanks!
-Jason-
- The system runs extremely slowly (it takes several seconds for the start menu to come up, for instance).
- So, I soft-reset the device.
- The T-Mobile splash screen comes on with version info (4.01.16), but with an *empty* R and G above them. (No radio version displayed, and no whatever-G-stands-for displayed).
- I wait.
- I wait some more.
- After waiting about 20 minutes, the Today screen finally comes on. Again, the system is extremely slow, and the phone part does not work at all.
- If I try to boot into the Wallaby boot loader, I get the dreaded "GSM Error".
A little more info:
I had upgraded to 4.01.16 at a ROM kitchen about a week ago, as well as upgraded the radio stack to the latest T-Mobile (6.25.02 I believe.). The system was running fine until yesterday.
When I first discovered the issue yesterday, I tried several attemps to reboot, then finally had to resort to a hard-reset.
The hard-reset succeeded, then I reinstalled all my applications, settings, and data. I did a couple of soft-resets to be sure it was working. It was.
This morning, I noticed the extreme slowness issue again, and soft-reset the device, and the same thing happened.
So, I happened to be near my local T-Mobile retailer, and explained the issue. He played with the device for awhile and was on the phone with a technician from T-Mobile. He hard-reset the phone and declared it fixed.
He did say he had to change the internet settings from internet3 to internet2. My internet had been working fine all week, and I'm sure I was on internet2, but in his words, "If you are on the wrong internet setting, you can't connect to the internet, the phone, or anything." Now I know he's either full of it, or misinformed, although he was extremely helpful and pleasant.
So....the question is: What *is* going on with my phone? I saw a reference on this board to something called repair.zip, but I didn't see it associated with any particular symptoms, so I'm hesitant to try it yet.
I'm 90% sure that my phone isn't permanently fixed, so I'm putting this out to the gallant men and women of xda-developers for insight.
Thanks!
-Jason-