Screen issue - rooted NST running ADW - Nook Touch General

I have an issue with the screen of my Nook simple touch. The refresh rate of my screen went down a small amount, and there is this large area of the screen where the black parts of the screen are not showing up. I will attach pictures. It is most visible when reading and when in the app drawer. This started when I began to use a custom background image for the home screen and the lock screen, but I am sure this is a hardware issue. Should I attempt to hide all traces of my root and go and attempt to return it? I have had this for about 3 weeks, so it is still under warranty.
Thanks!
Attached

Try rebooting your Nook. That may or may not do anything.

That does look pretty horrid. Almost looks like a finger run from bottom left-ish up the center. Does it start out clear, then degrade to this, or is it always this bad? Is it OK in the reader and the B&N home screen?
Keep in mind, anything not written by B&N probably doesn't refresh as often as it should for a clear display. Next time this happens, force a refresh by pressing the 'n' (shortcut menu) hard button twice. That can help if the display gradually degrades.

Did you find a solution?
I had the same problem too. Only the bottom left corner is working.
Attached the screensaver page.

brendan10211 said:
This started when I began to use a custom background image for the home screen and the lock screen, but I am sure this is a hardware issue.
Click to expand...
Click to collapse
Out of curiosity - could you post your custom background image too?
Does it resemble traces on second image you posted?

Thanks for all the response! Once I get to a computer I will respond to this.
ApokrifX:

ApokrifX said:
Out of curiosity - could you post your custom background image too?
Does it resemble traces on second image you posted?
Click to expand...
Click to collapse
I've never heard about "Stuck Pixels/Screen Burn" on E-Ink yet, but that's how it looks like...
But than we should all see them, because it's not that many screensaver images.
I'm

Ok. I think I figured out what went wrong.
During charging, my battery failed and overheated. This caused the battery to be stupid and overheat whenever it is charging, or for some odd reason, not in use for a period of time. The way to fix my issue is restart it 10 or 20 times, and let it sit outside (while it is cold, otherwise put it in your fridge) for about 10 minutes.
My question is:
Is there any way to replace the battery of my Nook? Or is it easier to hide all traces of root and take it back to Barnes and Noble? (I bought it 3 weeks ago)

brendan10211 said:
Ok. I think I figured out what went wrong.
During charging, my battery failed and overheated. This caused the battery to be stupid and overheat whenever it is charging, or for some odd reason, not in use for a period of time. The way to fix my issue is restart it 10 or 20 times, and let it sit outside (while it is cold, otherwise put it in your fridge) for about 10 minutes.
My question is:
Is there any way to replace the battery of my Nook? Or is it easier to hide all traces of root and take it back to Barnes and Noble? (I bought it 3 weeks ago)
Click to expand...
Click to collapse
No doubt: Reset, Restore and Return

brendan10211 said:
The way to fix my issue is restart it 10 or 20 times, and let it sit outside (while it is cold, otherwise put it in your fridge) for about 10 minutes.
Click to expand...
Click to collapse
Oh… AFAIK, these types of battery lose it capacity if exposed to negative temperatures (in Celsius, below water freezing point)
brendan10211 said:
My question is:
Is there any way to replace the battery of my Nook? Or is it easier to hide all traces of root and take it back to Barnes and Noble? (I bought it 3 weeks ago)
Click to expand...
Click to collapse
AFAIR, it’s two weeks unless you bought a protection plan...
I might be mistaken (both times). Please somebody correct, if I’m wrong…

Related

Help With 8525!?!?!?!

