Bare with me I know this sounds weird. My 2013 Wifi N7 worked well for quite a while, then would intermittently get extremely slow to the point of being unusable. It was previously unlocked and rooted so I reflashed the factory image a few times but it would still have issues. I was starting to think the flash memory in it was bad.
Just today I reflashed 5.1.1 (was on 5.0.1 which was the last time I used it). Upon first boot the startup animation started going extremely slow, occasionally speed up to normal speed, stop and appear to freeze then start moving slowly again. The animation continued to speed up, slow down and freeze. After about 10 minutes it still had not not gotten to the initial Android sign in screen.
I picked it up and slightly flexed it from 2 opposite corners and suddenly the boot animation starting playing at full speed. I stopped flexing it and it slowed to a crawl again. I did this a few times and each time slightly flexing it caused it to work correctly. I held it in the flexed position and the boot animation continued to display at normal speed and it finally completely booted up. Once it booted it asked to connect to Wifi and again was super slow and unresponsive after I let go of the corners to touch the screen. I then flexed it back and forth a little more forcefully and it has continued to work normally since then. I have played with it a little and rebooted a few times with no issues.
I am assuming there is something loose internally that flexing somehow fixes. Does anyone have any idea what would be causing this? I don't have a problem opening it up and trying to permanently fix whatever is causing the issue but I'd like to know the cause before I attempt a repair.
Fuzzy_Dunlop said:
Bare with me I know this sounds weird. My 2013 Wifi N7 worked well for quite a while, then would intermittently get extremely slow to the point of being unusable. It was previously unlocked and rooted so I reflashed the factory image a few times but it would still have issues. I was starting to think the flash memory in it was bad.
Just today I reflashed 5.1.1 (was on 5.0.1 which was the last time I used it). Upon first boot the startup animation started going extremely slow, occasionally speed up to normal speed, stop and appear to freeze then start moving slowly again. The animation continued to speed up, slow down and freeze. After about 10 minutes it still had not not gotten to the initial Android sign in screen.
I picked it up and slightly flexed it from 2 opposite corners and suddenly the boot animation starting playing at full speed. I stopped flexing it and it slowed to a crawl again. I did this a few times and each time slightly flexing it caused it to work correctly. I held it in the flexed position and the boot animation continued to display at normal speed and it finally completely booted up. Once it booted it asked to connect to Wifi and again was super slow and unresponsive after I let go of the corners to touch the screen. I then flexed it back and forth a little more forcefully and it has continued to work normally since then. I have played with it a little and rebooted a few times with no issues.
I am assuming there is something loose internally that flexing somehow fixes. Does anyone have any idea what would be causing this? I don't have a problem opening it up and trying to permanently fix whatever is causing the issue but I'd like to know the cause before I attempt a repair.
Click to expand...
Click to collapse
Hi,
I had the same issue like you, do you get what was wrong with your Nexus?
osi666 said:
Hi,
I had the same issue like you, do you get what was wrong with your Nexus?
Click to expand...
Click to collapse
Unfortunately no. I ended up giving it away to someone else with a N7 that had a cracked screen so they could attempt to transplant the working screen from my unit.
Related
Hi folks, I've lurked here for quite a while and gotten some invaluable info; so first off thanks for all of the contributions from the gurus here!
Now, I have a pretty strange issue that I haven't been able to find an answer on anywhere. I'm hoping that someone can help me sort this.
The background story:
My wife has a MyTouch 3G Slide that I bought for her back in July. Last week she managed to drop it in some water. It DID NOT get fully submerged since the water was very shallow. However, it did get a slight amount of intrusion. She pulled the battery in a relatively quick amount of time and we let it sit in a bowl of rice to dry out for a couple days.
The current deal:
When I felt the phone was sufficiently dried after a few days, I fired it up. It took a very long time to get out of the MyTouch splash screen and loaded noticeably slower than normal. Once in, the phone functioned perfectly normal. Absolutely no issues at all with any functionality once you get past the security pattern.
However, whenever you put the phone to sleep, it does some funky stuff. The screen goes black for a second and then comes back on, ready for you to swipe down and then enter the security pattern again. Then it will go black again. Then it comes back on. It just continues to do this, never stopping. Sometimes it will go to the security pattern screen too.
So I figured this may have been some hardware issue since it was acting like someone was just repeatedly pressing the power button. First I wanted to try a simple reboot though. Upon rebooting, the phone would not get past the splash screen. It just froze there.
I pulled the phone apart to see if maybe there was some corrosion on the PCB from the water intrusion. Everything looked fine, but while I was in I did a little wipe-down with some alcohol, then I put it back together. After multiple attempts, I was able to get it to boot again. But the boot process was still VERY slow. Occasionally, it would boot into safe mode as well. But when it booted normally, everything would always function great once logged into the phone. This convinced me that it wasn't a hardware problem since the phone would not cut into sleep mode or anything when logged in. It worked perfectly fine. So I figured that maybe there was some sort of corruption that occurred in the software.
So I tried a hard reset. Didn't fix it.
Then I figured that maybe I needed to do a reflash. So I rooted the phone since the water plunge voided the warranty anyways. Once rooted, I flashed TeamFenix 1.7.1 successfully.
But the phone still only fully boots intermittently, and the boot process is still slow. It also has the same problem in sleep mode which is killing the battery fast since the screen is pretty much constantly on. But once in, the flashed ROM works perfectly just like the stock ROM.
Video of the condition:
Since I'm new, I'm not allowed to put any links in my post. But if you type in the string below after the YouTube url, you'll see a quick video I posted of the condition.
watch?v=dX55URtaRHo
So it seems that there is some crazy issue only upon bootup and when the phone is put to sleep. Can anything be done to fix this? Is there a way to locate and fix corrupted software? Any and all help is appreciated!
Sorry for the self bump. Any devs out there have any suggestions? I gotta get this thing sorted.
If its happening on both stock and teamfenix, I'm pretty sure it's a hardware issue. Flashing a rom completely replaces the software, so it doesn't sound like its that.
Sent from my T-Mobile myTouch 3G Slide using XDA App
It actually seems like a problem in the power button. Did you check the contacts for the power button? Repeatedly pressing the power button will first lock it initially and dim the screen. Press again, then it gives you the chance to unlock. Press again and it goes back to sleep. Wash rinse repeat...
Yes, I understand. But if it were an issue with the power button, when you logged into the phone, it would randomly put itself to sleep. It doesn't do that, it functions perfectly normal with no errors whatsoever when you are logged into the phone. This problem is only exhibited in sleep mode which would rule out a hardware issue with the power button.
I just recently got a T217S from Sprint, had it about 2 weeks, running all stock, 4.42 Android. Ran fine the first week, then I noticed that the screen would start to flicker. Doesn't change colors, just flickers. Playing with the brightness can sometimes cause it to stop temporarily, but it starts again almost immediately. The level of brightness doesn't make a difference, neither does any applications I'm running. I've rebooted it into safe mode and without even touching it, it started flickering less than 30 seconds after booting. I've google the heck out of this and it doesn't seem to be a hardware issue, but an Android problem. I would like to avoid a factor reset if I can, especially until I get solid proof that it would FIX the problem. So far, no one can even tell me WHY it's doing it.
HELP???
Hello everyone, I just recently got a G3 and it was working fine for the 1st 2 days, no issues. I was sending a text to a friend earlier today and after it sent, it completely froze. After doing a soft reset it took forever to boot up. Once it booted up, it seemed to be fine. about an hour of operation, the screen looked as if it was freezing because it wasn't recognizing any of my touches. i decide to flip the phone sideways to see if it was actually frozen but it changed to landscape just fine. Sometimes it comes back to life then goes off again shortly after, and other times, i have to soft reset. I've tried the following to no avail.
Took the phone apart and cleaned both connectors.
Re-flashing the rom.
Trying 4 other roms.
Returned to lollipop stock.
I can't figure this out for the life to me and worked my ass of to be able to buy this phone. Any help would be appreciated as I can't afford to spend any more money on it!
I also have this issue, it's been ongoing for a few weeks. There will be short periods where it can work just fine, then it just freezes up and does not register any inputs. The content on the screen continues to run as if nothing happened (videos and games keep playing). Turning the screen off, waiting a couple minutes, then turning it on can sometimes give me another minute of use until it freezes up again. Also of note, when the screen is unresponsive and I press the power, it will dim to very low levels for a few seconds before going fully black. When the screen is being responsive and I press the power, it goes straight to black, as is normal and expected. From my testing, I've concluded:
1. This issue is not app dependent. It can occur at any time, and is not caused by alarms or overlays, such as blue light filters.
2. The issue is not from the specific battery I use. I've switched out between multiple batteries and used different chargers, none seem to affect the frequency of freezes.
3. Temperature may have something to do with this. When waking the phone after it's been sitting out in the cold, there seems to be a higher likelihood that it will be unresponsive. This is not always the case, which makes concluding that the issue is hardware related difficult, but some correlation seems to exist.
4. This issue started occurring shortly before I began having the popular "SIM Card Removed" issue, which I've yet to resolve (though can sometimes get the SIM card to work)
I am running stock 6.0 D85030p AT&T. I will post here again if I figure something out, but I have been trying for weeks without much success.
Hello everyon everyone.
I have the SM-P600 version, everything was good until the beginning of the week when touchpad began to go off without reason, and completely random.
I first reinstalled several official ROMs from the most recent to the oldest, with no significant improvement
Then i rooted and tried Lineage, it looked good for a while, but in the end same problem.
Please note, when the tablet begins to mess, the reboots are occuring more and more often and after a while it turns in a loop and im not even able to switch it off.
Samsung logo display, black screen, logo, black screen, etc ...
I think rather for a battery-side problem, if some people have faced similar problem, I'm taking help.
Do you know if by chance we can use the tablet without battery to test this theory?
Thank you in advance for any answers.
jb1207 said:
Hello everyon everyone.
I have the SM-P600 version, everything was good until the beginning of the week when touchpad began to go off without reason, and completely random.
I first reinstalled several official ROMs from the most recent to the oldest, with no significant improvement
Then i rooted and tried Lineage, it looked good for a while, but in the end same problem.
Please note, when the tablet begins to mess, the reboots are occuring more and more often and after a while it turns in a loop and im not even able to switch it off.
Samsung logo display, black screen, logo, black screen, etc ...
I think rather for a battery-side problem, if some people have faced similar problem, I'm taking help.
Do you know if by chance we can use the tablet without battery to test this theory?
Thank you in advance for any answers.
Click to expand...
Click to collapse
I think I'd be taking a close look at the physical power button. Seems to me that if it had gone flakey it could cause something like this.
marshallartsoz said:
I think I'd be taking a close look at the physical power button. Seems to me that if it had gone flakey it could cause something like this.
Click to expand...
Click to collapse
Hello and thanks for you answer,
Just to precise i never faced this issue while flashing an official or custom ROM, dont know if it is just luck or it can help in anything
Anyway ill try to check it the power button just in case
It's weird I just started having this exact problem myself. One morning I unplugged it and it had shut itself down overnight. Since then it randomly reboots. Sometimes I can get 20/30 minutes out of it, but once it starts, it can get into multiple reboots with the only way to stop it is to plug in the charger. I tried wiping cashe/dalvic (no help). Nothing was recently changed (including apps). Tried resoldering battery connector (battery was replaced a year or so ago with OEM Sammy). The P600 is rooted with TWRP installed, but no custom ROM. Usually the reboots start while I'm doing something (surfing, email, etc.), but I don't think it will do it while sleeping. I'm considering the power button, but I don't see this exact problem anywhere else, but this post. Any ideas?
OK. My tablet has taken a turn for the worse. Now it is stuck in a continuous boot loop. I tried the power switch, no help. I tried booting into TWRP, and it went back into rebooting before I could do anything. Strange thing is I can put it into download mode indefinitely without it rebooting. Should I ODIN back to stock? I tried the resoldering of the battery connection earlier. Any other ideas?
There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Gnatcatcher said:
There are similar threads but I think my problem is different from the others.
In the morning everything was fine for about an hour but once I left the house my phone froze out of nowhere. In the beginning It was still able to reboot into Android but always crashed shortly after and right now it's looping. I can still get into fastboot but recovery mode doesn't work, I just get back into the bootloop, probably because the phone crashes before it enters recovery mode (first google logo shows, then it crashes).
Sometimes when it crashes it produces really weird artifacts, which can cover most of the screen or are only a few pixels large, in different colors.
I found this guide which might help but I can't get into Recovery Mode anyway.
I read about the contacts getting lose, still gotta figure out if certain scenarios will allow it to boot.
Software is stock Android, on the latest update the Pixel XL received.
Update1: So after about 7 hours it finally booted to Android again, after taking of the case (cheap plastic one). And it does so consistently for some reason but sadly still crashes after a few minutes. Maybe it's heat related, the phone always got warm more easily with the case on.
I also just noticed that the phone restarts on it's own after crashing (and for some reason activates the night light) which could mean that it's trying to protect itself from damage.
Update2: Seems to be temperature related. I put it on a cold ice cube tray and since then it didn't turn itself off.
Considering the fact it restarts on it's own there could be some error logs, how could I retrieve those?
Update3: Higher tendency to boot when battery is low.
Click to expand...
Click to collapse
Maybe replace battery?
Hi there! I am not sure if your problem was fixed yet. But my Pixel XL died yesterday and did the same exact thing. It went into an infinire boot-loop, and after trying many times to power off and reboot, some weird artifacts appeared.
I think I messed up the phone, because at first the phone booted and then restarted, but now it just restarts and never ends....
EDIT: After some hours of rebooting, and more artifacts, the Pixel finally booted on android. Battery was at 4% so I guess that helped. It keeps rebooting from time to time, but at least I can copy my photos now haha.