Database Users

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 Coma like state

Right guys and girls, this "coma" stuff is driving me MAD!!!!!!!!!
okie the latest example is last night i put the XDA on charge not in the cradle as usual as i was not at home, but that seems to make no difference, anyhow i turn the screen off by pushing the power button (top left) yellow light turns on and begins to charge, next morning i pick up the device to use it and nothing.....not a sausage, dead as a doe-doe.
Im not able to power it on, im not able to "wake it up" with a call to it, buttons do not work at all, screen is dead, the yellow light stays on even when charger not connected, however it turns of several hours later.
Ok at this point in the past the only way to fix this was to hard-reset it, which is a royal pain in the arse as you all know, and lost all my info i worked on, on that last trip.
Except this time, it really is dead, Hard-reset dont work, removing the main battery and letter the internal one take the hit dont work, verious combos of reset, hard-reset, with and without battery. nothing
nope, this time it seems totally screwed, anyone have any ideas
O2 is going to get an angery phone call, as soon as there tech support peeps goes back to work after the weekend, they said originally it was just a glitch and i was to update my software (rom). Some damn glitch!
Anyhow in a bid to remain slightly more sain than i will be i was hoping that some of you guys have had a problem like this or even better know how to fix it
How you can help
Regards
Darren

O2 is going to get an angery phone call, as soon as there tech support peeps goes back to work after the weekend, they said originally it was just a glitch and i was to update my software (rom). Some damn glitch!
Click to expand...
Click to collapse
well maybe your phone is just broken
being angry at o2 will not help anything they dont make the hardware they dont make the software they just sell the device

Hum, intresting, before i start, O2 is to blame, in the world of retail and more importantly sales contracts, they are my first and direct point of call, in law, when i give them cash and they except it, they are entering in a contract which sticks them in the position to be blamed, however it is not about blame, its about getting somthing done about it, and they are the people who pull the stings, i do understand that they do not make these devices but thats not the point.
16 year old kids may be a bit put out when there phone stops working, however those who need there phone / PDA to work have more issues when things go wrong.
Whats more intresting is that 1 hour ago, the phone unexpectedly turned on by its self, although not surprisingly, all the data was lost. It seems to of woke its self up when the last remaints of power in the internal battery was about to die, to tell me this information.
Whilest i cant conferm this, if the others who have had this problem before
were to leave the phone off the charger for the battery to die, without trying the usual hard reset, i would expect it to wake up to tell you its about to die and then at this point plug the charger back in and hay presto!

well i'm not saying that you cant sue or demand your money back or place the blame on o2 i'm just saying that you cant expect then to solve your problem apart from reporting the issue to thc who again can blame it on microsoft

dazza8082,
What ROM version do you have on your machine?
I had the same problem with my MDA2 which came with ROM version 1.60 or something like that, but I managed to upgrade my MDA2 to 1.72WWE that I found somewhere in this forums and the problem was solved ever since. I even had lots of sudden SD memory wipes, so far so good... It's been like 4 or 5 months since the upgrade and counting...
The upgrade procedure was performed via the cradle and not via the SD card. But if for some reason you can't manage to boot your device you can always try the SD upgrade method.
I really don't remember the procedure but you can find lots of information somewhere in this forums.
Have you tried to get into Boot mode and then reset the device just to see what happens?
Press the Power button, the reset button and the joypad down at the same time and you should see a DOS-like screen indicating you are in boot mode, from there just press the reset button by itself and see if that helps. You will loose all your data with this procedure, but at this point chances are that you already lost everything in the device anyways.
Best of luck!

Suspend/Wakeup issues.

After receiving my o2 XDA Exec in the mail a few days ago I've had to soft-reset to get my device to unsuspend several times, what's odd is the lights are still blinking on the unit, but the keyboard backlight/screen will not turn back on.
A few times watching media it's gotten stuck to a green/white/once blue screen, too.
The battery is of course charged, it seems to be just these two issues.
I'm looking forward to worry-free enjoyment of my Uni once I get these issues solved, any advice is much appreciated.
I'm thinking this may be a WM6 issue, or a ROM issue, Hopefully someone has had this same problem.
(I have and am still searching the forum to check this out.)