So Yesterday for no reason at all my 8525's screen went white. i thought it had frozen or some thing but it didn't snap out of it. I pressed the ok button on the side and could hear noise. I decided to restart. Nothing. Did this like 7 times. Finally I let it sit without the battery for like an hour. I worked but the colors were all messed up. Reset and it worked fine. So i set my alarm went to sleep and woke this morning to an email and a white screen. Turning it on and off a couple of times did it and I was already frustrated.
Then I read on a forum about Activesync automatically opening throughout the day to try and connect. So I tweaked that to manual connections. Still the same. So I decided to take advantage of the warranty but I needed to set back my rom b/c as you already know, it voids it. Also thinking that re-flashing might get rid of whatever it was failing in. No, still the same, and now worse. As or an hour ago, my navigation pad doesn't work either. It actually works for about a second when I turn it on and then after I press anything on the pad or surrounding buttons, it's gone.
I really would like to fix it myself at least for now and use the warranty exchange at about 11 months but if theres nothing I can do, I guess I can go get a new one. Also, I don't know if it has anything to do with it, but I downloaded Google Maps to my phone yesterday on the road (through 3G) and that was the only new program installed( I think it mightve been this).
Has this happened to anyone else?
Any help would be much appreciated. I hope I explained enough for anyone to respond. Thank you in advance to anyone with anything really.
Actually if you do a search under white screen you'll find many entries. Any attempt to fix yourself will void the warranty. If you are lucky it may only be the d-pad connector that is loose. This it is possible to check yourself but if have a warranty then I suggesting using it.
Otherwise see the link to my site in my signature for dismantling and service manual guides.
Mike
Thanks. You know I think I will take advantage of the warranty sometime this week. I don't know what happened. But I'm to update my situation. It now seems as though my directional pad seems to be the problem. it glitches on and off and using it sometimes creates the fade-out to white screen. I have to let it go to standby on its own to get my screen back or play around turning it on and off for a bit.
Also, once i re-installed me ATT rom with no applications, my screen seems to be off. I have a 1/32th sliver of the bottom of the screen at the top of my touchscreen. Even in landscape it shows my scroll bar and everything. I didn't even drop it but it is now slightly skewed down. Any input on this?
I also found this website talking about the same problem having with and unorthodox solution (which I tried to no avail). Here's the link if anyone want to check this out. http://www.htcwiki.com/page/AT&T+8525+Display+issues:+Display+is+dim,+blank,+white,+has+lines,+etc.?t=anon
Anyways, I'm gonna call ATT about this see if they can help but I think I will replace, I just didn't want to so soon.
Thanks again for the quick answer.
ckent03 said:
Thanks. You know I think I will take advantage of the warranty sometime this week. I don't know what happened. But I'm to update my situation. It now seems as though my directional pad seems to be the problem. it glitches on and off and using it sometimes creates the fade-out to white screen. I have to let it go to standby on its own to get my screen back or play around turning it on and off for a bit.
Also, once i re-installed me ATT rom with no applications, my screen seems to be off. I have a 1/32th sliver of the bottom of the screen at the top of my touchscreen. Even in landscape it shows my scroll bar and everything. I didn't even drop it but it is now slightly skewed down. Any input on this?
I also found this website talking about the same problem having with and unorthodox solution (which I tried to no avail). Here's the link if anyone want to check this out. http://www.htcwiki.com/page/AT&T+8525+Display+issues:+Display+is+dim,+blank,+white,+has+lines,+etc.?t=anon
Anyways, I'm gonna call ATT about this see if they can help but I think I will replace, I just didn't want to so soon.
Thanks again for the quick answer.
Click to expand...
Click to collapse
Everything they suggest on that site you have tried I guess, the soft and hard resets etc.
I agree with you about the d-pad (directional buttons). Those with this problem often report that the d-pad or it's connector are re;lated to this issue.
Pleased you have chosen the warranty route. You see evn if you opened it up, it can work for a short while and then return again. Also push hard for replacement not repair. They may do this automatically but if not try to persuade them. The reason is that quite a few folks have reported that even after an HTC repair the problem can come back. Actually I think there may be more than one physical cause of this issue and sorting one thing does not mean it won't come back via another route.
The good news is, if you get a good one as I did on the second attempt, I never had white screen or alignment issues - despite heavy use.
Mike
Once again, thank you Mike for all your input. I will be issuing an order for replacement instead of repair. Being at work all day today I've seen that it hasn't "whited' out, if you will, but has actually kept working. Ever so often the d-pad goes but comes back in a few seconds. It may be due to the WM6 i had on it so for now i will keep the original ATT upgrade of WM5 and try to hold off on the warranty as long as I can before it expires. That way I can enjoy a healthy new 8525 longer.
For now I will keep looking around in these forums and see if there ever is a solid solution. Thanks again, and good luck with all.
CKent

Black Shroud of Death

FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then it goes to a black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. Playing around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried downgrading to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. laying around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried going down to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
Sorry, this post isn't going to help, but I literally laughed out loud when I saw
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Click to expand...
Click to collapse
in the preview of the post. Lol
Maybe I should delete my original Karma-Killing post as a start.
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
a.mcdear said:
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
Click to expand...
Click to collapse
It might not be software but I can see the recovery screen so I have some reasons to believe it could still be software. Unfortunately, if I try to RMA, they're going to say that I voided the warranty....because I probably did by opening the case AND running a cooked ROM. So, they'll fix it but as a service. I'm not sure it would be worth the cost.
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
yanbo2012 said:
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
Click to expand...
Click to collapse
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Skyeclad said:
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Click to expand...
Click to collapse
Yea, you screwed up by opening it. You might as well upgrade if all else fails. I'd hold off on another transformer for as long as I can though if I were you...already hearing about minor defects in tf300s such as light bleeding.
Then there's always the...iPad...but make sure you update if you get one! Jailbreak that MF first and then you'd be good to go. My dad wants me to jailbreak his iPad 2, but it doesn't help that he's "update happy"
Skyeclad said:
I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
farsight73 said:
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
Click to expand...
Click to collapse
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Skyeclad said:
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Click to expand...
Click to collapse
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
1) NVflash works on B60 and below.. check yours
2) Put it in a freezer for a night
3) Dissemble again and see if anything disconnected or loose since the last time you open it.
4) Smell it and see if anything like burn smell around the motherboard(this could be over voltage from a weak components).
.
.
.
.
.
If all above still yielled the same result..
5) Check and see if your TF101 could survive 2 storey height drop..
Good Luck..
farsight73 said:
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
...
2) Put it in a freezer for a night
...
Good Luck..
Click to expand...
Click to collapse
A lot of LCD screens can be damaged by freezing, unless you know that the TF is safe I would not freeze it.
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Skyeclad said:
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Click to expand...
Click to collapse
Lol, didn't you already take it apart before?
I2IEAILiiTY said:
Lol, didn't you already take it apart before?
Click to expand...
Click to collapse
Yes, but at the time I was looking for a cable that I could loosen, now I'm looking for a cable to tighten. Fml, yes it sounds stupid but I'm at the point where I need to decide if a repair or replacement is the next step. I'm not thrilled with anything out there.
Almost exactly the same problem here...
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
I had the same problem of the backlight being on but no video. It worked over the hdmi but that was it. I had to send in my unit via a RMA to get it fixed.
Thankfully it was under warranty so they fixed it. Did you drop your unit?
MeLikes said:
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
Click to expand...
Click to collapse
Just out of curiosity, why not nvflash your way back to stock? I did because I couldn't find my HDMI mini cable. I haven't opened my tablet again. I'm going to try to RMA it.
try to nvflash stock rom and start over? that would your best chance....
Sent from my Transformer TF101 using xda premium
Well first of all i don't know how to use NVflash, and secondly i have a B70 transformer so i don't know if it will work. Also i need to flash the stock Taiwan firmware because that's the original firmware that came with it and i can't find instructions for that. Just wondering though does flashing the stock rom using NVflash also install the stock recovery?

Nexus S 4G Hardware failing?

