Anybody ever have this happen to your MZF? Happens once every few days, and usually goes away after a few shakes. A few times I hard-rebooted the phone, and the display was still messed up in Recovery mode; the top half of the screen was affected but not the bottom. I could actually see the rows of static being drawn on the screen in big chunks. I can't remember if it was happening before the 7.1.1 update, but I think it was. Thinking it might be a faulty connection?
My phone did that around that time. It went away, but it's back now. Not only is it back for me, but it won't actually reboot. I can hear the splash screen (as if it was rebooting) however, the screen doesn't change. Still stuck with those crazy lines.
I had this happen... probably about 3 separate times. Each time there would be moments (either after tapping it, squeezing it, rebooting it) that it would flash back to a normal screen, then after about an hour it seemed to stay "fixed" probably for a month or two. The 3rd time it happened in the morning and hadn't resolved by the time I left work and stayed that way as I took it into Verizon. The Verizon guy took care of ordering the factory replacement at 7:30pm and it arrived literally the next morning. The crazy thing was that after I left Verizon it resolved and stayed "fixed" until I wiped it and sent it back in to Verizon, so I was able to copy and duplicate everything to the replacement phone.
While the screen looked like that, all the functions remaining intact, i.e. I could guess where I should tap and the sounds occurred that should have. I even attached my projector mod and the projector would display everything correctly even as the phone display was not.
I have not had the issue reoccur on my replacement phone.
Sent from my XT1650 using Tapatalk
Sent from my XT1650 using Tapatalk
edneum2 said:
I had this happen... probably about 3 separate times. Each time there would be moments (either after tapping it, squeezing it, rebooting it) that it would flash back to a normal screen, then after about an hour it seemed to stay "fixed" probably for a month or two. The 3rd time it happened in the morning and hadn't resolved by the time I left work and stayed that way as I took it into Verizon. The Verizon guy took care of ordering the factory replacement at 7:30pm and it arrived literally the next morning. The crazy thing was that after I left Verizon it resolved and stayed "fixed" until I wiped it and sent it back in to Verizon, so I was able to copy and duplicate everything to the replacement phone.
While the screen looked like that, all the functions remaining intact, i.e. I could guess where I should tap and the sounds occurred that should have. I even attached my projector mod and the projector would display everything correctly even as the phone display was not.
I have not had the issue reoccur on my replacement phone.
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
Sounds like exactly the issues I had, functions intact even though the screen was janky. Luckily was still in warranty period from Moto so got a new one sent to me. (Moto customer service is the ABSOLUTE WORST by the way). New phone is working fine... so far.
Related
So I recently called VZW to get a replacement phone for my Droid 2 due to the fact that it kept auto resizing things by it's own. The new phone I received via Fed Ex booted fine and I installed my backups and everything. Thing is, my GF accidentally dropped the phone on the ground (facepalm...) and after that the phone no longer boots properly. No physical damage as far as I can tell, no scratches or anything. When I turn the phone on the LED backlight turns on and a thing white line (Think 1 pixel by 1 pixel straight line horizontal across screen) flickers on and off.
I called VZW and they will be sending me ANOTHER replacement phone.
My thing is, since I can not boot into it to wipe and restore to factory settings, I don't know what will happen when I send the phone back with the root and what not.
Any tips?
komputerfreek said:
So I recently called VZW to get a replacement phone for my Droid 2 due to the fact that it kept auto resizing things by it's own. The new phone I received via Fed Ex booted fine and I installed my backups and everything. Thing is, my GF accidentally dropped the phone on the ground (facepalm...) and after that the phone no longer boots properly. No physical damage as far as I can tell, no scratches or anything. When I turn the phone on the LED backlight turns on and a thing white line (Think 1 pixel by 1 pixel straight line horizontal across screen) flickers on and off.
I called VZW and they will be sending me ANOTHER replacement phone.
My thing is, since I can not boot into it to wipe and restore to factory settings, I don't know what will happen when I send the phone back with the root and what not.
Any tips?
Click to expand...
Click to collapse
Can you boot to bootloader?
I ended up having to send my phone in with root on it, nothing happened. Got the text on the new phone saying "Thank you for returning your device!" and nothing happened after that.
theecho said:
Can you boot to bootloader?
Click to expand...
Click to collapse
Every once in a while it will flash the bootloader really quick but it flickers the white line again so I guess not.
Sent from my DROID2 using Tapatalk
I got up this morning, grabbed my tablet, switched it on and found that no matter what, it wouldn't respond to touch input.
Hoping I could sort of "kick it" by using a keyboard I plugged one in and while that worked fine, it didn't unstick the digitizer.
Had to reboot.
Anyone else seen this?
I've had this happen once or twice, and as you mentioned the only way to get it to respond was by a reboot.
oooooo.... never happened to me for the full 6 day since i have this tab i suggest you turn then for replacement....
just remembered something are you guys by any chance use screen filter? that causes touch problems in some spots....
I'm using it on my phone but but not the iconia
its has happen twice in the last two days. Usually when the tab is left for a while hours. You're right the only way to unlock is to reboot.
thor2002ro said:
just remembered something are you guys by any chance use screen filter? that causes touch problems in some spots....
Click to expand...
Click to collapse
Na, I'm not using a screen filter. It happened twice in the first couple of days of owning it and hasn't happened for the last couple of weeks. I've had the same thing happen on the Desire HD a couple of times as well. It doesn't happen very often so I'm not overly concerned.
Jup, sometimes the screen doesn't respond. I found that if you rotate it (even with the lock on) and then turn on the device the screen wants to rotate and will then be unresponsive. Reboot and all is fine. Seems like a software bug to me.
Just in case you haven't done so, remove the sticker on the right border. It has a metallic back and interferes with the screen. I had that happen on a display model at BB twice withing 10 minutes. Once I removed it, no more problems. And I haven't had any problems with my purchased one.
A friend of mine bought one online and complained about the same thing. I told him to remove the sticker and the issue went away.
the sticker on mine was removed in the first five minutes. haven't had the problem again yet. hope it was a fluke
I just got my transformer in a few days ago, bought it off of a store on eBay that I HAVE ordered from before. All the plastic was on the device and everything, thank god I haven't flashed custom ROM. Just a few minutes ago my girl was playing pinball when the screen started going NUTS on her. The screen started flashing on and off and then colored waves of pixels started passing through random bits of the screen. The game stayed in the background while all this happened I guess on top of it. It just kept doing it and would act like it was going to stop for a second then happen again. Finally I was able to turn it off after having to time my ninja-like finger jabs with the screen flicker. I waited a few minutes and turned it on again. The ASUS screen popped up and then went black for a minute, I pressed the power button quickly and the Eee pad screen popped up and then went into the lock screen. Everything seemed normal for 2-3 minutes, I downloaded a quick dead pixel detector app and everything passed fine. I just rooted last night using Razorclaw, so I checked my superuser to make sure there were no problems (just in case) and it needed an update. I did so and checked it, because it kept force closing auto-open apps when the tablet booted, after the update those apps opened fine (titanium and rom toolbox). right after this, maybe about total 7 or 8 minutes after booting, the screen began flashing again as I was trying to uninstall the dead pixel app. eventually she timed her own finger jabs with the demon screen flicker and clicked OK to uninstall app. as it was uninstalling the screen started working fine. right after it was done uninstalling (bout 30 seconds), what do you know, the bloody ( i love that word) screen started being crackhead-ish again. Its turned off now. Does anyone have any prior experience with this issue? I will contact the razorclaw team to ask them if maybe its a side effect, but I just wanted to see if any of you folk knew anything about this. It IS a newer B70 model and I do have another 5 days to ship it for a return from the seller. I'm pretty sure I will unless I get a response with a sure fix for this being software or something. Also while I've got your attention, I'm under the impression I can boot to stock recovery to factory reset? hopefully at least.... and if I do so, please tell me this will remove root access?
Thanks much in advance for your answers, which I'm sure there will be some useful info as usual with XDA.
Lemonoid
UPDATE: MY tablet won't turn on now.
Best option, return the defect peice..
Hey .. if you have 5 days to return to the shipper, go ahead and return the defect piece. My wild guess is that it has no connection to the software installed or rooted, its mostly an hardware issue (first of its kind though).
I have not faced any screen related issues with my B80 version...
Return this & Get Prime
Cheers,
Amrth
i do agree with the guy above,
write what hapend and return it, and in hope that they can fix it, if not u will get a brand new or the money back.
My TF101 works flaviously and it's something i wanted and even with custom rom its more better and funnier, so yeah, thats a hardware issue or some "wrong made tablet"
My rooted 32GB has just started doing this (2nd time this has occurred now). When I try to unlock, it just makes a click sound and relocks and blacks the screen. The first time resolved itself. Not sure if a reboot will help (probably so), but wondering if anyone has seen this or has any suggestions.
doncaruana said:
My rooted 32GB has just started doing this (2nd time this has occurred now). When I try to unlock, it just makes a click sound and relocks and blacks the screen. The first time resolved itself. Not sure if a reboot will help (probably so), but wondering if anyone has seen this or has any suggestions.
Click to expand...
Click to collapse
Is there any magnet near the N7? (if you have case, maybe the it is not working to well, most of the case is not prepared for daily use )
Ábel
Does the screen turn on and everything looks fine, but there is no touch response at all? Do the hard buttons prompt the menu's like power down and volume control but there is absolutely no touch input? I am asking these questions because if it is doing this you are having the same issue as me, I had been working on this issue for a solid month with absolutely no luck and the issue kept getting more frequent.I have re-flashed stock Google images both 4.1 and 4.2 with absolutely no luck. After the clean installs I did not root it I left the it completely stock and the issue is still there, also I thought it may have been my Poetic magnet case, well i took it out of the case and it still does it. I even removed my $20.00 dollar Steinheil Ultra Crystal Screen Protector thinking that may have something to do with it but that's not the issue. After every reboot it will work fine, so I was completely frustrated and could not find that many people on line with this issue. I finally had to send mine back to ASUS and they stated it was a screen assembly issue and they could replicate the problem, well I got it back last week and five minutes after booting it up the issue is still there so needless to say I have to RMA it again. What really bugs me is the Nexus 7 worked fine for two months not one problem then, I left it in a cabinet for 2 days without touching it and that's when the issue started and it has just gotten worse.
I apologize for the long story if this is not your issue but I just wanted to save you a lot of hassle if it is.
My issue isn't as complicated, fortunately for me. The screen is black (even though cover, with magnet, is open). I hit the power button once to get the screen to light up and slide the unlock. It looks normal but only flashes for an instant, then makes the click and the screen goes black again.
It self resolved again, so I actually am suspecting that it could be that when the case is folder over, the magnet may possibly be causing this. So thanks for that suggestion. Next time it happens I'll be looking specifically for that to see if I can narrow it down.
I assume bricked is the right term. And I'm pleading for some help here on what I can try before I call Google Support again.
Here is the quick run down: Bought 2 Nexus 6P, (Gray - Me), (White - Wife). Wife bricks her phone in 15 days, screen seems to work when held at different angles, can't seem to get it to stay on permanently, acts almost like an old VCR where it will partially draw the screen horizontally. Almost like a loose connector. It only stays on for milliseconds at a time, not long enough to factory reset or do anything remotely useful. Holding power for 8 seconds doesn't help. Holding power and both volumes does not help. Just to clarify, device is running, screen is black. Not a boot issue per say as a screen issue. Could previously hear her get alerts, can't right now (only see a battery icon). Since the screen is the main issue, I'm flailing in the dark as to where I am at any given point in time.
I assume how she uses the device because mine has been perfect and I can't seem to find a vocal crowd with this issue. However, after she bricks hers, she uses mine for an entire week and doesn't have any problems. Google support is extremely helpful and sends out an entire new device. I set it up and restore the apps, within 3 days (Friday -> Sunday) she has the exact same issue again - bricked. Now I'm completely flabbergasted. This device is still spotless, she has barely used it, it hasn't hit a surface hard, hasn't even been sneezed on. I can't even begin to stress how short a time period this is for a device to brick in. I can't help but feel this is a software app and the restore brought over the delinquent app. However, how come I can't reset the device and get back to a clean slate? Can anyone give me a trick?
Please, please help. She wants me to switch back to Verizon because of these device issues. However, even with 2 people, we are saving a ton on Project Fi and I really need this to work. Everything else has been a joy.
So I got it working. But I have a few questions...
Process:
1. Connected it to charger
2. Held power and both volume connectors
3. Held power again
4. Did both of these actions for upwards of 30 seconds at a time hoping for some response from the device.
5. Put it down on the table to write my forum post (still charging).
6. Battery image came on and off the screen randomly
7. Picked it up and held power one last time and it started booting normally.
I'm not sure which sequence of events led to what and I'd really love to know how to reliably reset it in the future. If this is the case then it means it was a software issue all along that persisted over several reboots.
Additionally, I'm frantically pulling software off of her phone - Elmo Calls, Sesame Go, Snapfish, Pinterest, etc. Fearing that one of these apps that I don't run on my device could be causing this. Is there any way to troubleshoot the software itself and see what device could have had access to the screen power and perhaps been powering the screen off as soon as I attempted to power it on (causing a flicker)?
Thanks.
your experience is really unusual you bought 2 phones but the one you are using does not have problems but your wife has, you switched phone then the problem occurs there is a chance a program is causing it as you already received a new one and it still occurring try to let her use the phone with the same software you are using and avoid which you dont use see if there is any progress.
Did you try factory resetting either phone?
Sounds like a software issue if they both had the exact same issue.
does she have some kind of serious strong magnet in her body or purse? haha
Soulfly3 said:
does she have some kind of serious strong magnet in her body or purse? haha
Click to expand...
Click to collapse
That's what I was going to say. Seems consistent to what a strong magnet would do to a screen. My next guess was a rogue app.
No magnets, nothing crazy. It started happening again yesterday a few hours after fixing it, I've hard wiped the device and bypassed the restore. Only updated the base applications and it is sitting on a charger - waiting to see if it will happen again.
Get a new wife?
VerucaSalt said:
Get a new wife?
Click to expand...
Click to collapse
Or, as OP seems to like to get things in 2, get 2 new wives so that if you brick one, you still have one left without having to wait for RMA.
All jokes aside, is there any specific oddities in how your wife uses phones (Does she work at a metal scrapyard with a big ass magnet? Okay, I promise, last one.) Or you could be extremely unlucky to have bought a defective unit, which was replaced by another defective unit.
To reliably reset the 6P you just hold the power button until the phone vibrates as it starts to boot again. Did the screen flake out as it booted up too?
ttminh1997 said:
Or, as OP seems to like to get things in 2, get 2 new wives so that if you brick one, you still have one left without having to wait for RMA.
All jokes aside, is there any specific oddities in how your wife uses phones (Does she work at a metal scrapyard with a big ass magnet? Okay, I promise, last one.) Or you could be extremely unlucky to have bought a defective unit, which was replaced by another defective unit.
Click to expand...
Click to collapse
Although these posts are funny as hell, honestly you would be surprised how many common every day things you come into contact with that can wipe data right off any storage medium. Although its definitely a possibility that you received a crap refurb phone, when you get the next RMA I would take some time to monitor your wife's daily routine with her cell (not her tinder activities), she might just be placing it near/on something that is wiping the phone or corrupting the data. Could also be a really junk app, but google is pretty good about keeping them out of the play store the best they can.
dl200010 said:
To reliably reset the 6P you just hold the power button until the phone vibrates as it starts to boot again. Did the screen flake out as it booted up too?
Click to expand...
Click to collapse
Yea, it was flaking out on the 8 second hold reboot - I performed it dozens of times without getting my screen back. What works reliably for me is to hold power and both volumes and then hit power again once the diagnostic screen shows up (whether I can actually see it or not). The reboot off of the diagnostic screen seems to bring the phone back to life consistently.
She is using the phone w/ just the base apps from yesterday - I told her to try breaking it without loading new apps - will see how this plays out today.
jaaaaaaaaf said:
Yea, it was flaking out on the 8 second hold reboot - I performed it dozens of times without getting my screen back. What works reliably for me is to hold power and both volumes and then hit power again once the diagnostic screen shows up (whether I can actually see it or not). The reboot off of the diagnostic screen seems to bring the phone back to life consistently.
She is using the phone w/ just the base apps from yesterday - I told her to try breaking it without loading new apps - will see how this plays out today.
Click to expand...
Click to collapse
Was that diagnostic screen flaking out too? I suggest to get more aggressive and factory reset through recovery and than ONLY connect her google account to get her contacts. Run like that for about a week. Otherwise your other choice would be to unlock the bootloader and try a custom ROM. I would suggest Cyanogenmod, DLROM (mine), Pure Nexus Project, or even Noob Builds.
ttminh1997 said:
Or, as OP seems to like to get things in 2, get 2 new wives so that if you brick one, you still have one left without having to wait for RMA.
Click to expand...
Click to collapse
haaaaaaaa, very good
---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------
Soulfly3 said:
does she have some kind of serious strong magnet in her body or purse? haha
Click to expand...
Click to collapse
Was actually going to say this too, is there somewhere she goes or sits which has some kind of strong magnetic field? It's odd that it happened to one and then to the next one, unless they're just both from a faulty batch.
Suppose I will add a follow-up. Since I ripped all her software off the device it hasn't crashed once in the same fashion. So I mean, that is the conclusion. I'd love to say I knew how to dive deep enough into Android to pinpoint exactly which app had such incredibly disruptive and adverse affects (far worse than complete OS crashes). But I don't know Android well enough. Google has the original phone. It definitely seems like an app should not have been able to take over the display so completely.
I'm going to move forward and have my wife install more of her apps. Just wanted to shoot an update out in case I don't revisit this. Thanks everyone who posted.
Maybe a combo of rogue (rouge?) apps? I mean some apps do have the ability to draw over screen, so that might have caused whatever problem you had.
And OP, don't leave us