Related
I have been using the new XDAII for about three weeks or so and already I have experienced over 6 times critical crashes that caused the device to not even be able to restart after reseting. Even more troubling is that even when pressing the on/off button and hard reseting, the problem still cannot be solved. The only way I got around it is by actually removing the battery and letting it sit for a few minutes, put in the battery and then performing the hard reset. Of course, then I lose all data that was previously on the device. Right now, what I do is use the xBackup program to back everything to SD card and just wait for the device to crash. Then ultimately recovering. I can get around, but this is really quite annoying.
I have written to O2 about it and they said something about a radio version 10513A0, and that if this is the version (and it is), then I need to either register (which I did and wait for some upgrade), or send it in to O2 collection point for repairs. I really don't want to send it in because then I would have nothing to use (since its both phone and PDA). I just don't see why O2 could not just simply fork over the upgrade software. Also, I have experienced twice that the device would suddenly no longer be recognized by Activesync (newest version). It would automatically connect as GUEST and nothing could be done about it. No shuting down Activesync and restarting, or rebooting computer or/and xdaII, or even removing and reinstalling Activesync could solve the problem. Again, the only solution I have is to perform the infamous full reset, wipe out the whole xdaII and then everything works again.
Anyway, all of this is really killing me here, just wondering if anyone has experienced this kind of situation and maybe have some advise.
By the way, the Bluespoon Digital seems to work fine with the XDAII although sometimes it does crash and a pairing must be done again, but definitely not like the Jabra 200 problem.
I had the same sort of problems with my first XDA-2 and as time pasee the problems got worse, So i returned it to o2 and got another one, same software and hardware versions, but this time with no real problems
John
XDA II Critical Crash
I have had the exact same problems as you experienced and was about to throw that gadget out the window... but then
Following advice received from an XDA II owner I tried the following:
I hit soft reset each time upon seeing the red text in the lower right corner 5 consecutive times. Then I waited and my XDA II came back to life effectively performing a soft reset rather than having to do a hard reset. Fascinating, let's see whether you have as much success !!!!
Thanks for the tip... I'll try it next time it happens again! However, I'm still wondering about the ROM v 1.06 and that Radio software upgrade. Thanks!
I'm also finding the XDAII needs a hard reset more often than the XDAI (although fewer soft resets). Had to do it twice last night, very annoying. Interesting tip about the soft reset at the boot screen, will give that a try next time.
O2 really should do something about it!
Ya, I totally agree. All this reseting and crashing and recovering is really not acceptable. The product features are definitely good and they did make some improvements, but this kind of quality is a definite downgrade. Even O2 admits that if your radio number is 10513A0 then you should send it in to a collection point for a software upgrade. They also insisted on registering which I did, but I just don't understand why they could not just simply post a downloadable software upgrade or ROM upgrade so that we don't have to be without a device. After all, we are talking about something that is both your PHONE and your PDA.
The ROM upgrade is definately necessary. I sent mine in and after that, no hangs whatsoever. No more hard/soft resets at all either. :lol:
if only it was so easy
I would have sent it in, but since I am traveling and don't live in HK, there is just no way to send it in. Besides, it takes about a week, which means nothing to use during the time. O2 really should be more considerate about this. If this was just a functionality upgrade or a boost in bells and whistles, waiting is reasonable. However, we are talking about crippling disfunctionality in a US$800+ device, they should atleast have the sense to post a fix to solve the problem. I heard something will be released in January, I wonder if this is confirmed. I am really sick of waiting. After all, MDA and T-Mobile supposedly already have something out. If they don't do something soon, I would really reconsider anything from O2 next time.
I have experient the same problem on my XDAII, and after 7 times hardreset during 14 days business trip in USA. I send it back to O2 and wait for the solution(already 1 week pass). And even a hardreset sometime could hardly be reached. You need to try 6-10 times. I think it should be a hardware problem because I acutrally upgrade my rom to a newer one(and not the english version), and after two days, I lost my phone function again. I have faced the same problem on my older PPC phone once(LENOVO ET180) and after I send it back to the vendor, they said the mainboard has failure, need to be replaced. After doing so, it works 6 months without a hardreset. I saw the same issue on PPCSG and PCCW.net, they all send their PDA+Phone back to the service. I think you better do it now as maybe there is no a ROM upgrade could solve the problem.
Goog luck. and if without those issues, it is really a perfect PDA+Phone. I love it. When I faced those ****, the only thing I could think is to buy another XDAII
I've the same problem
I've tried your tip to restart my Mda2 with XDA2 rom, and it works!!!!!!!!!!
Now I'm looking for a new Rom upgrade to change my radio version...
Still I think it's the solution and not to replace the radio hardware...
Cant Trust My XDA II
Well it's now Dec 2004 and I ALSO have the same problem.
I've only had my XDA II a couple of months and already I'm quickly loosing my patience with it!!
It crashes at least TWICE a week causing me major headaches.
If I was abroad and it did this I would be in severe trouble.
I brought this as a business tool and I'm afraid it is to unreliable to place
my trust in...
I have the latest ROM update installed
I can ill afford to send it in because it holds my customer base,
day to day stuff, Navigator and many other stuff I use on a daily basis.
"O2, what can you do for me?"
Topdog38uk, what software have you installed - especially any today plugins?
rgds,
Alex.
sigh... i haven't had such a problem since i bought it..... till i update the new rom from O2 uk site... now i feel like throwing to on the ground lolz. anyway i just installed WM2003 SE upgrade mysterman from the forum and 1 crash so far.... :roll:
Ok, I have spent the past few hours both ruining my phone, and then trying to fix it
So here is my situation. I have a newly purchased SX56 Phone that I decided to try to upgrade using the exe off the Siemens site. I made sure my battery was fully charged, plugged into the cradle, and started the process. At about 10% during the Radio Stack upgrade, the phone failed. My desktop told me to unplug the USB cable, and then reset, at which time the Radio Stack would finish updating. This of course didn't work, and I got the 1% error. It kept rebooting with the 1% error. I proceeded to try to soft resent, and go the now infamous white screen.
I don't currently possess an SD Reader, and its one in the morning, so I don't imagine getting one until tomorrow. In the meantime, after reading MANY posts, I'm not sure what to do.
I suspect that my Radio Stack is gone or fried, and I'm not sure I understand if I can somehow reload it or not?
I'm assuming my current ROM is still intact, only because for one brief second at one moment, I got my PPC up again but it was barely functional, didn't have a start menu, just a white bar at the top of the screen where the start menu bar was before. Since then I've only gotten white screens.
I have tried doing the boot-loader just to see what I got on my phone, I apparently have Wallaby 5.22, but I don't understand if this is a bad thing or not, as I saw many people talking about getting down to 5.17 or 5.15??? Furthermore, I didn't have an SD card in the phone when I pulled up the bootloader, and the phone just got a GSM ERROR. I have yet to find informative info on if this is ok considering I have nothing in there, or if this is a problem for me.
I have also tried the volume + soft reset to get back to the 1% error, but I haven't seen that yet.
My end goal is to have a functioning phone, I would like to have WM2003, but its not necessary. I'm just not sure anymore what methods to try from my current situation.
Keeping in mind I am frozen on the white screen page, Should I:
1. Try to reinstall the Radio Stack first? (and if so how? Does it involve copying files to a SD card? I assume so because I cannot connect to my phone anymore through active sync)
2. Try to get my PC2002 or WM2003 up and running and not worry about the Radio Stack just yet? (also how if this is the case?)
3. Try to return my phone? (This is a last option, because I'm not sure I can even find this phone anymore in my area, and I really like it, and would love to continue to use it)
and finally, am I pretty much screwed on charging my phone until I fix everything else?
Thanks Again
Thanks for all the great information
unless you are in US
then installing the us radiostack which is shipped with the s56 update is a big nono!
imho then installing any radiostack unless you have gsm signal issues or if your phonecompany tell you to is somewhat a risky buiness
Rudegar said:
unless you are in US
then installing the us radiostack which is shipped with the s56 update is a big nono!
imho then installing any radiostack unless you have gsm signal issues or if your phonecompany tell you to is somewhat a risky buiness
Click to expand...
Click to collapse
I am in the U.S., and ATT Wireless sent us all text messages telling us about the upgrade,...
If the radio is knackered the only option is to return it or get somebody on the forum to help that has jtag kit for direct chip flashing. Personally I would send it in for replacement.
cruisin-thru said:
If the radio is knackered the only option is to return it or get somebody on the forum to help that has jtag kit for direct chip flashing. Personally I would send it in for replacement.
Click to expand...
Click to collapse
I seem to see others talking about reinstalling the Radio Stack using RSUpdate, etc...would this not work for me? How would I know if my RS is completely gone, or just malfunctioning because of a bad install?
Not quite sure what the issue is with this one. Back in the beginning of the year my XDA II fell from waist height when the carry case snap popped open (notebook bag brush across the front catching on the flap). The only noticeable problem after that was that the power button no longer works, so I have to power it on by pressing the phone or address book buttons etc.
About a month and a half after that incident the phone suddenly just stopped getting signal. I was using the standard shipping firmware with a few apps. Soft reset, hard reset both failed to fix the issue, the phone simply will not pick up the network. Interestingly enough if I play with the phone settings and go through the process of manually selecting a network the phone WILL pick up available networks in the area (this kills my idea that the GSM radio failed altogether). For now I've had to switch back to a junk phone as I've been unable to figure this one out. Anyone have any ideas on this one? I'm using T-Mobile for a service provider and I'm based out of California.
Also, does anyone know of a place that can do diagnostic/repairs here in the U.S.? So far my searches have come up empty.
Thanks in advance.
Give this a try:
Reflash the phone with any version of ROM and it should start working fine again. I think the problem is that you're radio firmware somehow got corrupt.
Ok, guess I'll have to give it a try. I've been avoiding trying the slightly riskier stuff as I got this thing via an independant third party, so warranty/support are iffy.
Is there a general release ROM that I should be looking for (using T-Mo in U.S.)? Or should I look to cooking my own (which I'd rather not)?
You can try upgrading the ROM with the same branded one. That shouldn't void the warranty.
I.e. If you've got an O2 device, get the new O2 ROM
Reflashing
I have had a simular problem with hard locking. Finally my phone quit working all together. I went into boot loader mode and flashed it. It's like having a new phone again. So yeah.. I think the ROM's can get corrupt.
Brandon
NeoCole: Looks like you are using T-Mo in the U.S. Mind if I asked what you flashed yours with? Did you use a specific ROM, Radio Stack version etc.?
I'm running an unlocked i-mate (contradictory to my subj title, I know).
Flash it with the T-mobile 1.72 ROM
ROM Version
Well.. I flashed it with the IMATE 1.72 ROM and used most of it's extended ROM. I used the battery Meeter from the Qtek extended rom. I built most of my extended ROM Myself.
I look at T-Mobile's Beta 1.72 ROM like I look at Windows ME. Both should have never happend. I can't count how many times I had a hard reset with the T-Mobile ROM. I'm not sure if it was a combination of the programs I was useing or not. I saw a post that said SBP was possibly causing the problem. So I quit using SBP products. Later I still had to HARD RESET from time to time. Now that I'm running differently, My device has never been so smooth.
Let me know if this helps,
Brandon
Looks like I'm pretty much screwed. Without a working power button I can't do a hard reset into bootloader mode. When I try using a utility app that allows me to do a hard reset I can't hold down the jog dial at the same time. Good times.
*edit: yeah, that would be 'can't' hold down the jog dial.
You don't need to boot into the bootload to perform an upgrade... the upgrade software takes care of everything for you (except the hard reset at the end)
All you need to do is sync through Activesync and then run the upgrade program.
I would (and have!) flash the imate 1.72 ROM. It is very stable for me and HAS improved the battery life of my imate.
As stated above, just start the flash process and it will put the device into bootloader mode and perform the flash. It will need a HR at the end, but since your power button is not working, maybe you could remove the battery, slide the red slide/switch back into place for a few seconds as if the battery were there, then slide it back, put in the battery, slide it back into place and press one of the puttons to turn it on.
Hey . . . it might just work!
imate 1.72 ROM did the trick. After I actually READ all the posts regarding the ROM I realized it came with an installer and got that done. So far so good. Now if I could only find my missing tomtom 3 cd key that went MIA during my last move
Hey, that's fabulous! Welcome back to the world of convergence.
Hi all,
After spending 2 days with my vario my dreams of a half-decent smartphone are shattered.
I've got a C500 which hasnt really caused me any problems in over a year, now 2 days after having a vario i'm almost pulling my hair out.. can this phone possibly have been released in such a bad state or is it just mine?
For starters it crashes, not now and then, but like it's a hobby of the vario's, i dont think i can leave it for an hour, come back and find it hasn't hung in some form.
Sometimes i have to do a soft reset, sometimes, i can press the power button, get the screen to light up but can't do anything. Sometimes I get icons but when I click them i'm told the shortcut doesnt exist.
Ooh another thing it seems to like doing is randomly going into flight mode, and one really good crash was when i called it and the source phone could hear the ringing but the vario was just sitting there doing nothing.
So is it just mine or is this the most unstable phone the UK has ever seen? Is it worth me asking for a replacement, or just flashing the k-jam/qtek rom over the t-mobile one? Is there a way to backup my t-mobile rom and flash it back should i find the qtek/kjam rom does the same?
I've tried hard-resetting then cancelling all the t-mobile gubbins that loads from extended rom, but that didnt make any diference.
Any advice gratefully appreciated
Thanks
Personally, I'd say get T-Mobile to replace it! Unless you've installed a buggy piece of 3rd party software (but if you did, you wouldn't on here complaining about the phone you'd be complaining about the software, right?).
I also have an MDA Vario. I haven't touched the Extended_ROM (was going to, had a look and decided it was running fine so don't mess with it).
It's solid as a rock. As per a thread on howardforums asking how many times per day have I soft-resetted the phone and my answer was an average of zero.
I hard reset it on the day I bought it (after installing GPRS Monitor which knackers the backlight turning back on after sleep) and took the battery out after T-Mobile decided to disconnect me from their network (at their support line's request).
Anyway, it's on 24/7, never needs a reset of any kind, gets mobile emails via ActiveSync and is generally a wonderful piece of kit!
List what apps you've installed (even if they're T-Mobile supplied ones from CD) since buying the phone as there may be something buggy there. If not, definitely get T-mobile to replace it as it's certainly not a crap model (mine is absolutely fantastic).
Thanks Andy,
I've literally not installed anything, i'm just about to install pocketcommander but that will be the first thing i've actually installed. I've hard reset the phone this morning and it's already hung once on me (
I'll give tmob a call and see if they can send me another out today or something
Yeah, then you've definitely got a knackered phone. They should replace it (how long have you had it) without problems.
Hope you enjoy the replacement, they really are a great bit of kit
Well just had my first ever dealings with tmobile supoprt and it's as bad as the phone
They say because my contract/phone is only 3 days old i need to go back to the people i bought the phone off to get a replacement, problem is they'l want me to send the whole boxed thing uip and all the box etc is at home since i work away during the week
That's got to be faulty, like others have said.
WHen I bought mine, (T-Mobile shop in Leeds), I was told that if it was faulty within the first 28 days, there'd be a straight replacement issued immediately.
Don't accept anything less.
For what it's worth, I always try to be exceptionally pleasant when returning things rather than going in "all guns blazing"; it gets results a lot more often than the "I know my rights" approach. Of course, when it all comes down to it, the "i know my rights" approach might be necessary, but hopefully it shouldn't be.
The phone is superb, so stick with it even tho it is a bit of hassle for you.
good luck!
hi there no problems with my vario either. seems to work fine. no soft/ hard resets needed so far. have had it for 10 days. only thing is after the xteended rom instals there is a file called canned text in words which opens up in a crazy language. does not go on hard resets. but does not cause a problem either. any ideas on what this file is. have othar vario users noticed this file. please help.
_Belial said:
Thanks Andy,
I've literally not installed anything, i'm just about to install pocketcommander but that will be the first thing i've actually installed. I've hard reset the phone this morning and it's already hung once on me (
I'll give tmob a call and see if they can send me another out today or something
Click to expand...
Click to collapse
may not be relevant to your problem, but if skype is installed on yours from the hard reset install, it may be worth removing, on the k-jam as soon as i removed skype, reseting stopped happening
I'm having a wierd problem with my Hermes. I have the Scnaps 4.01 WM6 rom on my phone right now, but the same thing happened with Blacks rom when i was running that.
Sometimes when i turn it on, it says it has signal so i try to make a call i get operation failed, and then you see the signal drop back to searching, it finds the network and then logs back on. Same thing happens even if i dont make a call, turn on the hermes, and look at it, has signal, then 10 seconds or so later it drops to searching (it never really had signal) then logs back on, and then sms's get delivered. I've also had people try to call me during this time and it's like the phone is off.
I've tried a few different radio versions recently but same behavior with all of them. 1.54.30, 1.54.07 and currently on 1.43.
Something else weird is the fact that it seems like (I could be wrong) this only happens after having the rom on for a week or so, ie after flashing a rom, the first week or so i don't get the issue, then it slowly starts to happen - this could just be my imagination.
Has anyone else had this issue? Any ideas/suggestions welcome, thanks
Hi Ferni...
This is something that is becoming quite an issue recently
Firstly, have you made sure the SIM contacts are nice and clean and everything is fitted OK - and have you tried a different rom image? If not - try these first.
Secondly, where abouts in the world are you and what network are you on?
Thirdly - when did you install 1.54.30 and 1.54.07 - did your problems start before or after you flashed a 1.54x radio - and what radio were you running before trying these.
Finally - What other information do you have about your device - is it a herm100,200 or 300, what IPL/SPL is it.
Sorry for the 100 questions, but I'm investigating these issues at the moment as a lot of users have had similar problems especially after using radio 1.54.x as this thread discusses.
Thanks for the reply. Just read the other thread you linked to (and the threads it linked to). Interesting to know i'm not the only one.
I just pulled the sim out and gave it a rub and the contacts and put it back in. I also had a bigger battery in it, so i removed that and put the standard one back in. See if that makes a difference.
I used to run the black rom, now I run the schaps one, trying to avoid flashing it again just a pain to resetup everything you know....
I'm in Australia, on the Optus network. The JasJam is actually only sold by Telstra here, but i got one 2nd hand and use it on the optus network fine (Optus sell the Dopod). The latest radio rom 1.54.30.10 i belive is actually from Telstra - in the offical WM6 rom from them for the JasJam.
As for when i flashed which rom and when the problems started happening - i can't really say sorry, i didn't keep track. I've had the phone around 6 months, flashed it with a cooked WM6 rom (black i think) when i first got it, i probably updated the radio as well.
How do i tell if it's a 100, 200 or 300? Also not sure what SPL it is, HardSPL or something?
Tempted to flash it to the official telstra rom released recently with the latest radio, so if it does die completely i can send it back for warrenty. What do you think?
Thanks for the info - every little helps at the moment!
Firstly, yes - the radio you're running is native to the area and network and so if you're running 1.54.30.10 and it goes duff you should be covered by your warranty so don't worry. Also, it's not certain yet that there is definitely a problem with this radio so don't loose too much sleep. (Most of the problems linked with this radio that I've researched so far seem to be coming from Europe and after rolling back).
As for flashing with the official ROM, that's a decision for you - however in the cases of sudden GSM death, the phone will still boot to Windows and it is still possible to flash the OS and bootloader roms (just not the radio) so if it did go bad with an unofficial ROM on it you should still be able to roll it back - again sleep easy ;-).
As for the problem - the steps you've taken are a good start, see how it goes and keep us informed here.
It may be worth also trying to manually set your band (if applicable on your network). Sometimes problems like this can be caused by issues on the network itself and trying an alternative (maybe a friends) SIM card for a different network or even manually switching the phone to GSM (if available) can "cure" a problem (although it's a pain if you specifically need to use 3G and it's data speeds!).
Finally - to see your full device information you need to enter the "bootloader" (tricolour) screen. Hang on to this information on the bootloader screen as it can be useful if you ever encounter a bad flash.
To do this, hold the OK button on the left of your phone and the power button on the right then press the little reset button with your stylus. You will then see the model at the top with the IPL version below it and then the SPL version below that. To get out of the tricolour screen, press the reset button again. Needless to say this won't erase anything or damage your device but make sure you close your apps and save your data first
I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.
ferni said:
I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Click to expand...
Click to collapse
What radio are you currently running? Thought it was 1.54.30.10 or did you change that the other day when trying a new ROM?
ferni said:
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.
Click to expand...
Click to collapse
*IF* this is the sudden GSM death syndrome then it will progressively get worse unfortunately - but it might not be that (think positive!)
[edit : removed - brainfart you answered my question] Incidentally, just updated this thread here - Look at post #60, it's a long post but there is a couple of possible things for you to try there (multiple flashing on a "chilled" phone) for users who STILL have some GSM connectivity... Might be worth a go and certainly could do no more harm... The post itself is very technical but just follow the instructions about 3/4 way through the post and ask any questions back here in this thread so things don't get too confused!
In terms of flashing your ROM - when you _really_ feel the phone may die _very very soon_ then it's worth considering flashing it with the latest OFFICIAL rom from your provider while you are able to do a full flash but don't leave it until DHL are at your door to collect it just in case you need some help!
Oh yeah... and finally for tonights post - Rolling back from Olipros Hard SPL... back to the normal, official SPL - Mr Vanx has written a fantastic guide to this here complete with illustrations - That should save you some searching
The SPL rollback, of course, should be the very last thing to do before shipping it back under warranty of course tho - just incase you need it in the mean time!
Good luck - and keep us updated - particularly if all works again (or not)forum.xda-developers.com/showthread.php?t=299070&page=32
I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?
ferni said:
I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?
Click to expand...
Click to collapse
Yes. Crazy as it sounds, if the previous radio caused "logical" bad blocks - a combination of a couple of flashes in quick succession with the PLA at a cooler temperature might recover them! (temperature issue came from the data sheet for the chip itself - Apparently more efficient writing at temperatures a minimum of 10C below ambient).
Good luck - let us know how it goes... I've got my fingers crossed you'll have a Hermes with it's wings back shortly
Last night the phone got worse, i had a missed call, tried to turn the unit on to see who it was and it wouldn't turn on, so i soft reset it, it booted up ok, but wouldn't pick up a signal.. eventually after about 5mins it did, but then it locked up. So i pulled my sim card out put it into an old phone which i'm using for now.
This morning came into work and put it in the fridge for 15mins, and flashed the latest radio firmware on it. Then flashed the latest official telstra rom onto it (getting ready for warrenty). That's just finished, only step left is to put the original boot loader back on. May test it again for a couple of days to see if i can get it to do the same thing on the offical rom/radio before i send it back. Will let you know.
Thanks for your help so far.
Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried
ferni said:
Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried
Click to expand...
Click to collapse
We did indeed - Ah well, at least you're covered by warranty
Mr Vanx has written a fantastic guide to rolling your bootloader back - complete with illustrations. (repeated for others who've just started reading this thread)
Yeah hopefully it gets covered under warrenty. That bootloader guide worked perfect
For anyone who cares, they replaced my radio board under warranty - I now have a new IMEI number. Haven't got the phone back yet to test to see if it's fixed.
Did you ever upgraded the Radio ROM ?
Or was it always 1.43.
My first ROM only upgrade.
http://forum.xda-developers.com/showpost.php?p=1462158&postcount=292
Yeah i had tried a few different radio roms before this. I suspect it didn't like being flashed so many times.
I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?
I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works
gondalguru said:
I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?
Click to expand...
Click to collapse
I flashed one of the wm6.1 roms and ended up with 1.54.07 radio and was getting the "modem disconnected" error message everytime I tried to log on to the internet.
I reflashed the original WM6.0 ROM from AT&T and then reflashed my radio to 1.48 (can't go back to 1.16 because of the radio bootloader I think) and then tried to log on to the internet.
That didn't work
But then I made a phone call to my home phone
tried logging on and it worked.
Been working fine since
crossing my fingers and hoping I dodged the bullet, not gonna flash again til ATT comes out with 6.1 then if it acts up even a little I am gonna send it in for warranty repair.
I hope this procedure works for you mate.
pedro2k said:
I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works
Click to expand...
Click to collapse
Not exactly sure where this setting is, the closest thing I could find was to install HTweakC. And now I have auto attach off. I also live in WI rural area, and 3G has been growing. Coming closer my home, and when I go to work it switches to 3G from Edge and I believe this is the biggest cause of this problem. I will let everyone know if this has helped me or not.
Thanks pedro for your suggestion. I will try that and will report back.