Had this phone since launch and I think she's finally ready to go..
Your thoughts
First issue: Woke up this morning to my phone stuck in horizontal mode (CM9).. No amount of reboots, cache clearing, display rotation setting playing with would stop it. It would reboot straight to landscape mode.
Second issue: Tried pulling the battery.. When inserting the battery the phone booted right up without me even having to hit power.
Third issue: I removed the battery again, this time for longer and now when I insert the battery the animated charging icon appears (without being on external power)
Fourth issue: When the phone was powered up it would randomly not recognize it was on external power even when plugged in.
Fifth issue: Reading the writing on the wall I did a quick unroot return to stock and locked.. After this rotation works fine again, it seems to charge but if I pull the battery and insert it, it will still show the white animated charging battery icon for about 5 seconds. I can even press the power button quickly to bring it up on demand like it's really on external power when it isn't.
You can remove the second "issue"
It happens on most phones... normally when u pull the battery and quickly put it back in
Sent from my Nexus S using xda app-developers app
qaz2453 said:
You can remove the second "issue"
It happens on most phones... normally when u pull the battery and quickly put it back in
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Yeah.. I had it down to that myself.
Took it to Sprint.. He tried blaming it on my battery (because it would take 10-20 seconds to even acknowledge it was charging after plugging it in)
So, I demonstrated how I can make it "charge" without being connected to power by making the powered down charging icon appear when it was unplugged. He laugh with a bewildered look on his face and just decided he'd send me a reconditioned (he said new but the box serial number starts with "RECD") and also a new battery. The whole day before I received my replacement my old phone was getting worse and worse.. Random reboots, and odd thin vertical lines when on Automatic backlight in bright sun..
New phone is working as it should now.. I can't complain. What's it been? 9 months since release? And this is the first time something went wrong with it and Sprint had a new phone at my door in 24hrs. Love good, quick service.
Take cm9 off and return to stock.
See if it functions normally.
This just sounds like a case of user error to me.
If you don't wanna go back to stock.....restore a known good backup....wipe and reflash your current rom.....
albundy2010 said:
Take cm9 off and return to stock.
See if it functions normally.
This just sounds like a case of user error to me.
If you don't wanna go back to stock.....restore a known good backup....wipe and reflash your current rom.....
Click to expand...
Click to collapse
I did return it to fully unrooted 100% OTA stock. You think I took a phone to Sprint to have diagnostics run on it rooted and with CM9 on it? :laugh: It wasn't user error.
I don't know ya by name so.....
If you browse these forums often you see all kinds of dumb things. I just usually assume the worst to start.
albundy2010 said:
I don't know ya by name so.....
If you browse these forums often you see all kinds of dumb things. I just usually assume the worst to start.
Click to expand...
Click to collapse
I get where you are coming from.. Name's Bill btw.. Yeah, I've seen plenty of facepalming stuff on XDA my few years here so I guess a lot just assume the stupid and work their way up to common sense. :laugh::good:

20 days, 2 bricked Nexus 6P

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

TMobile S8 works fine, except the screen won't turn on

My brothers TMobile S8 screen randomly stopped working. It has no signs of damage anywhere as well. Weirdly, I managed to get the screen to go on one time by pressing some button combos to try to follow a guide to get it into recovery to factory reset it. Upon the phone booting, the battery had 3% and when I went to show him, it was dead. Now after letting it charge, the screen does not work once again and I can't seem to get it to come on in the same way it did before, the bright blue recovery screen.
Is there any software I can use to just attach the phone to it and factory reset it? I mean, I've seen bad phone screens before that have still had images show up on them, even if heavily damaged physically or it no longer responding to touch and showing dim lights. But this one simply doesn't turn on, except the one random time it did, and it was perfectly fine, showed no sign of damage. Any thoughts would be greatly helpful
Is the battery known to be good?
If not replace it. The system will not boot if there's not enough current. It takes a fair amount of power to boot up. A charger can't provide enough to do so...
It boots up fine, I can hear the initial TMobile boot audio as well as the notification sound the phone makes when it gets to the lock screen. I also had it stop charging @80% not too long after buying the phone on release, with some custom ROM I installed. Ofc its a possibility its battery related, since I can't see anything on it, but it was taken care than the average person I am sure
With a custom rom all bets are off. Makes troubleshooting much harder. Possible rootkit.
Firmware and malware aside if it's booting but no display, possible loose ribbon connector, failed display or mobo. That's assuming the battery is good...
Well I did disable/uninstall Superuser from the phone, and I used it for a couple years before giving it to my brother to use. That is a good point about the cable, I will search for images, maybe I can squeeze a few spots to just see what happens
moccor said:
Well I did disable/uninstall Superuser from the phone, and I used it for a couple years before giving it to my brother to use. That is a good point about the cable, I will search for images, maybe I can squeeze a few spots to just see what happens
Click to expand...
Click to collapse
Sometimes just reseting a connector is all it takes. Those are low voltage lines and a perfect contact is needed.
If the battery is more then 2-3 yo it's probably at the end of its usable service life.
Thanks for the input, I will open it up if nothing else works and I will report back if it helps

Categories

Resources