Maybe consider a hard reset?
Mine's running WM5 and doesn't have this problem - it will sometimes decide to change it's backlight settings to zero when switching from battery to power or vice versa though.

Ironically enough, I woke up this morning, turned the phone on and it had hard reset itself, I'm going to assume its a software issue for now, if I can't find a way to fix it, I'll just have to buy another unit and get rid of this one.
Love the phone, not this particular unit though.

similar problem here?
a week ago I installed PsiDocs .cab for SDHC and i am running a 16gb card and have noticed that sometimes I have to soft reset to wake it up, also test driving pocketweather on the card so i think that this might be my problem.

Radio firmware faling off after reboot on BA

got my BA flashed with WM6.0(russian firmware)...VERY stable version...but!
if i pull off battery on_the_fly, or got battery discharged then on next boot i got first two lines "R: none G: none"
the only help is reset-button. after that it boots ok with (R: 1.15....etc)
how to get rid of that minor bug?

there is no way of getting rid of that bug, it is like the 4 colour screen. it comes with every rom here, so for soft-resetting use the proper soft-reset istead of pulling the battery off. since there is no proper airplane mode in most of these roms and the phone keeps re-enabling itself, you can use that "feature" to have the ppc working without phone functuality

hm...no good(
that means that everybody got this stuff(WM6.0) not working _properly_?

well, actually it is working properly, i used to wonder about that too, but there's no point in complaining. it is just a given fact and you have to learn to live with it. little things like that are, despite the fact that the BA is huge and doesn't have much battery power, reasons, why people go off and buy new devices. also there are minor bugs in wlan and bluetooth that come with every rom here. that's the way it is, and that's the price you have to pay for upgrading your phone instead of buying a new one and i for one think, that's a rather low price
to get back to the point: as i use sun_dream's finger-friendly build 20758 and have lost my stylus about a year ago, for soft-resetting i also don't use the stylus hole, but use the today screen icon that comes with xcpuscalar, which of course wouldn't work, when the device freezes, but then i simply take out the battery, start over, and when the device is ready i soft-reset from the icon. it is not the ideal way, as by that you somehow delete your wlan settings as well, but still i'm happy, my precious old BA still is up to date

soft reset
every rom after WM5 in BLUE ANGEL needs soft reset after u see this case,then works normally.thnx.

most times, u will need to do a soft-reset at the 1st cold boot (replace battery and so on). as Chef_Tony mentioned, we all just have to remeber do that.

Big problems with Touch HD

I have a UK supplied Touch HD from Orange and it`s going crazy!
Problem 1:
Backlight switches off without warning, touchscreen still responds but obviously you can`t see anything! Multiple hard resets will eventually coax the backlight to wake up, but the delay between power button pressed and the "first buzz" of life is around 20-30 seconds. Started happening when it was about 2 months old. Initially it was infrequent and I put it down to an installed software problem, but now every few hours. Other symptoms include the charging light failing when the backlight fails and there is usually an increase in heat around the case. Strangely however when I use it as a sat-nav and it is permanently charging the backlight never fails. I have tried a new battery, desktop charger, turned off fast-sleep, autolock, light sensor, full reset and removal of all my software and it still does it. Sometimes its OK for 5 days, other times it goes "dark" after 10 minutes.
All ROMs updated to latest versions. NB This started happening with the original Orange installed ROMS
My original solution to the problem was to run bootloader which forced the backlight on, but the long delay between on/off and start means this doesn`t work anymore.
Problem 2:
Screen display appears inverted and mirrored after pressing power button during operation. This is an infrequent problem but may be connected.
I live in Thailand now. HTC Thailand will no doubt take it and charge me $250 for a new motherboard whether it needs one or not. I can`t easily return it to the UK and I just hope somebody somewhere has some ideas?!?

I was just talking to another user with completely bizarre issues. What you are experiencing is totally abnormal. Just to make sure it's not a software issue- what SPL version shows up in your bootloader? Also, what rom are you currently running?

Please read next post

Please read next post

** OOPS my typing brain isn`t working today **
Thanks for replying. I had upgraded to:
2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship
with soft uspl but last night I reinstalled the original Orange ROM, effectively factory fresh. (The HTC April update won`t install natively on the Orange variant of the phone) and the thing stayed on all night and didn`t go dark. However, this morning when I got the reply, I turned off the phone to get to bootloader and it took 3 battery removals to activate the backlight.
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
Any suggestions would be gratefully received.

jamesmclean said:
** OOPS my typing brain isn`t working today **
Thanks for replying. I had upgraded to:
2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship
with soft uspl but last night I reinstalled the original Orange ROM, effectively factory fresh. (The HTC April update won`t install natively on the Orange variant of the phone) and the thing stayed on all night and didn`t go dark. However, this morning when I got the reply, I turned off the phone to get to bootloader and it took 3 battery removals to activate the backlight.
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
Any suggestions would be gratefully received.
Click to expand...
Click to collapse
So is the phone working properly again with the factory Orange rom? All I can tell you is that if you want to run the 2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship rom you must have a base SPL of 1.54.0000. Even if you use USPL to flash the rom to bypass CID-locking you still need to upgrade your SPL because the new 1.56+ roms are not compatible with an SPL version less than 1.54.0000. Read the guide in my signature for more information.

I see cRaCKwHoRe is on your case, so your in safe hands. I'll leave it to him.
One suggestion though. Instead of creating new posts and saying 'Read Next Post', why not just edit your first post and state 'EDIT' or 'Update' with new information below. This way thread remains short and easy to follow
Just an idea mate!!

Hello again. As I said in the previous post, reset to check the ROM version caused it to happen again. 3 Attempts to wake it up this morning. This afternoon another spontaneous backlight failure. I started to wonder if it could be connected to something on the flash card. So I took that out and it has behaved since then. But this doesn`t mean problem solved as it had worked ok for the 5 previous days with the WWE 1.56 ROMS.
Also, HARDSPL is being identified as a Trojan "heur" with Bitdefender.

jamesmclean said:
Hello again. As I said in the previous post, reset to check the ROM version caused it to happen again. 3 Attempts to wake it up this morning. This afternoon another spontaneous backlight failure. I started to wonder if it could be connected to something on the flash card. So I took that out and it has behaved since then. But this doesn`t mean problem solved as it had worked ok for the 5 previous days with the WWE 1.56 ROMS.
Also, HARDSPL is being identified as a Trojan "heur" with Bitdefender.
Click to expand...
Click to collapse
Most virus scanners show a false positive that USPL and HSPL are trojans or viruses. This is based on heuristics and how these utilities work. They are tried and tested and are most definitely safe.
And again I stress that you cannot run a 1.56+ rom on an SPL version below 1.54.0000. Since you are running SPL 1.14.0000 this is why you are having such issues. You need to flash a newer SPL version!

After the hardspl back to original Orange ROMS:
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
I had 2 dark events. I wondered if there could be a problem with the memory card, so I took it out. My reasoning being, after it goes dark and is reset, something was causing it to wait 30 seconds before "smart mobility" and/or buzz (if the screens still alive). When my PC does that its usually because there`s a memory card or external hard drive confusing it. Took out the card and it was OK all night. Formatted the card this morning and had no problems all day.This is a guess, I am an idiot! But the memory card is the only ongoing part of my phone; internal storage and ROMs has been cleared or upgraded every month.I dont doubt my feeble attempts to upgrade to 1.56 and bypass HTC`s no upgrades for Orange handsets policy may have been a significant contributory factor. Interestingly, Orange are actively discouraging purchase of the HD, they have had too many problems with their handsets.
Going to keep the phone empty for a few days, no software, no sat-nav and see if I have any more events. Then I think will read your HARDSPL instructions far more carefully and retry the ROM upgrade. Excellent work by the way!
The odd thing about this telephone (apart from the inversion and mirrored display problem, which still occurs) is that following the nuclear option of total clearance and ROM upgrade/downgrade it will behave for an number of days and then the backlight dies again. It could still be hardware!
Going to keep my eye on things for a few days.
But if anyone else has had these problems with their HD or Orange handset, please tell! Maybe you aren`t crazy! To help this is a list of symptoms:
Spontaneous backlight failure but screen and phone responding
Simultaneous charging light failure
Delayed reboot 20-30 seconds before first buzz
Continued backlight failure requiring multiple hard resets to resolve
Weak vibration during failed backlight reboot
Inverted and mirrored screen at boot or after wake-up
Thanks!

Looks like a SPL problem only. It is responsible for the boot events and mismatched display drivers between SPL and the ROM most likely did it. Anyway interested in knowing updates once U flash a new SPL 1.54. and ROM..

Problems not resolved. Backlight dead again today. Multiple failures 10 minute interval. Totally fed up with HTC products. My previous HTC phone MDA Vario 2/Tytn/Hermes had to be replaced 4 times under warranty and until 2 weeks ago I used it when Touch HD died, now it has completely died as well.
Even in its "as-supplied" by Orange configuration the Touch HD won`t work now. May be I will try one more attempt at ROM upgrade. In the meantime I`ve just bought a cheapo Samsung sgh i200 for basic pocket PC functionality and just because it doesn`t say HTC on it!
Windows mobile is great. Massive software library and great to customize. But in my experience HTC make lousy unreliable products!

jamesmclean said:
Problems not resolved. Backlight dead again today. Multiple failures 10 minute interval. Totally fed up with HTC products. My previous HTC phone MDA Vario 2/Tytn/Hermes had to be replaced 4 times under warranty and until 2 weeks ago I used it when Touch HD died, now it has completely died as well.
Even in its "as-supplied" by Orange configuration the Touch HD won`t work now. May be I will try one more attempt at ROM upgrade. In the meantime I`ve just bought a cheapo Samsung sgh i200 for basic pocket PC functionality and just because it doesn`t say HTC on it!
Windows mobile is great. Massive software library and great to customize. But in my experience HTC make lousy unreliable products!
Click to expand...
Click to collapse
That's really unfortunate. Seems you have bad luck, consistently
Most people really like HTC devices. They do actually make some pretty decent stuff. Seems you've just gotten rotten luck.

Taken it back up to 1.56 with Hardspl as suggested. Installed Dutty 3.4. And it worked... For one night! Dead again today. I think now it is a hardware fault. So I suppose she`s off back to HTC and I will have to pay some money.
I have been very unlucky with HTC products. I said before I had to have 4 HTC Hermes, thought it would be interesting to tell what was wrong with them:
1. Orange SPV3100 WM5. First generation Hermes 100, hopeless wifi, buggy, returned to store and refund.
2. MDA Vario 2. WM5 Upgraded radio version, better wifi. Decided it didn`t like being a telephone anymore and the radio died after 3 months. Returned to store.
3. MDA Vario 2. WM5 Factory replacement. Dead memory card reader, didn`t make it out of the store when I went to collect.
4. MDA Vario 2 WM6 (Hermes 300). Working wifi, a much better operating system. A real telephone. Lasted 18 months! 2 weeks ago, complete power failure for no specific reason. Won`t charge or do anything now.
But before Nokia and iPhone customers get too smug. I also had an iphone when they were first released in 2007 (1.02) and that was a bug infested piece of junk as well. Got stolen in Bangkok. I really do miss having to reinstall the OS every 2 weeks! And my brother`s Nokia N95 has spent more time with Nokia than with him. 8 visits to Nokia care.
And now I have a broken Touch HD, probably with a power supply issue!
All these phones have one thing in common. They were (with the exception of the Hermes 300) first generation examples. And just before you rush out and pay big bucks for the latest telephone from HTC or whoever... Think, was this phone ready for release? Or was it just rushed out to keep the shareholders happy?
Think about it...

Hell! finally I found someone with the same problems. But I have bought it just some days ago!! The only thing I have done since then: installing tomtom on my sd-card and setting this gps-signal thing to the value 3000.
when I bought it i tried to run it in the store: after turning on, black screen but still vibration when i pressed some button, so it must have been on. Then it suddenly worked, installed the system, everything perfect. yesterday i installed tomtom, today it probably "died" around 20 times. everything the same like already described, screen messed up, after turning on vibration after 30 seconds, god!
is there anything i can do? i just bought that thing

Spontaneous backlight failure but screen and phone responding
Simultaneous charging light failure
Delayed reboot 20-30 seconds before first buzz
Continued backlight failure requiring multiple hard resets to resolve
Weak vibration during failed backlight reboot
Inverted and mirrored screen at boot or after wake-up
Click to expand...
Click to collapse
Sounds like you have the exact same problem as my HD: inverted screen, screen blank but still functioning etc...
http://forum.xda-developers.com/showthread.php?t=520781
I am waiting for mine to happen more frequently before sending it away for service. Otherwise they will just return it if they can't reproduce the problem.
Pretty sure it is a hardware problem. I am in Australia and have the original stock ROM.

We may be onto a new fault here. Just noticed 2 more threads with the same screen issues. My phone has been OK for a few days, but today screen won`t wake up at all. Hooked it up to Pocket Controller Pro and it`s reporting a "microp version mismatch 0" in its dark state. Been checking on other websites and this seems to have been a problem with Touch Diamond previously. There doesn`t seem to be an update for microp firmware. One user tracked it down to a loose connection between screen and motherboard. I don`t know! I just wish it would work!
Any suggestions for MICROP issue?
Currently running Dutty 3.4 with 1.56 Olinex. But this has been a problem long before this ROM version.

Fallen Spartan told me this:
"Have you tried going to Start > Settings > All Settings > System > Power > Advanced and making sure device isn't set to turn off after a period of time?"
Until now my phone works without problems, I will report again after some days

Yup, tried that one. Doesn`t work. You will notice after you end a call, the screen will be dim. This is the warning of imminent backlight failure. It is not power management dependent. My problems with the phone started in Feb. Initially intermittent. Now constantly.
Sometimes the thing will work for a few days for no reason. Only way to guarantee no failure is permanent USB power. Pull out the USB and watch it die, instantly! That`s with the original or the new battery.
New motherboard may be the only solution. But it is worth noting that when I had problems with my Hermes and it had to go back to HTC 3 times, each time a new phone was sent. On the service report "New motherboard" was reported. The guy in the T-mobile shop told me they`re too expensive to repair so it`s easier giving you a new one. They still hold onto the old one for 3 weeks though!
Might try to repair the Touch HD, I still have my Samsung SGH. (It`s very slow!) but I think I will wait for ASUS or Toshiba phones with snapdragon processors. Had enough of HTC and don`t want another iphone.

This is a hardware issue. No if's, and's or but's. It is caused by a disconnection between the screen and the motherboard. A faulty motherboard or a loose / broken connector is the usual culprit. I would say 7 out of 10 times it is due to a loose connector. It is a poor design to begin with and after being dropped or roughed up enough it tends to break or get loose. HTC typically just replaces the motherboard in a warranty repair situation.
If you are lucky and just have a loose connector and are comfortable with opening up the device yourself, you can disassemble the device and re-connect or re-solder the 2 port connector that connects the motherboard with the screen. Of course this will "void" your warranty so I wouldn't recommend doing this unless you are comfortable working on micro-electronics. If your case is the type where it is intermittent and it works sometimes and then sometimes not, then you have a loose connection and it just needs to be reconnected or re-soldered.
I have seen and fixed a couple of these now.