Okay people, I just got my S3 last night, and after about 3hrs of use, my problems developed. My problem is intermittent, but nonetheless, very aggrivating. When I press the power or home button, screen wakes, but touch is unresponsive. I thought it might have been a lockscreen issue, but I've tried all variants including no lockscreen and have the same problem. Is there any updates or fixes that anyone knows of or do I have a defective phone? Any thoughts are welcomed. For what its worth, I also rooted my device, and it installed supersu. I don't know if that could be related, but I'm going to give a full unroot reset a try as well.
Sent from my aokp_tenderloin using xda premium
Are you connected to charger, that can cause pro lems when getting unstable current
Sent from my GT-I9300 using xda app-developers app
On or off the charger, makes no difference. I Fully factory restored, pulled root, triangle counter reset, and everything else in between, and the issue still remains. Even tried another rom and kernel, sames results. Seems like I have a fancy light up paperweight for the most part. First samsung phone in over 10 years, and this is what I end up with. Great job samsung.
For how long is there no response.anyway try disable s-voice in settings.that is directly related to home button.power button hmm, don't know..
So, factory reset the phone, reflashed stock rom, even booted phone up with no sim or memory card, fresh from a reset. On the main setup screen, if I lock the phone, then wake it up, touch is dead. Definitely a hardware problem. Called samsung uk because anyone who used DAILYSTEALS.COM will find out if their phone ever needs service, that the phones sold via them came from the UK. Not really happy this wasn't explained on their website prior to purchase, as I would have held off. Now my 3 day old phone with not even 24hrs of use on it is off to a UK service center.
Word to the wise when buying online, check the origin of your phone if the retailer isn't an official seller. now my money saved is going right back.
zodiaxe66 said:
For how long is there no response.anyway try disable s-voice in settings.that is directly related to home button.power button hmm, don't know..
Click to expand...
Click to collapse
As stupid as it may be, I want s-voice to work, shouldn't have to disable something to make the phone work properly out the box.
Related
Hey, I recently got this phone, and I must say its impressive. It runs so well and a great phone all-around. However lately when I go into department stores or even large buildings, the phone has no signal.
However when this occurs and the phone goes on standby, I noticed that you can't turn it back on without popping the battery in and out.
Is anybody else having this issue? I've been googling it and I can't find anything. Is this an android OS issue? A Hardware issue? or its just my phone doing it.
TLDR: No Signal kills phone? Is this common?
No issues here. If I lose signal it comes back on after im in range. Have you tried a factory reset since you had the phone. I did a factory reset when I got my phone and a lot of the issues were fixed.
This sounds like a weird problem. If its not related to an app or something and factory reset doesn't work, I think you should exchange it.
Sent from my SGH-T959 using XDA App
Actually I would think its a software issue not a phone defect. I have been experiencing the same issue. I'm on my 2nd one and the only way I can prevent it from blacking out like you say is to set it in flight mode. Kinda sucks when you're a cellphone salesman and you pull out your phone to try to sell one then the screen is just black and frozen.
I'd bet money it's all related to the GPS problem. With GPS enabled, and you go somewhere where it cannot get a signal (a weak as it is doing that anyway), GPS enabled apps, especially google maps but others as well, have locked my phone up.
My fix until the fix comes out is to leave GPS turned off except when I specifically want to use it.
I don't its a GPS issue the phone freezes even when the GPS is shut off. I'm willing to bet that the OP is having the same issue and his GPS is off as well.
@ op are you using setcpu app?
Sent from my GT-I9000 using XDA App
Farrenkip said:
TLDR: No Signal kills phone? Is this common?
Click to expand...
Click to collapse
Yes it is common fault throughout the Samsung Galaxy line of phones. Apparently pressing and holding the power button for ten seconds will force the phone to reboot, though I can't confirm this myself as it has never worked for me...
Some people have reported that a new SIM helps, others recommend the NoBars app. Personally I've tried both and neither have helped, leading me to think that this is a yet another hardware/software bug that can only be properly fixed by Samsung. It's perhaps also worth noting that I've had this happen to me 12+ times on two GT-I9000s running stock firmware with zero modifications.
I've entered a building where I work and have lost signal many times and ate lunch for nearly an hour. I just get the no signal image, but never blacked out.
It is true that holding the power/lock button for aprox 10 seconds will force a reboot.
Valeo said:
Yes it is common fault throughout the Samsung Galaxy line of phones. Apparently pressing and holding the power button for ten seconds will force the phone to reboot, though I can't confirm this myself as it has never worked for me...
Some people have reported that a new SIM helps, others recommend the NoBars app. Personally I've tried both and neither have helped, leading me to think that this is a yet another hardware/software bug that can only be properly fixed by Samsung. It's perhaps also worth noting that I've had this happen to me 12+ times on two GT-I9000s running stock firmware with zero modifications.
Click to expand...
Click to collapse
ive had the phone freeze a few times due to the gps **** and holding the power button has always rebooted the phone. you might have to hold it longer than 10 seconds depending on how hard the phone has locked up, but it eventually reboots.
Okay reformatting worked and fixed the signal issue. Musta went app happy and installed something that messed it up. Now that I reformatted i was a little more cafeful with what i Installed. However lately now my back and home keys has glitched and every time i push it, it either holds the menu key and goes to search or disables them for like 10 seconds
You must have install something the first time that is making your phone act up. Recommendation master reset your phone is like it come out of the box. That's what is master reset in case u don't know. If that's doesn't work get a new one. I am pretty sure they will change it cuz they did it for me.
Where do I master reset? I did Factory Data reset in the privacy settings. Is that it?
Okay doing a master reset. For those who need to know the combo. I did
Volume up + menu + power
So far this is a fix. Lets see how long it lasts.
Update: Going to take it back tomorrow. This must be a hardware failure.
That's not a master. You do it from the priv section with phone on. You will also have to call samsung if older then 15 days.
Sent from my SGH-T959 using XDA App
Maybe its the building? blocking the signal
Sent from my SGH-T959 using XDA App
I've locked the phone on 3G many of times, and when I go home I lose all 3G so the phone is in emergency mode.. sounds like you need to flash the new firmware.
Is my fascinate defective? Why does my back button randomly press itself? In fact, it seems like it's doing it as a long press sometimes since pressing the power button takes a random screen shot!
I've posted about this before, but this issue came from EB01. Surely others are experiencing such a thing!
This happened to me on stock DI01. I don't know why, but all of a sudden one day, it started doing those phantom presses. For me it was the back button and menu button. I also had a hard time long-pressing the home button to pull up the recent app list.
I have insurance through Verizon, so I just took it into the store, and they ordered a refurbished replacement for me. I didn't have to turn in my phone until the new one came.
It's a different story if you go directly to Samsung. Through them, you are without your phone for 6 days (2 days shipping there, 2 days repair, and 2 days shipping back), and no temporary phone is provided. I was only going to do that as a last resort, but Verizon actually came through.
The end result is that the new phone is definitely better, and I can tell there's a difference in the button response - not in a bad way, though. It's a more "solid" experience as opposed to the previous phone being more finicky.
I have this same issue as well, and have had it pop up on me well before EB01. It's not all the time, but it happens often enough that it's annoying as hell.
Anyone happen to know of a software based solution? Considering all of the rooting/etc. I've done to my phone, I don't know how feasible it is to get replacement hardware..
Skyh said:
I have this same issue as well, and have had it pop up on me well before EB01. It's not all the time, but it happens often enough that it's annoying as hell.
Anyone happen to know of a software based solution? Considering all of the rooting/etc. I've done to my phone, I don't know how feasible it is to get replacement hardware..
Click to expand...
Click to collapse
I believe that if you were to odin back to stock (or any official OTA update) that they wouldn't know you'd ever been rooted.
Superclean 2.4 Voodoo - VA Green
I have the same issue. In fact, it just happened a few minutes ago. Sometimes it only had one phantom press, other times it will go spastic. When the latter happens I have to press the back button to make it stop.
I'm glad I'm not the only with this issue. Looks like I'm calling for a replacement tomorrow.
Sent from my SCH-I500
Joshuaboyzn said:
I believe that if you were to odin back to stock (or any official OTA update) that they wouldn't know you'd ever been rooted.
Superclean 2.4 Voodoo - VA Green
Click to expand...
Click to collapse
That's what I did. I was rooted and removed a bunch of the VZW bloat when I first started seeing it. I ended up flashing an Odin package for stock/unrooted DI01 onto the phone to make sure that rooting didn't cause the problem. It still ended up happening on stock. I took it in to Verizon and had them look at it, and they were none the wiser. It's been a couple of months now, and I've heard nothing about my returned phone.
Both the DI01 and DL09 Odin packages should be available in the development forum. Be sure to disable voodoo (if you are using it) before you use Odin.
Domush said:
I have the same issue. In fact, it just happened a few minutes ago. Sometimes it only had one phantom press, other times it will go spastic. When the latter happens I have to press the back button to make it stop.
I'm glad I'm not the only with this issue. Looks like I'm calling for a replacement tomorrow.
Sent from my SCH-I500
Click to expand...
Click to collapse
I just hate the idea of getting a refurbished phone. I sure hope this is a software issue.
Doesnt verizon insurance go through asurion or something like that
Blue Super Froyo
Verizon should be quite familiar with this problem at this point. This problem ran wild on the OG Moto Droid. I've had family members return their phones and within the first year get replacements per warranty (factory defect).
The problem stems from either using a charger that doesn't have a USB module (aka doesn't require you to plug the USB data cable into a charger brick) or from improperly plugging in your phone (for instance, not putting the phone in a dock completely or having the USB connection slip partially). The unusual changes in voltage kill these smartphones and cause them to almost short-circuit, resulting in the "ghost" phenomenon. Many people have had this problem within the last couple of years and have found this to be the culprit. Just google "Ghost Droid" for more information.
WhiteRocks said:
Doesnt verizon insurance go through asurion or something like that
Blue Super Froyo
Click to expand...
Click to collapse
Verizon's insurance does go through Asurion. That's not what I did, however. I told Verizon I didn't want to make an Asurion claim (which comes with a $89 deductible). They said I could go through them for the Samsung warranty. They sent me the replacement and then I sent back my phone (like you do when you make an Asurion claim), but there was do deductible or charge for it.
Now, they might have only said this because I have the extra protection through them. I can't guarantee they will do this for everybody.
Zerg The Bear said:
Verizon's insurance does go through Asurion. That's not what I did, however. I told Verizon I didn't want to make an Asurion claim (which comes with a $89 deductible). They said I could go through them for the Samsung warranty. They sent me the replacement and then I sent back my phone (like you do when you make an Asurion claim), but there was do deductible or charge for it.
Now, they might have only said this because I have the extra protection through them. I can't guarantee they will do this for everybody.
Click to expand...
Click to collapse
Your phone comes with a 1 year warranty from Samsung for hardware issues. Assurion picks up if the user damages the phone, like dropping it or water damage.
Update for anyone following this thread..
I got a replacement phone and restored via nandroid, ensuring identical software. The phantom button presses are gone! So, it seems the button presses are indeed a hardware failure, not software related. If you have phantom button presses, get a replacement phone and save yourself some grief.
Cheers
Sent from my SCH-I500
Ugh, I'm getting them too. Really don't feel like getting a fourth refurbished fascinate.
Sent from my SCH-I500 using XDA App
Dammit. I assumed it was software since this only started happening when I switched to froyo. The kernel is buggy and I figured this would go away once the devs bring us ones from proper source.
I guess my days of not safely removing from PC are catching up to me.
Sent from my SCH-I500 using XDA App
The only thing I've noticed on my phone is my power/sleep button sometimes randomly takes screen shots instead of going to sleep, which I thought I read was the back key sticking, is this similar to what everyone is experiencing with these phantom button presses? Mine isn't backing out of programs or anything?
I've had these phantom button presses on mine on and off since I got the phone. Even before I rooted it. I always assumed it was because the soft keys were dirty/oily and were incorrectly registering touches. Wiping off my phone has always taken care of the problem.
My fascinate has infrequently done this over the last several months. Today, the stupid thing started pressing the back button every few seconds. Rebooted several times. No improvement. Switched kernels. No improvement.
I decided to try to see if this is software or hardware. Rebooted to CWR and left it setting on one of the options. Right now it has been setting for about 10+ min and no random back buttons have been pressed. My thinking is, if this is a hardware bug it should have selected the highlighted option since the back button is used as the select in CWR.
Anyone have any ideas?
I think I might try a clean reload starting from the stock ODIN when I get home.
Phone is rooted and running SC 2.9 Voodoo Kernel, voodoo disabled.
I have this issue really bad ever since upgrading to Gingerbread...
If I use Odin to flash back to the Stock Verizon 2.2 the issue disappears, but if I flash any gingerbread, doesn't matter if its VGB or one of the CM7 nightlies, the phone presses the back and menu button pretty consistently and also if you remove the battery for any reason at all, it loses or forgets a lot of apps that you may have installed (Live Wallpapers for instance) and also takes 3-5 reboots or power down cycles to finally boot up NOT in Safe Mode.
Not sure what the hell is going on, but I may have to just Odin back to Verizon stock 2.2, root it and live with the bloatware
Oh, and this issue is persistent from my original Fascinate to the refurbished replacement that Verizon just sent me. So either they sent me a refurbished phone that has the exact same symptoms or its an issue with Gingerbread and the Fascinate.
Any suggestions?
Anybody? Bueller?
Could my stock Samsung 16gb memory card be causing this? That's the only thing that was carried over from my old phone that had the button press issues to the new refurbished one.
Has anybody made that correlation?
Bump,
Googling about this problem, it seems this is a wide spread problem with Fascinate and few other Samsung phones. No one knows of the real problem nor a fix.
It is unacceptable for Samsung not handle this problem which sounds like it's hardware related for this long.
Any more input guys?
I was about to buy the Samsung Fascinate myself but this sounds like a major problem to me.
Hi everyone,
i don't know if someone already encountered this but sometimes my GS3 does not respond when i try to wake him up. (it's not turned off just standby). The screen stays black en nothing works. One time the screen did woke up but i couldn't unlock it because the touchscreen didnt work. It could not be turned off and the buttons didn't do anything! The only way for me to get out of this was a battery pull!
I did not root or modify anything on this phone because i like the stock samsung TW for the first time .
Did anyone else have this problem? And how did u solve this? Thank u.
Possibly due to an app you have installed.
Sent from my GT-I9300 using xda premium
dnlgee said:
Possibly due to an app you have installed.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thank u i didn't thought of that. Is their an easy way to find out wich app this could cause? I still find it very weird. If an app is not compatible than it just shouldnt install intead of breakin the phone right? XD
This happened me last night as well. Couldn't do anything other than turn the phone off, and when it came back on it was fine again.
Unrooted as well. Would like to find out how I can prevent this from happening again?
if you are not sure about the root cause of the problem better factory reset your mobile
bala_gamer said:
if you are not sure about the root cause of the problem better factory reset your mobile
Click to expand...
Click to collapse
Yes, if it happens again than i will try that. But i already sent the unit back from were i ordered it. They will send me a new one because its their policy to send a new one if something happens in 2 weeks.
So i will see if it still occurs with the new one otherwise its one of my apps. Than i will install only a few apps and see what causes it. If it doesnt occur one more thime than the unit was faulty. Ill keep u guys updated.
chicoelnino said:
This happened me last night as well. Couldn't do anything other than turn the phone off, and when it came back on it was fine again.
Unrooted as well. Would like to find out how I can prevent this from happening again?
Click to expand...
Click to collapse
Did it happen once? My phone had it like 3 times so thats why i sent it back. But if it still occurs with my new phone than it must be one of the apps i got Luckily they got DOA policy. I asked if it includes ''the phone does not work as it should" and they said yes send it back u will get a new one yaay but now i have no phone
I had this. After a hard reset, multiple times, and configuring with no accounts (no samsaung account, no google, nothing), it still happened. I ended up returning the phone and I've not had a single problem since.
I think it was either faulty memory or a dodgy firmware flash (more likely). Either way, I didn't care to find out and now it's all good.
sama said:
I had this. After a hard reset, multiple times, and configuring with no accounts (no samsaung account, no google, nothing), it still happened. I ended up returning the phone and I've not had a single problem since.
I think it was either faulty memory or a dodgy firmware flash (more likely). Either way, I didn't care to find out and now it's all good.
Click to expand...
Click to collapse
Yes lucky i found this out early too.. Because after another week i wouldnt get a new one and now i get
Factory reset your phone.
Hope everything turns out alright.
So I searched the forum for a bit and saw some people have similar issues but not the exact issue that I have. For some reason, my phone's power button only turns on the phone. After the phone is on, it doesn't work anymore. (i.e. will not put the phone into the lock state nor wake up the phone) The only way for me to wake up the phone is to plug it into the charger which will activate the lock screen.
Some additional information:
I am currently running Stock 4.0.3 ICS unrooted.
I have tried a factory reset on the phone.
I have also tried the *2767*3855# factory format code which is supposed to reinstall the phone firmware.
I was using the Go Launcher/Go Locker app as my default home screen and lock screen but this is still happening even after a factory reset back to TouchWiz.
This problem occurred after turning my phone back on this morning after it died due to running out of battery.
If anyone knows what I should do or can point me in the right direction, I would be grateful.
Warranty replacement.
raduque said:
Warranty replacement.
Click to expand...
Click to collapse
Boo, that sucks. Do you think going through AT&T or Samsung would be better? I guess its between a refurbished phone vs not having one for 2 or so weeks.
Malaranu said:
Boo, that sucks. Do you think going through AT&T or Samsung would be better? I guess its between a refurbished phone vs not having one for 2 or so weeks.
Click to expand...
Click to collapse
Funny thing about this question. We have a recent thread about this going on right this very minute. :highfive:
MotoMudder77 said:
Funny thing about this question. We have a recent thread about this going on right this very minute. :highfive:
Click to expand...
Click to collapse
Haha found it in the general section. =D thanks. :highfive:
Woe you are lucky! Hoed you factory reset without a hard brick
Sent from my SGH-I777
Malaranu said:
So I searched the forum for a bit and saw some people have similar issues but not the exact issue that I have. For some reason, my phone's power button only turns on the phone. After the phone is on, it doesn't work anymore. (i.e. will not put the phone into the lock state nor wake up the phone) The only way for me to wake up the phone is to plug it into the charger which will activate the lock screen.
Some additional information:
I am currently running Stock 4.0.3 ICS unrooted.
I have tried a factory reset on the phone.
I have also tried the *2767*3855# factory format code which is supposed to reinstall the phone firmware.
I was using the Go Launcher/Go Locker app as my default home screen and lock screen but this is still happening even after a factory reset back to TouchWiz.
This problem occurred after turning my phone back on this morning after it died due to running out of battery.
If anyone knows what I should do or can point me in the right direction, I would be grateful.
Click to expand...
Click to collapse
had the same problem few days back.well i stay in india so there is no option to get it repaired by samsung service center.so,i took the device to a local mobile service shop and he fixed the issue with in 3 Hours...he said that he has replaced the power button and now my device works fine..it costed me 10$ =550 Rs
I have the same problem with my galaxy S2. I have changed the button, but it doesn't work anymore.
Sorry for my bad english, I'm french.
My stock, never-rooted GT-I9300 (4.1.2, I9300BWELK1, JZO54K.I9300XXEMC2) is plagued by boot loop problems. It first started about 3 months ago, where the blue charge LED would suddenly come on and the phone would not wake from sleep. I pulled the battery, then when it was turned on it showed the initial S III logo, then the O2 logo followed by the glowing Samsung logo. Then repeated from the O2 logo endlessly. I pulled the battery again, then the next morning restarted it without the SIM or SD card in, and it had done a partial factory reset - i.e. lots of phone contacts were there with the texts, but all the settings had reverted to default. Later that day while on charge the same thing happened again, and I sent it away to O2 for repair.
When it returned, the same thing happened 6 weeks later although this time it was on when it froze and went straight to the O2/blue LED stage. Another repair (I'm fairly sure these 'repairs' were just factory resets...), and 6 weeks later exactly the same. Back to the O2 shop for another repair.
This time they replaced the 'main board' and when it came back it had a different Wi-Fi MAC address. This time only 6 days elapsed before the same fault arose again, and finally I was eligible for a replacement handset. This lasted 2 days before a boot loop condition occurred again! This time, being sure it couldn't be a hardware fault I tried my own /data and /cache wipe, which worked. I skipped all but the must-have apps, and I thought this was going to be stable but once more this past weekend the boot loop happened again (I've got my restoration procedure down to about 15 minutes thanks to the practice!)
I don't know what could be causing this and I'm fed up with resetting my phone. Are all S IIIs this unstable? I've never had a phone that required a factory reset within 18 months! When it is in the boot loop, I can access recovery and download modes, but safe-mode start-up has no effect.
The last remaining candidates I can think of are a problem with my SIM card, or a defect with my SD card... or an app. Can anyone suggest the best way to troubleshoot this? I'd really really rather not have to skip importing my settings as I have among other things many SSIDs I don't easily have access to re-create.
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
kernalk said:
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
Click to expand...
Click to collapse
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Skander1998 said:
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Click to expand...
Click to collapse
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
kernalk said:
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Everything to carries is "news".
I can't help with logs and whatnot, so I'll leave that to someone else.
You can always flash and downgrade to the older firmware that didn't give you a problem, if the problem persists, it is indeed an app.
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
That doesn't fill me with confidence!
Thanks again for the replies. I'm not wild about downgrading. I liked the improvements! Is it possible to downgrade in a carrier supported way? Retaining warranty compliant has been rather useful in the past few months!
Sent from my GT-I9300 using xda app-developers app
You can flash any official via odin.
Sent from my GT-I9300 using Tapatalk 4
Well late Friday night it did it again. Not sure when exactly as I was asleep. Woke up in the middle of the night and went to check the time, Looked at my phone to find the blue LED on when it should have been red for charging or green for fully charged, and it was very hot - wouldn't turn on either. Pulled the battery but it kust went into the loop. I was away from home so I couldn't do any troubleshooting and had no choice but to wipe.
This time I didn't restore settings and the only apps I installed were SMS Backup & Restore and Puzzle Alarm (I know this isn't the culprit as I only started using it this week!). Gone are all my precious wifi SSIDs but otherwise I'm not sure I've noticed the difference.
So I'm now not connected to my work wifi, nor have I set up my work email or Lync - two of the things I use my phone for must after Facebook which I've also not reinstalled. Facebook mobile web is really hard to use by comparison.
By chance I popped into the O2 shop later that day and had the fortune to bump into a Samsung rep who had never heard of this and agreed that I was unfortunate to have these problems (how touching!) and suggested I speak directly to Samsung support rather than O2 which I will do this week. I will also contact O2 about a replacement SIM and look into replacing the SD too.
This is really silly. I'm not keen on downgrading the software because the first thing either Samsung or O2 will do is upgrade it again. Frankly at this point I'm fed up with the whole thing but I've got a year left on the contract and even a pretty much new handset like mine won't fetch enough.