Related
Like the title says... woke up to the HTC boot screen and it wont boot past it. I bought it on Nov. 18th so it has been 34 days and ATT will not replace it in store because it is 4 days past the return date. Warranty will cover it, but this is frustrating right before the holidays. BAck to the old Tilt2 I guess.
Watch out and always sync your pics and such to your zune software!
Woke up this morning, once again with a dead Surround. This was my replacement device that warranty covered from December. Another one is on the way from ATT, but I was wondering if there is some lemon law where I can get my money back or something? If my phone is going to keep dying every few months I don't want it.
kdj67f said:
Woke up this morning, once again with a dead Surround. This was my replacement device that warranty covered from December. Another one is on the way from ATT, but I was wondering if there is some lemon law where I can get my money back or something? If my phone is going to keep dying every few months I don't want it.
Click to expand...
Click to collapse
in texas theres a lemon law but i dont know if you have one
The rep on the warranty line said after 2 or more FRU's they will negotiate a replacement device. Which is fine, as I may be negotiating for a different phone if this one dies.
Was it plugged in when it died?
Sent from my Desire HD using XDA App
The first one died unplugged, moments after I woke up and shut my alarm off and unplugged it. The second one was plugged in and the bright white screen woke me up in the middle of the night. Both of them acted funny before they self-bricked, like forgetting my IE favorites and deleting some apps randomly.
I had this same problem. Replaced under warranty and so far I haven't had that same issue. I did have a different issue though, where it didn't read the whole memory properly as referenced in this thread:
http://forum.xda-developers.com/showthread.php?t=916865
I'm worried this device is prone to failures, as I've now had two devices acting up. I'm trying to get AT&T to give me a different device, but they said I can only do same device exchanges under warranty.
vel0city1 said:
I had this same problem. Replaced under warranty and so far I haven't had that same issue. I did have a different issue though, where it didn't read the whole memory properly as referenced in this thread:
http://forum.xda-developers.com/showthread.php?t=916865
I'm worried this device is prone to failures, as I've now had two devices acting up. I'm trying to get AT&T to give me a different device, but they said I can only do same device exchanges under warranty.
Click to expand...
Click to collapse
They do in fact have a policy for device replacement for multiple FRU's. Meaning, if you are like me, and have already replaced two under warranty (meaning you are using your third device) if you have problems with the third they can negotiate an alternative device if it is still under warranty. Call the warranty exchange number over and over until you get someone who is knowledgeable and is willing to work with you. And keep calling with every complaint so they have it on file!
Good to know. I guess I'll just go and exchange it now and hope the next one either lasts forever or calls it quits ASAP. Warranty is running short these days :\
The warranty is one year from original purchase date or 90 days from activating the replacement device, whichever is longer.
My Surround also wouldnt boot up. happened last week. It was on my desk and not in use. I watched as it said goodbye and shut off. Battery drained and turned off, no big deal as I tend to let that happen before plugging it in for the night.. Only this time it wouldnt get past the white HTC screen. I did the whole volume button reset thing and still nothing. Ended up talking with HTC and getting it shipped to Texas to get it looked at. next day it was in the mail back home. Should be here in the next day or so.
Im curious to see if the paperwork will let me in on what happened. Although I sort of doubt it.
Awesome! I was under the impression it was just 90 days.
Talking about HTC Surround acting funny?
Well, mine likes too.
1. I used my phone as a alarm clock. Every night I connect it to the wall charger and leave it turned on resting on the night table. The next day guess what, I woke up late. The phone never sounded the alarm, in fact it won't make any sound at all. Have to reset it to return it to normal.
2. There have been a couple of times where I have not received calls in hours. When I press the power button to check the status, the phones goes throughout the complete power up sequence. But the phone was already powered on the last time I checked a couple hours ago and the battery is full. Its like it powered off by itself at anytime without warning!
3. Try to use the phone while charging and you'll notice touch screen response gets a a little jittery. But I found a "cure" for that. Hold your phone in away that your fingers make physical contact with the metal frame around the display. This will minimize the jittering effect on the touch screen.
4. Camera autofocus needs prescription lens. My HTC Surround digital camera have a hard time trying to focus on objects more than 15 feet away. It gives focus confirmation but the pictures always look blurry.
Those are some of the bugs I found in my HTC Surround purchased from AT&T last November. I'm sure they are not the only ones!
Those are known bugs, but seemingly have no correlation between devices randomly dying or not. My first surround had all those bugs and died, my second one showed little signs of any of those bugs and died anyways. Hoping my third one dies within warranty so I can get a new phone :/
This has happened once before, but just for a small amount of time to to the heat (I believe). The phone has been off for over and hour and refuses to turn on whether I hold down the volume button, don't hold down the volume button, or push the battery in at the exact time as I'm doing the other one or two. The splash screen flashed for half a second and immediately went back off when I plugged my evo charger, the usb part, into my portable ipod charger, so I believe this means there is still help available! Last time this happened, which was months ago, it seemed as if it just needed to cool down a bit, and my reading on the internet confirmed that the phones shut off when their batteries reach too high of temperatures. So what I did was wrap the phone and the battery, separately, in a large wash cloth and let them sit it the fridge for a little while. No luck, I'm running out of ideas (and I realize a ziplock bag may have been better but who cares). A few days ago I installed cm7gginggerbread7 (wimax) over cm7gingerbread2, but have not had any issues up until now and everything has run perfectly as well as smoothly. Is there any way I can turn my brick into a phone? Perhaps there's a way to adb something even though the phone wont boot (im a noob). I'm just pissed cuz I finally got every little thing exactly the way I wanted it, and now I'm stuck with a paperweight :/ I thank you for all your help, brave knights
It just suddenly shut off and won't turn back on?
And you weren't messing with anything?
If so, sounds like it's a hardware or battery issue.
Can you try a different battery?
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
sitlet said:
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
Click to expand...
Click to collapse
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
matt2053 said:
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
Click to expand...
Click to collapse
If they can't get it to power on then it really doesn't matter if it's rooted or not because they won't be able to find out.
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Raillery said:
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Click to expand...
Click to collapse
If this occurred while you were NOT changing anything with the radio partition or recovery partition then it's not a brick issue.
Sounds like you have a hardware issue.
Take it to the store.
If you smash it you will be paying $100 to asurion for a replacement as Sprint changed the TEP again.
Just wondering was your battery completely dead before this happened. I have read some people here and other places have said that if the battery completely dies that it won't charge unless you put it on a actual battery charger made for it. Does the charge light come on when you plug it in? Also, like my friend before me said, take it to Sprint. Ask them if they have a battery you could try. If it doesn't work it will eliminate the battery being the issue. If it won't boot they will replace it. They won't be able to tell if it is rooted because it won't boot. If you were flashing a radio and didn't let it finish or the battery died during the process, you are bricked.
Does the charge light flash when plugged in?
Sent from my PC36100 using Tapatalk
The light doesnt change
clean off the battery contacts
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
vespix said:
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
Click to expand...
Click to collapse
Take the original battery to sprint. Tell them the story and get a replacement, ask for some free accessory since you've helped them isolate a reliability issue.
LOL
There are two known issues with the Evo to be aware of. The first is the charging bug. If the Evo shuts off due to low battery level there is the possibility that the charging circuit fails to recognize the dead battery as even being there and will not charge. The workaround is to charge the dead battery in another compatible phone or use an external battery charger. This is supposed to be fixed in the next update but we'll see.
The second is the thermal sensor bug. The thermal cut off starts to trigger at lower and lower temps til even freezing the phone won't work. I thought the local service center was joking til I actually saw it reproduced. This is a hardware issue and the only fix is a replacement phone.
The first issue is intermittent but knowledgeable service centers are aware of this and will either charge the dead battery or swap out with a charged one.
The second issue is reproducible but can take some time to do so depending on how far off the sensor is. Again, knowledgeable service centers are aware of this and will want to reproduce it before ordering a replacement.
Not sure what technical thong is happening, but I do know I panicked when it happened to me, bit it turns out if you try to charge EVO from a USB port while its in the recovery mode it will eventually drain and **** off. I forgot I was on recovery mode and came back to what you described. After doing the swap with my GF's EVO and realizing my battery was fine, I remembered how I had left the phone in the first place and Googled it to confirm that will cause the dead EVO scare.
Sent from a corrective lens wearing eskimo translating Turkish smoke signals viewed over a streaming webcam at 640x480 resolution via a U.S. Robotics 14.4 Hayes compatible modem.
This has happened to me twice, but since I was on the extended battery from sprint, I would just pop my stock battery in and it powered up fine. Each time I just brought my battery in to sprint and they replaced it. Also, when it happened to me the charging light wasn't turning on or anything.
Sent from my PC36100 using XDA Premium App
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
cjh6386 said:
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
Click to expand...
Click to collapse
Blinking charge light means that the battery v has dropped below the required v to turn on the phone. I see 4-5 Evo's a day like this as well as the charge bug.
I actually got it booting again somehow. Now, it consistently turns on, will boot to the bootloader, but recovery doesnt work and it wont boot into the phone. It does search for pc36 image though... i might try that.
I just sit here and shake my head on a daily basis when I see people talk about problems and inevitably, and I'm not saying this is applicable in this case, but they say in their post they were using ROM or Kernel Manager.....
Had my Nexus 4 for some time now and the issues started once Android 5.x.x was released but has increased more recently.
I ended up trying around eight different ROMs posted on here hoping it might be OS level but it still does it.
Currently using this MIUI build whilst sacrificing the ability to use certain apps like banking.
It's getting to the point where it decides to power down and might not even turn back on till the next day. Which is exactly what happened yesterday.
When I attempt to power it on it gets as far going through all the boot animations; then I'll hear some sort of notification sound and it just powers down. This is the case for all ROMs.
As far as the battery being messed it was replaced with a new one a few months ago with me thinking it may be a solution for it. It's never been dropped or damaged so I don't suspect any internal damage. There's also no overheating ever if it helps. Just wanted to gather some opinions/advice on it before I pull the plug on the device and buy something else.
I am not sure if my situation is similar to yours but I'll share it anyway.
My battery was also a newly replaced recently but with an OEM battery, not the original from LG.
So it turns out that so-called 'new' battery depleted rather quickly and the power off randomly happens to me as well.
Until one morning, I realize the back cover was having this huge hump like its about to break apart.
Then I took apart the back cover and to my surprise, the battery was bulking inside (sign of a faulty battery)
Although it still can hold the charge, but it was making my phone looked like it was about to explode.
So my mistake at the time was thinking that the battery is fine when its actually not.
Because it was from OEM, so there is a chance or possibility that battery might go bad beyond our expectation.
Thanks for the reply!
Yeah I did replace it with a non LG battery but that was out of non being in stock at the time.
What I have now is a Kamal Star replacement from Amazon
The bulking you mention I don't seem to have with this current battery but when I was replacing the previous one I did notice it was bubbling if that's the best way for describing it; just a few small bump/bubbles over it randomly spaced. I really hope it wasn't somehow the cause the of the current fault.
First of all, hello to all Note 4 owners and my deepest sympathies to those affected by this "bug" (whatever it actually is).
I got used Note 4 in March 2016. It was trade in for my Sony Xperia and guy told me he had it for around a year. I liked this nice device. It had great display and served me very well. Excellent, even better term.
It was until December 2016 when dreaded bug appeared, and I knew nothing about it at the time. You already know it - lags, restarts, freezes, unable to turn on, going to download mode, harder and harder to start up...
How it happened is what amazes me most. I have 2 batteries, both original. I exchange them sometimes when I am on longer time without charger. This night (before it all happened) I let phone charge down to 0% because it showed false % in battery bar. It would die at 15% and not charge over 92% for example. This was factory battery and not my spare one I got later. I found out battery % is reset each time I let it charge down all the way, then after it shuts down I charge it up and it fixes the percentage bar temporarily. Anyway, as I was saying, that night (day before I experienced the bug) I wasn't in a good mood and phone died on me sometimes in the early night. I was annoyed and I started up the phone, it got to homescreen then shut off because it was empty. I did it again. This time it got to boot animation. Again. Again. How foolish of me. I did it until phone couldn't be turned on at all. Then I set it up to charge and left it overnight. Tomorrow I took it and left to work. It was peak 100%.
Around 10AM I got some messages on facebook messenger, and I wanted to check them out and reply, I took a break from working. In middle of my typing, phone simply froze. Froze, it wouldn't react to physical buttons, virtual keyboard, nothing. Screen was on non stop with frozen facebook messenger, virtual keyboard on screen and my unfinished message.
I took out battery and turned it back on. Phone was never the same since then... First "light" freezes and after second or two it "let's go" and all messages I typed appear instantly in messenger. Sometimes I press power button to wake device it wouldn't right away. It was getting harder and harder... after investigation I learned about this production "flaw" from samsung, I've read many pages about this error, many of those here on XDA (by the way community here is wonderful)...
I bought another device because Note was getting in state of unusable. I left it alone on table and it stand there for some time.
I couldn't give up it's wonderful screen, power, pretty TouchWiz... and after I've read a lot about this, I decided to buy new motherboard. I got one from ebay in late August and it arrived sometimes in middle September. 60 US dollars. I asked seller will all functions work, is IMEI blacklisted, is WI FI working, does it has good memory chip (which is culprit for bug it seems) and seller kept saying to me everything works, is tested one by one before shipping, and he said "it must work, 1 year warranty!" I smiled a bit, it's how he said it.
I ordered also some tools for disassembling phone as I wanted to do it myself. Very cheap, 7$ and there is everything there, really nice kit. It got to me before motherboard. Then it arrived. Same night I wanted to do it, I couldn't wait to use my note again. I missed it.
One friend at work which owns mobile store and repair, told me to wait until tomorrow, he will do it for cheap but I was not patient enough. I thought I can do it. After couple of youtube videos I started it... Bottom line is I didn't heat up the device to loosen the glue and I ended up breaking the screen... And couldn't attach screen to motherboard, because Samsung made it hard without removing the screen too. I went to my friend and he scolded me for not waiting few hours and eventually found me used screen for 75$ more... They are 150$ around but he took it from some friend of his own to help me because he felt sorry and he got that friend's phone, got out the screen and transplanted it to my motherboard and casing over for free. I have working Note again...
Now, I don't know what to do with it? Do I sell it? Use it? I felt free to attach some screenshots from it, to add up to collective knowledge of XDA (it was my intention with this story in the first place). Who knows... maybe some info from here might help someone, sometimes.
Phone info showed my phone (motherboard) is made in 01.2016. Brickbug check app can't identify the memory chip (shows production date as 11/1999 which is not possible for note 4). It is fast now, one screenshot proves it. Friend said he stress tested the board (whatever it means) and it seems fine. All functions work, I tested everything too. Board color looks different - shade of green is different. KNOX warranty void status 0x0.
What is opinion of fellow XDA's about this? Do I use this thing, sell it... it cost me more than it's worth, and selling it will be just extracting mere costs I invested. But I like the device... I feel like just going through with it, whatever happens this time... maybe my pain with emmc fail is over.
Maybe some other members reading this, can screenshot their brickbug check app statuses? Those which have "healthy" devices and those having emmc issues too? Maybe we can build database of good chips, and which devices may be "safe"... I will sure add my results here in attachments.
I wish everyone owning this good little device much luck and as less problems as possible...
PS Mods can move thread to some other one regarding this issue but I'd like it stays thread of it's own... but I will conform to decision of Mod team. This is wonderful and helping site, thanks goes to owners which built it and mod team keeping the order, as well as userbase for contributing to collective knowledge and "hacking" the android and devices in a good way.
StreetKing
Two and a half years and still no issues. I'll gladly contribute to your database since I seem to have one of the "good" chips.
Had a bootloop today on my phone lgg6 Australian version. It was charging and over heated then would go to the LG logo and keep rebooting then it went to a yellowish screen with a whole heap of code about the battery. I pulled the phone appart to see if I could find anything wrong. And to my astonishment the heatsink paste was dried up and powdered. Cleaned it up replaced the thermal paste put it back together and works great. Also noticed doesn't get as got especially when charging. Hopefully this doesn't happen to anyone else. I noticed also in the last two weeks it's been sluggish and dozer a few times also rebooted once.
Any proof?Any pictures/videos about that?I just can't believe in this-
"heatsink paste was dried up and powdered,Cleaned it up replaced the thermal paste put it back together and works great".Looks like a bull**** for me,honestly.
Um your a moron why would I say it do ****
This is what happened
Then it bootlooped. Seriously I was trying to be helpful. Some people.
I'm not saying you're a troll,i just wanted to see a proof of that,ok?And that means i am a moron?
We'll learn to try not to be insulting.
And I didn't get any pictures of the heat sink paste but it was a pink powdery substance that wiped off when I touched it. Haven't had a good run with phones lately my Nexus 6p bootlooped and can't be repaired and now my lgg6 did and could be which I thought was pretty awesome. Considering the last LG phone I owned was a lgg2 which was pretty easy to work on also. I won't be buying another Huawei phone ever again that's for sure. I have owned every Nexus since the first one and they have all been great for what they are. I wouldn't mind buying a LG v30 as I didn't realise I couldn't unlock the bootloader when I bought this.
Hi
Just to say that same issue just happened couple of minutes ago... I didn't know G6 could run this bootloop problem. I had this issue with my old G4, now the G6...
I think I'll say ciao to LG even if I really like their product!
The phone is almost a year old now. Have you ever heard of a bootloop case? I'm pretty sure if there were problems like G3/G4 had, we'd knew already. Fortunately, the g6 is a sturdy device, both software and hardware, and it takes a lot of heavy usage every day. Not to mention flashing and testing custom roms almost daily,
This happened to my phone out of the blue last night. Kept on alternating between black screen and the lg logo. Did the reset, power button and volume down but that just gave me the same yellow screen. Charged in I could get the looping, unplugged with would just go black then back to yellow if I tried to reset or selected reboot. Then it just went dead despite having approx 50% battery. Unfortunately I bought it from eglobal about 10 months ago so I'm not holding out much hope for a successful warranty claim.
Thanks for the info above, there seems to be very little about this issue out there so at least I hae something to try.