Database Users

OT: Random XDA Reboots

This is slightly off topic, but I figured this board was still the best place to ask (and hopefully get an answer).
Has anyone experienced random soft resets from their XDA? Often when I press the power button to turn on the screen it just resets on me. After the reset, I often have voicemail - so apparently while the screen is off, the XDA is freezing up not receiving calls or SMS and then reboots when I turn it on.
I have had this happen to 3 of 4 XDA's now. When this happened with my 1st two XDA's, I called TMobile support. They had me hard reset and when this did not resolve the issue, they replaced the unit (it took a day or two for symptons to re-appear). My 3rd XDA was replaced on an out of warranty repair (cracked screen at concert), leading to my 4th XDA which is my current one.
It is a Tmobile USA XDA. Right now I am running WM2003 4.0.11 and RS 6.24.
I find it hard to believe I've ended up with all these hardware defects. Which is why I wanted to ask other users if they've had this problem. I am debating re-flashing the Official Tmobile ROM, waiting to see if the problem continues and then getting another hardware replacement. My other thought was to wait for the Official TMobile WM2003 ROM and try that version. Could this be some software defect?
-murph

I noticed the same thing happening when I was running WM2003 4.0.11 and RS 6.24. It became so bad that I went back to the original Tmobile ROM and the problem disappeared.
Also, I heard this is corrected in WM2003 4.01 ( the latest tmobile update) that is circulating out there. But so far I have not gotten it and tested it.

XDAII Critical Crash

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:

XDA II: Phone not working anymore and where to repair in US?

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.

Hard Reset when Registering to Network

Hello Everybody,
I have just another cool prob.
My unit is HARD RESETTING every time I reach a radio signal
Radio Stack: 1.05.00
ExtRom: can't upgrade, defected
OS: 1.13 ITA
Can it be a wrong Radio the solve? I will now begin all what I maked:
1) The great error of upgrade to 1.12 Imate ITA from an ITA Qtek
2) The repairing center said that there was a mix of Qtek and Imate: and that it's impossible to upgrade
3) After trying to upgrade with an almost dead battery (and failing 2 times) I think that I've defected the ExtRom: but that would not be a problem, only for the repairing centre that would to change the MoBo
4) Suddenly I notice noitceable interferences when I was calling and when gaining any tipe of signal
5) Tried MANY radio stacks (and upgraded to OS 1.13 ITA too
6) And then, everything worked "fine" besides the interferences, the ExtRom, and the low temperature mess that will not wake up the Unit, but the Radio Stack was still functioning
7) And finally the real mess: I was listening to music with TCPMP, when a call arrived. I've answered normally, and closed the call. HARD RESET.
So, after few seconds to register to the network, it Hard Reset. Not sure of this, but I think that it can be the interferences that occurs. If it is, I'm supposed to pay the hardware reparation, 230+ €. Hope thet a Radio Upgrade will solve the mess. Otherwise, I will broke this deficient "phone" (that isn't anymore on how it seems)
Note that all the other things are perfectly functional, even the bluetooth stack.
After this, I will probably write all the things wrong on this f***ing device...
ANY HELP IS WELCOME!
From: MocciJ

This is an upgrade of the mess
First the interference is called RF leakage (or something similar)
Second I've tried to upgrade the radio stack to 1.13 and what I've found: The problem persist! :lol: :lol: :lol:
Third, I think it's really the RF: it gradually appeared and so... PUFF!
I will also add that if a sound was made by the ext spk when RF is audible, it was amplyifing... To mention, the red button was making ext sound... Finally I will say that the RF had destroyed himself; I can't hear it anymore, because it's HARD RESETTING first.
Mine is a faulty device, I know. I loved it too, I felt really bad when it hard reset in this manner. I also know that I have payed 420€ for a phone pda... Now it's value it's below 200€... I'm gonna cry
Now I only hope the repairing center will accept it. SURE IT ISN'T A ROM PROBLEM. Now I only need someone that can explain me how to get rid of the error 113 that face me in the ExtRom Upgrade... Because if I succeed in this and upgrade to a pure Qtek rom, there will be some chances to regain warranty... Without pay anything...
DON'T TRY TO PUT A DIFFERENT BRANDED ROM ON YOUR PDA
AND THINK BEFORE DOING ANYTHING STRANGE
THINK ABOUT UR WARRANTY!!!
From: MocciJ

Yes, I've tried it.
Sure, I think it's impossible repairing it for myself. Sigh.
I also noticed that everytime I Hard reset the unit by the network registering prob, my ext speaker is WAY degraded. It probably seems that the interference is eating my speaker...
The ONLY thing that I can do is to try to upgrade the ExtRom bypassing the error 113. By doing this, the repairing center can declare the integrity of the rom and the native faults.
Luckily I've left my old phone, the Nokia 3200, still perfect...
Thank'u anyway for the interest...

The message above is the answer to a guy that misteriously deleted his comment... :?: :?: :?:

Bad replacement niki?

I had sent a phone in for repair, which was then said to be unrepairable and so I was given a replacement niki (however the replacement was a refurbished one).
Its only been a week or so but I have had major problems with calls. Most of the time I cant make or receive calls even though the signal bar has two or three bars. The phone says its dialing but it doesnt and ends the call automatically. If I ring my phone it goes straight to voicemail! Note that I said "most of the time" because my phone calls do go through soemtimes but thats like once every 20 or so tries or if I make a phone call immediately after a soft reset or just get lucky!
The other functions of the phone work fine. I have done a hard reset thinking it was something I installed but the problem is still there. Done another 4 hard resets (each time trying something different like taking the battery out before the custom orange stuff is installed) but with no change.
I did a search and came across another thread but it wasnt really solved and blamed it on S2U2. Obviously S2U2 cant be the cause for me since the problem is there even after a hard reset. (http://forum.xda-developers.com/archive/index.php/t-393077.html and http://forum.xda-developers.com/showthread.php?t=387615)
Im thinking it could be that the radio version is old (since it is a refurbed version) and also I remember reading about poor signals some time ago which was solved by changing the radio version (and is also probably why I didnt have this problem with my original niki).
Note: I have also tried the sim in another normal phone (samsung e900) and it worked fine so this is definately a problem with the touch dual.
A little bit of info:
Im with orange in the Uk,
the ROM version is 1.31.61.10 with a ROM date 10/30/07
and the Radio version is 1.58.16.27.
(Also...I havent done a radio update because I am still under warranty but I would like to know if it could be causing the problem or if it is a hardware problem).
Thanks for reading this long post (didnt think it would turn out so long, lol), but ANY help or advice will be appreciated.

well it sounds like a bad signal, so unless you want to unlock yor phone and try the modded sedna radio (best) id just send it back and complain loudly