Just wondering if anyone else is having this issue. Today while using my phone in different apps the phone would suddenly stop recognizing touch input and while I wasn't touching it the apps would behave as if someone was touching it all over. I'd try exiting the app, but the capacitive buttons would not function. I hit the power button and when I came back from the lockscreen I was able to exit and everything worked for a while. Then it started happening again. I did a restart and it was still happening. Turned the power completely off, left it for a while, and then turned back on and haven't noticed it again, but haven't been using it much.
I've been on meanrom for a couple days and this just happened today. Anyone else experience something like this? I'm hoping it doesn't happen again and if it does that it isn't a hardware issue. A real downer if I have to flash it again because I just got everything the way I like it, but I'd rather do it again than have to send it for repair.
Could be the kernel, are you using an overclocked kernel?
Yes, I believe meanrom comes with an overclocked kernel. I would get the non-overclocked version if I could, but that doesn't seem to be an option. I'd ask about the issue in the rom thread, but I can't yet.
FrankthaTank said:
Yes, I believe meanrom comes with an overclocked kernel. I would get the non-overclocked version if I could, but that doesn't seem to be an option. I'd ask about the issue in the rom thread, but I can't yet.
Click to expand...
Click to collapse
MR 4.8.1 comes with [email protected] default and 1.5ghz and 1.8ghz as options check the MeanROM-ICS folder for the othe 2 options
Some kernels undervolt as a way to conserve power, they use other tricks like predetermined voltage stepping and may have modified governors as well. Any one of those can cause issues with hardware, then again it could be a simple ground issue with you phone. Have you tried pressing the edges of the screen? It may not be sitting correctly, the og EVO screens would have issues with grounding when the screens for what ever reason would start lifting.
Ah, thanks! I'll give that a try.
Seriously you guys are freakin awesome. And so fast. Thank you! XDA is lucky to have you guys. Glad I joined. :victory:
FrankthaTank said:
Ah, thanks! I'll give that a try.
Seriously you guys are freakin awesome. And so fast. Thank you! XDA is lucky to have you guys. Glad I joined. :victory:
Click to expand...
Click to collapse
Sounds like a digitizer issue to me.
Sent from my EVO using xda premium
That may very well be the case but, digitizer issues can still be attributed to a ground fault, undervolting or voltage stepping. I'm sure op will let us know, I too am leaning towards hardware failure though
Bad news. I tried one of the developer tools that shows a line for pointer location. It appears I have a dead zone. I had tested out this tool before and it was a constant line, but now it always skips over the same spot (a horizontal strip). It came back briefly, but now it seems to be really dead.
I might try a full wipe and flashing another rom, but this does seem to be a hardware issue. Really disappointed since I just got the phone. It never got rattled or dropped or anything. I guess I'll have to go for repair, but anyone know if there's a chance that I can get the repair guy to leave s-off? Also through TEP there shouldn't be a deductible for repair, right?
Thanks again om4 and bigdaddy619 for all the assistance.
A lot of sprint repair centers no longer work on damaged screens. They don't have any legitimate reason not to either. Sucks to have to get it replaced
om4 said:
A lot of sprint repair centers no longer work on damaged screens. They don't have any legitimate reason not to either. Sucks to have to get it replaced
Click to expand...
Click to collapse
Had to get a replacement, but figured out why the Sprint centers don't do screen repairs anymore. According to the repair person at the store I went to, the insurance felt there was some fraud going on with the employees selling screen parts. Apparently there is a big market for smartphone screen parts. So the policy is that phones must be sent in for a refurbished replacement if the problem is with the screen. Since mine was new though, I got a new replacement.
I was told that it was due to the overall cost....what you said makes way more sense. Way to go dbags, making things so much more complicated for regular customers
Related
Something just isn't right about all of this. I think everybody agrees that the random reboots are a result of the recent update and is something that will be fixed by another update. If that's true, why is Verizon swapping out phones for people?
I called Verizon yesterday complaining about the reboots and was told to factory reset my phone as it had been working for other people. I was also told to call back if the reboots continued and that my phone would be replaced. Of course they continued so I called today and have a replacement on its way.
I guess I'm hoping that the phone I get hasn't had the update applied. If it has, what's the point of Verizon sending it? How is it even possible that their tech support doesn't know the cause of the random reboots?
yes i agree it seems a little fishy. but for the average customer rolling back the software might not be the easiest thing to do. not to mention its a PITA.
i would imagine it makes them happy hearing they will get a new phone. i think its just a band aid while they are working on it.
headcheese said:
yes i agree it seems a little fishy. but for the average customer rolling back the software might not be the easiest thing to do. not to mention its a PITA.
i would imagine it makes them happy hearing they will get a new phone. i think its just a band aid while they are working on it.
Click to expand...
Click to collapse
The thing is though, tech support never told me not to update the new phone when it arrives. I won't be updating but there's a lot of people out there who don't keep up with these forums that are going to update and end up right back in the same boat.
Maybe they want to investigate the phones with issues
My advice is don't get a replacemnt for your phone because your giving up a new bought pphone for a refurbished phone. Bad choice in my opinion.
One mmore thing. Verizon is not taking these phone in for investigation. Here merely just a company trying tto make the customer happy that's why there replacing phone. There nothing techy about it. Its just an attempt at customer satisfaction.
I agree with dalrym05. I had random reboots both Before and After i applied the ota. Don't think it has to do anything with the hardware.
Sent from my ADR6400L using XDA App
My wife has had random reboots before the update. Hasn't had any since the update. Mine has had one reboot when I was watching a 2hr video on youtube with a very low battery when it did it. I really think it has something to do with apps not being addressed properly. She has apps I would never use and one was causing an issue, so she pulled it. The lag stopped at that point. If they swap your tb and it reboots, start looking at what is installed.
Sent from my SCH-I800 using XDA Premium App
I just wanted to spread the gospel. If you follow the instructions in this thread, http://forum.xda-developers.com/showthread.php?t=1081230 it has virtually eliminated the random reboots for me. I also had reboots after updating my radio. I used the combo prescribed in this thread and they are gone
dalrym05 said:
My advice is don't get a replacemnt for your phone because your giving up a new bought pphone for a refurbished phone. Bad choice in my opinion.
Click to expand...
Click to collapse
I agree. Unless my phone is practically unusable through no fault of mine, I try to hold off on getting a replacement phone as much as possible.
Sent from my ADR6400L using XDA Premium App
Verizon has acknowledged the rebooting problem and is working with HTC:
http://www.androidcentral.com/htc-verizon-working-thunderbolt-reboots
sprodigy said:
I just wanted to spread the gospel. If you follow the instructions in this thread, http://forum.xda-developers.com/showthread.php?t=1081230 it has virtually eliminated the random reboots for me. I also had reboots after updating my radio. I used the combo prescribed in this thread and they are gone
Click to expand...
Click to collapse
That's great for people who are rooted.
So, yesterday morning this all went down. My Rezound has been nothing but an expensive paperweight. I am not new to the rooting game so save the nonconstructive comments.
Early Monday morning I felt the need to change things up a bit so I wanted to flash the latest CleanRom 3.7 to check it out (coming from BAMF v.09). I backed up all my apps & data and continued to make a nandroid backup (with Amon_Ra 3.14). After that, I completed the necessary wipes (including boot because Scott packages his roms with the kernel) in recovery and then flashed CleanRom 3.7 (MD5 sum matched) then booted into bootloader to flash the kernel. Everything went perfect with that.
After the phone booted I realized how low on battery I was on but connected to Wi-Fi during the initial start-up on the new rom. I got all my accounts and data synced/restored and was getting ready to knock out. I set my alarm, placed the phone on the wall charger and confirmed it was charging by the orange light around 3am.
I woke up yesterday morning around 7:30am and realize I'm running late. I pick up my phone to see if the time is correct and I get nothing but a black screen. Pulled the battery...nothing...plugged in the phone without the battery..then plugged in the battery...nothing. On my 45 minute commute to work I removed the battery and let the phone sit (hoping some magic would happen lol) and nothing changed.
When I made it to my office, I plugged the phone in to see if it would accept a charge and 2 hours later nothing. I have the 3.7v battery and have had no indications of a bad battery (short life, warm, etc.). Due to the circumstances, I was left with no choice but to go to the local VZW and order a replacement.
The guy at the Verizon store plugged my phone in the wall charger and saw it was not accepting a charge. Swapped the battery with his own personal Rezound and mine worked in his, however, his fully-charged battery would not work in mine. Narrowed it down to the phone itself which blows. I thought at worst it would be the battery.
I am really curious how/why this all went down of all times when I wasn't doing anything to my phone. You guys/gals have any idea?
Marcismo55 said:
and continued to make a nandroid backup.
Click to expand...
Click to collapse
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
My bad..I forgot to mention I have been running Amon_Ra from the start. I've never ran CWM on my Rezound and I did run across some threads regarding the charging issues associated with CWM.
Thanks though!
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
mpalatsi said:
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
Click to expand...
Click to collapse
Yes. All the contacts were intact and free of dirt/debris.
pkopalek said:
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
Click to expand...
Click to collapse
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
More than half of all the roms out there are from ports/leaks. Please explain.
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
nosympathy said:
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Actually I didn't even take the SIM out. Maybe I should have given that a try.
EmerikL said:
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
Click to expand...
Click to collapse
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
That's only for charging when you're booted into recovery if I'm not mistaken...
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If flashing killed it, it would have never booted back up...
Marcismo55 said:
Actually I didn't even take the SIM out. Maybe I should have given that a try.
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
Click to expand...
Click to collapse
In my case when the Verizon rep gave me the phone he put the sim in and put it in backwards. To be fair, it does go in "backwards" to every other android phone I have owned haha.
Sent from my ADR6425LVW using XDA
mjones73 said:
That's only for charging when you're booted into recovery if I'm not mistaken...
Click to expand...
Click to collapse
It may depend on how you're charging. The charging process requires some intelligent oversight - if you power off the phone, and connect a charger, the process is controlled by code loaded from somewhere. I think that code is in, or loaded by, the recovery. That would tend to explain things like this, this, this, and this.
jayochs said:
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
Click to expand...
Click to collapse
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Marcismo55 said:
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Click to expand...
Click to collapse
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
^This. Even if it is new hardware there can be defects. **** happens!
Marcismo55 said:
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Click to expand...
Click to collapse
I assessed your OP as related to a phone not charging.
I see what you mean, now. My points were in the case of non-charing, or failure to charge (and a phone going dead on the charger) which aren't things I've seen on any stock-based ROM, but very much so on ICS ROM's (and Kernels, as such).
I bid you good luck on your replacement hardware. Stuff happens!
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
I understand Scott. I am in now way shape or form saying flashing your ROM was the reasoning behind all this as I have flashed numerous times before this and had no issues. Also, considering I am one of the very few this has happened to, i think its pretty obvious this was a hardware failure. I
I'll be running your roms soon enough
Thanks to everyone providing insight on this situation. I'll be back at it again very soon!
Hey guys, I came had the HTC Sensation, and I broke it VERY bad, and T-Mobile refused to give me a new one, so I bought the Amaze 4G on Amazon.
The phone worked okay for the first week, and about 10 days after I had it, it started to randomly freeze and I would have to lock and unlock the screen for it to work again.
Wasn't a big deal at first. It was almost as if the processor wasn't getting enough voltage for example, on my Sensation if I undervolted it too much it would freeze up and I would need to pull the battery.
Not as big of a deal though, but it is SO ANNOYING when trying to text or type something and having to go through the whole process.
But then the device was getting very slow when I had it on the charger, so I argued with Amazon to take it back and they said I would have to contact the private dealer.
I had no luck with the dealer, so I basically got screwed over out of 500 bucks.
BUT... I think the problem is fixable...
Correct me if I'm wrong, (and I probably am), I am NEARLY 100% positive this is a battery issue or a processor issue.
And maybe one of you phone geniuses will be able to help me out (You guys never dissapoint)
But before I drop 15 dollars on a battery, I want to know if one of you have had experience with a problem like this. Even after rooting, wiping, installing countless roms and apps, I have had no luck at all.
Did you buy it used?
Iscreaman2311 said:
Did you buy it used?
Click to expand...
Click to collapse
Yea it was "Certified Refurbished" by the company, but they said that there was no way to prove it was like that when it left their shop, so basically I got screwed out of everything. I tried contacting HTC also and they said a standard repair could range up to 100 dollars, and I really don't want to spend that unless I have to, but I am almost positive it's the battery that doesn't give the phone enough power. I will take it up to T-Mobile and see if they have a tester battery I could use. Very weird problems though, it makes me wonder if it's more than the battery.
Thaxtonator said:
Yea it was "Certified Refurbished" by the company, but they said that there was no way to prove it was like that when it left their shop, so basically I got screwed out of everything. I tried contacting HTC also and they said a standard repair could range up to 100 dollars, and I really don't want to spend that unless I have to, but I am almost positive it's the battery that doesn't give the phone enough power. I will take it up to T-Mobile and see if they have a tester battery I could use. Very weird problems though, it makes me wonder if it's more than the battery.
Click to expand...
Click to collapse
I think we need more info before we can think of possible reasons for the problem.
Are you rooted?
What software version are you using?
Did you do the factory reset?
What apps are running background?
Did you try different sd card?
Did you get logs (logcat, etc.)
etc. etc.
It may be purely hardware issue like you say, but as you say, software can cause similar problems, too. Especially, if you can remedy the problem by going in to the lockscreen and back, I think it is software related.
EDIT: Wait a minute! You're the same guy asking about s-off'ing the phone with ICS leak, aren't you? Probably you didn't flash the original ICS RUU before flashing a custom ROM? Mismatched firmware can cause tons of problems and there's no easy solution to it rather than to flash the firmware. But then, if you're not s-off'ed, you can't flash firmware to begin with. What a mess you are in.
Also if you think it's a battery problem plug the thing in problem still there not the battery. It will get full power plugged in even with a bad battery.
Sent from my HTC_Amaze_4G
My phone began having issues with touch behavior. It has over time gotten worse to the point where my phone seems to have a mind of its own. I took it in to a sprint repair center because I have read that the digitizer is a common failure with the Evo 3D. Anyway the repair guy told me that the issue was because I am rooted, that root corrupts files necessary for correct touch input. I have never herd this before and wanted to ask if anyone can either confirm or deny this. I would like to specifically read some developers perspective on this.
IXKastling said:
My phone began having issues with touch behavior. It has over time gotten worse to the point where my phone seems to have a mind of its own. I took it in to a sprint repair center because I have read that the digitizer is a common failure with the Evo 3D. Anyway the repair guy told me that the issue was because I am rooted, that root corrupts files necessary for correct touch input. I have never herd this before and wanted to ask if anyone can either confirm or deny this. I would like to specifically read some developers perspective on this.
Click to expand...
Click to collapse
Completely untrue. Rooting voids warranty and so that's why he came up with that excuse. Just unroot (this guide is good), and then take it to the sprint store again and don't say anything about root. they should give either a replacement or replace the digitizer. Then you can just root the new phone or root again.
Well the surprising thing is he gave the phone back to me and said he had ordered a replacement phone and that they'd call me when it arrived. This is why I asked, because I wanted to know whether to root my new phone when it came in.
He gave the phone back to you and ordered you a new one at no cost to you because that's just a trick reps play..
Root had no effect on screen wear and tear or digitizer failure..
Sent from my PG86100 using XDA
This just goes to show that you should read and research before modifying your device. No root has no effect on hardware.
#Root-Hack_Mod*Always\
I started having serious screen errors after flashing the VM firmware. I tried the fix, and it didn't work for me. Looking at a multi-touch test, it's showing four touch points in the middle when I'm only touching it once at the top.
flomexico said:
I started having serious screen errors after flashing the VM firmware. I tried the fix, and it didn't work for me. Looking at a multi-touch test, it's showing four touch points in the middle when I'm only touching it once at the top.
Click to expand...
Click to collapse
Unfortunately that's what happens when people flash hacked/leaked firmware. Rooting itself doesn't cause hardware problems, but flashing things like this does. Hopefully someone will come up with a fix to fully reverse it. If not, hopefully you have insurance.
mreyesems said:
He gave the phone back to you and ordered you a new one at no cost to you because that's just a trick reps play..
Root had no effect on screen wear and tear or digitizer failure..
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Do you mean that I could get billed? Or what would be the purpose of the trick?
IXKastling said:
Do you mean that I could get billed? Or what would be the purpose of the trick?
Click to expand...
Click to collapse
They could bill you for service w/out warranty but only if you tell them to.
Sometimes they say things like that because they don't want to go through the hassle of ordering a new phone for you, especially since they don't earn any commission for that kind of help.
Also, technically if you are rooted your warranty IS voided, even though a lot of the time hardware problems aren't related to root at all. I guess what I'm trying to say is they technically aren't aloud to replace a non-warrantied item so they make up a reason why they can't in order to keep the customer at least somewhat understanding.
sitlet said:
Unfortunately that's what happens when people flash hacked/leaked firmware. Rooting itself doesn't cause hardware problems, but flashing things like this does. Hopefully someone will come up with a fix to fully reverse it. If not, hopefully you have insurance.
Click to expand...
Click to collapse
Yup, my impatience screwed me over. I'm probably gonna end up bricking it.
In relation to the thread, rooting doesn't do anything. So yeah, you got got.
Yea, I had the same problem and the store said the same thing. Like others said, it's untrue. The stores will try to avoid the issue but phones should be replaced.
Sent from my EVO 3D on ICS using XDA
So last night, my phone decided that it would no longer like me to use it. The screen is a full screen of (for lack of a better term) rainbow snow. It is pixelated. I can't see anything except the snow. I have gotten it to show my lock screen by kind of tweaking the phone by bending slightly. When I get the lock screen, the touch screen no longer works. I can hit the power button to turn the screen off, and then again to only get the snow. I am thinking it's probably a hardware issue. I haven't dropped it or gotten it wet. Which leads me to my next question. I am rooted and running CM 10.1. I can't get in to recovery mode to restore to a stock ROM. If I take it in to Sprint for repair/replacement will they have a way of seeing I am running a ROM and decide they wont't work on my phone?
thedanpal said:
So last night, my phone decided that it would no longer like me to use it. The screen is a full screen of (for lack of a better term) rainbow snow. It is pixelated....
Click to expand...
Click to collapse
Is it possible that you CAN get into recovery and you just don't know it because you can't see it? Work with me here.
If you can power down the phone, try powering up into bootloader/fastboot and try to flash an appropriate RUU from fastboot/usb. Just a shot in the dark...
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
tmwilsoniv said:
Is it possible that you CAN get into recovery and you just don't know it because you can't see it? Work with me here.
If you can power down the phone, try powering up into bootloader/fastboot and try to flash an appropriate RUU from fastboot/usb. Just a shot in the dark...
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Click to expand...
Click to collapse
That is a very good chance. I will give it a shot tonight. Thanks for the idea.
I pretty much have no idea what to do now. My phone won't mount the SD card on any computer. The phone recognizes the SD card, i just wont mount it. When trying to use RUU i just get the error 170. So, i guess i will be dropping my phone off at sprint and hope for the best.
Same issue. Was running Carbon which is cm based. Tried everything, nothing worked. Took it to the Sprint store yesterday and they got me a refurbished LTE. I'm thinking of getting the HTC one but can't afford it right now. Refurb phone works alright so I'll just keep it for know but I know what you're going through. it sucks and although the ROM worked awesome it may have been the culprit.
Sent from my EVO using xda app-developers app
SiGuy11 said:
Same issue. Was running Carbon which is cm based. Tried everything, nothing worked. Took it to the Sprint store yesterday and they got me a refurbished LTE. I'm thinking of getting the HTC one but can't afford it right now. Refurb phone works alright so I'll just keep it for know but I know what you're going through. it sucks and although the ROM worked awesome it may have been the culprit.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
The tech thought it was a connection issue with the display, but he couldn't get it fixed and thinks the motherboard went bad. They are replacing the phone with a new one, but they are backordered so I have to wait a week.
Yeah but what caused all of our phones to have the same issue that doesn't exist on sense roms? Kernel overpowering the motherboard causing it to fry?
Sent from my EVO using xda app-developers app