Hey guys, long time lurker.
Recently, the right 8th of my screen has become non-responsive. I have flashed several builds since then to confirm that this happens regardless of what ROM im running. I believe this is a hardware issue.
Does anyone know if there is a screen calibration/screen debug app to confirm this?
Or should i take my phone into verizon. if so, i assume i shoudl through the stock software on the phone? I have never had any hardware fail on verizon (d1, dx, tbolt user), how anal are they about replacing malfunctioning hardware. i do not have insurance (since i am very careful with my cell phones and have never broekn one).
Any ideas??
Should be covered under manufacturer's warranty.
Bamf sense 3.0 RC4 with MR2 radio
recap
took my phone into verizon (after flashing back to stock) and gave told them that i cleaned the screen, restored back to factory, etc. they looked at the phone for 30 seconds, and then said "ok, we'll send you a new one".
ive read a couple of other posts saying that i should return to stock (including the bootloader). so ill do that before i send it back. either way, thanks for the help
Related
Okay, googled, and bing'd the crap out of this and it looks like so far everyone who's had this issue has had to send their phones in for repair, but before doing that I thought I'd ask here aswell to see if anyone has been able to solve this problem.
I've had my HTC Surround for about a month now and this morning when I went to use it I noticed I couldn't read my emails, it said something like "Oops we were not able to retrieve your email." I thought no problem I'll just restart my phone. I turned it off, and turned it back on. Ever since then the phone has been stuck on the white HTC start screen. I've pulled the battery four times and tried restarting it. I've restarted it holding the volume up and down buttons and I get a bootloader screen (no option to hard reset). I can plug it into my computer on the bootloader screen and the computer recognizes the device as an HTC SD card. (This is nice to know seeing as I can, if I ever get the phone working again, load files on the phone's SD card that Zune won't let me) however this is bad because Zune will not recognize the phone.
Sooo, anyone else had this problem and been able to fix it themselves? I don't want to have to send it to HTC because I have no warranty. I bought the phone used. Any thoughts would be appreciated!
And this is running 7004, I have no unlocked the phone or tampered with it in any way. (yet)
Have you looked in the development forum for your stock ROM and tried flashing it from the bootloader?
I couldn't find a rom to flash. Maybe I will just use this as an opportunity to switch to Sprint and buy an Arrive. That way I can be done with ATT's crappy service.
I'm on my third surround now, with both previous ones dead with the exact same situation you have described. I called ATT, had them replace them on warranty for free. I'm waiting for this third one to die so I can get a different model
P.S. I tried flashing the stock ROM, hard resetting, and everything else trying to get both phones back to life but I ended up just having to warranty them. Call up ATT and have them send you a new one.
Thanks, I was able to do a warranty claim. Technically I wasn't allowed to because I bought the phone outright (used) on craigslist. But since the person at ATT was lazy and didn't check when I went in the sent me to my local device support center and I was able to walk out with a new phone in 5 minutes.
Hope this doesn't keep occurring though. If they were to ever check how the phone was purchased I'd be screwed.
doejohn531 said:
Thanks, I was able to do a warranty claim. Technically I wasn't allowed to because I bought the phone outright (used) on craigslist. But since the person at ATT was lazy and didn't check when I went in the sent me to my local device support center and I was able to walk out with a new phone in 5 minutes.
Hope this doesn't keep occurring though. If they were to ever check how the phone was purchased I'd be screwed.
Click to expand...
Click to collapse
I had the same problem with my Surround a few months ago. Then I had another one that kept losing the data off the device. I'm on my third one now and it has been holding up for three months.
I also noticed in the store that all the display models of the phone were having the exact same issue.
I think they changed something up, as this new one seems to be hanging in there much better than the last two.
hi
i am new , post post post
Phone info: rooted, stock, s-off, CWM 5.0.2.7, BusyBox 1.17.1, ES File Explorer
In a nutshell, my phone's display died after a bit of condensation appeared under the glass. I have no idea how the moisture happened, as I've been babying this phone since my 1/7 purchase, and I haven't dunked the phone in water or exposed it to steam. Had it tucked in an inside coat pocket while going for a walk, discovered condensation spots later that evening (and no, I don't sweat like a horse, either). Screen began flickering over next four days, requiring brightness to be turned up to max, but otherwise operated normally--until day five, when the display went out completely. Liquid indicator under the battery is pure white, btw.
So, after discussion with HTC Warranty and Repair, my phone will be shipped off to be fixed, hopefully, under warranty, and I won't get dinged for out-of-warranty repair since this is a moisture issue (albeit one I'm baffled as to the cause).
What I'd like to know is what to expect upon return of my repaired phone. I know the HTC tech's will likely be wiping all data, and this means I'll have to reroot, correct? I have my most recent Nandroid backup on both my PC and my SD card, so I can restore to that, but I wasn't clear about the rerooting end of things.
Any experiences from others who have gone through the warranty repair process would be appreciated.
Many Thanks --
--
King Cheetah
Well I sent my 3G Slide in to get the camera lens cover and keyboard fixed. I had the old hboot and flashed back to stock with s=on. They fixed the 2 issues and updated my phone to the Froyo OTA with the new hboot.
It isn't unrealistic to think the same would happen. So the Fabulous work the guys in the dev forum will be more appreciated once the hboot issue is solved.
Sent from my myTouch_4G_Slide using xda premium
Actually, I just got back my phone from repair. hboot was 1.44.007 the one that is hackable.
It's essentially a roll of dice right now, because the OTA isn't in full effect yet. Maybe you can make a special request that they don't restore your phone (although that's usually the first thing they do) or tell them that you don't want the latest OTA
That pretty much answers my question--I'll have to go through the process once more for root once I get it back.
As far as I've been able to glean from the HTC and T-Mobile forums, the OTA is still on hold due to error troubleshooting, so I doubt that will be applied until all the bugs have been squashed. In fact, there's no word that the update will be ready this month, so I'm fairly confident the hboot will still be 1.44.007.
Thanks for the replies --
--
King Cheetah
Yea - I sent one in to be serviced and got it back as it went out (fixed though) and still had s-off 1.44.0007 hboot.
I restored everything else to stock retail launch before sending it in.
They told me on the phone before I shipped it that if they chose not to repair i'd get charged. If there was evidence of tampering it was their option to not do anything to it.
I was also told that it would be flashed to their current software as the last thing before it left the factory.
I imagine it's up to the tech to decide if they want to work on it if it comes in with s-off - but now we have a guide for how to get s-on so this should no longer be a concern - it's in dev here.
Also, my theory was that the update being on hold was why I got it back with the software I sent it out on - and seems to be what everyone else thinks too.
Well, what the title says. It's becoming extremely annoying. Any suggestions?
what rom are you on?
I was on stock UCLA3, but when this problem occured I completely went back to stock. Still exists.
have you tried to do a 3e recovery factory restore?
I don't know what to do, honestly. I'm open to any suggestions! I'll look that up, thanks in advance.
Flash a custom rom with good kernel!
Well, I returned the phone to its original state. Exactly how I bought it.. The problem still exists. I don't think this is a kernel/rom issue.
What does ATT look at when they do exchanges? My counter says 2, is that a bad thing? Or can I just say I was trying to restore it because it kept shutting off and I didn't exactly know what I was doing? It has to be something with the hardware.
MAGiK9 said:
Well, I returned the phone to its original state. Exactly how I bought it.. The problem still exists. I don't think this is a kernel/rom issue.
What does ATT look at when they do exchanges? My counter says 2, is that a bad thing? Or can I just say I was trying to restore it because it kept shutting off and I didn't exactly know what I was doing? It has to be something with the hardware.
Click to expand...
Click to collapse
Yeah thats a bad thing, but they probably wont say anything. Don't mention anything about the counter
I started having the exact same issue this last weekend, took my phone into At&t warranty center, they replaced the battery and did a reflash back to factory rom. Still had the issue after that. The problem didn't start till after I took it out of my otter box and started taking the back off to pull the battery for rooting and flashing roms. Since i have put the phone back in the otter box case I have not had it restart on my yet. I am thinking it is a loose back cover and the battery is being knocked loose and then back in place hence the restarts. Just some of my observations from my own experiances with this same problem.
Ironically, mine has never happened until I took it out of the Otterbox Commuter case.
luckily i haven't had this issue, and i have removed it like 8-10 times before learning I didn't have to...
I took my phone to the att store so they could look at it.. I explained what was going on and the guy told me he was going to check the counter.. BUT he never did. He ordered me a new battery, and if that does not work they will send me a new phone. However, i'm going to get the new phone anyway.
Reboot issues and battery
Ok, same problem here, ICS leaked 4.0.3, Samsung Galaxy S2 skyrocket. Thought it was setcpu and/or busy box, not.. I notice that when I moved my phone in an odd manner it would reboot. Removed the battery cover and noted that there was play in where the battery sat, so much so that I was able to stick my finger nail into the separation, I don't know call it a half a cm. Any way, I took some note book paper, made a wedge so the battery was nice and tight... so far so good. Will let you know.
I'm not sure if this will be any help or not. My phone has done the same thing a couple of times and at least twice I've noticed that it was because I had the phone in my pocket and I was accidentally holding down the power button when I was bending over/squatting/etc. As for the other times it has restart on its own, I have no idea. It's been at least a month since those happened though.
Hello all, i am having a couple of problems with my sensation,firstly its a refurb supplied by an insurance company and they only gave it a 30 day returns policy which expire over a month ago,i had already sent one back where the microphone didn't work.
The first problem is that i have a green flickering that appears on just over half of the screen (see attached video) it comes and goes but is there most of the time now,if it gets really bad in the area where the screen flickers the graphics within that area goes corrupt almost as if someone has brushed the graphics down the screen with a paint brush.
It is worse than the video shows but only have an old phone to take the video with.
Could this be hardware malfunction? It was there before i upgraded to 4.0.4 and there afterwards.
The second problem is since upgrading to 4.0.4 i have terrible battery life 8-9hrs max the phone keeps turning it self off, on nearly every re-boot "upgrading applications 0-32" comes up runs through the upgrading and then turns off again. these re-boots also suck the life out of the battery.
I haven't yet tried flashing a new custom rom to it as it has not been rooted etc yet.
Any ideas/suggestions?
Thanks in advance.
I am 99% sure the screen flickering is hardware related. For battery life, firstly check for battery draining apps running in the background. The android is upgrading message happens when android is building the dalvik cache and seems to happen only when dalvik cache and cache are wiped on deodexed systems, however it seems to happen on every boot on odexed systems but either way, its normal and nothing to worry about
oh well time to phone the insurance company AGAIN then,just as you get all your progs/games on your phone you want on there, somethings screws it up.
was gonna flash a custom rom to see if that worked out the screen probs but, i shall wait until i know what the insurance people say.
Thanks for the response
Now what to do for the best????
Ok so i contacted my insurance company and they agreed to take the phone and fix it for free,they have dispatched a special delivery envelope to me.
I have wiped my phone and got a little annoyed because i have got 29gb worth of programs installed and its such a pain in the arse to reinstall everything!
So the phone is now reset to factory settings and guess what......Thats right the fault has gone!
What to do still send it off with no visible fault?
Or keep it?
I cant see it being a program thats did it as i hadnt s-offed the phone or rooted it so there shouldnt be any software that can interfer with the phones screen can there?
I have had a few "huh humm" trial versions of games and apps on it,could there be mal or spyware that has done it or possibly where something may or may not have been [email protected]?
What to do.....
back a little bit...Damn phone
Well after the factory reset the battery life is a lot better.
The screen flicker has come back but very very intermittently so hoping that the tech guys at either the insurance company or more likely HTC as the insurance people quoted this "you should within 17 days you will get your phone back" will be able to see it.
All this trouble aside this is definitely one of the best phones i have ever owned and i love it,never did i think back in the days when i owned a titan II and a jade did i think i would ever see graphics like i do today,the game, application programmers/designers and the phone makers just keep on astounding me with what they produce.
I sent my LG G2 back to LG some months ago as the top of the screen was unresponsive and the screen was starting to get unglued. It was right before my warranty ended. When I got it back, as my warranty was already expired I decided to root the phone (using stump), but I kept the stock rom. Actually the only reason I rooted my phone was to install jishnu's camera mod as I wanted better quality pics and 4k video (and that never happened as I never got to see the lg g2 version of it).
After a couple months, my phone started rebooting with no apparent reason. After a week of this shenanigans, I woke up one morning to a bootloop. I was able to get it in download mode, so I tried flashing the original stock to undo the rom using the LG flash tool method (http://forum.xda-developers.com/showthread.php?t=2663369), but It didn't go through because it said it was a different version of the phone. I even try with the alternative dll provided in the post with no luck.
Two days later, after fighting tirelessly with the phone, I was able to get into recovery (twrp). At this point, I installed a Rom (slimkat) and that seemed to fix the problem. Then, a couple days later my phone started doing the same stuff again. Most of the time, the reboots were quick and it only bootlooped every now and then, and finally going into android. It get's really hot around the camera though.
Today it's absolutely stuck in a boot loop and won't go into recovery. I was able to pull the logs a couple days ago right after a reboot.
I would really appreciate if anyone could look into them and tell me what's wrong and if it's possible to fix. My biggest fear is it is hardware related (which would suck because it basically just came back from being serviced).
Except for these last episodes, it's the best phone I ever had. I love the quality of the pics, the size, the screen and I was hoping not having to upgrade for a couple years.
Thanks in advance.
(I removed the Logs because even though I scrubbed personal data from them, I still got 16 downloads and not a single reply related to them, and just to be safe, I will minimize the chances of anything going sour)
Have the same issue. It just started going in bootlops. Sometime I can get a few hours of use if I am lucky but no matter what I do (diff roms,baseband, lg flash tool to original firmware) bootloop will not go away.
Seems like something many people are experiencing after a year.
Let me know if you figure it out