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.
Related
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.
Hello!
Everything was working fine until my phone started acting up about 6 months ago. The screen began to become unresponsive, apps crashed when switching between them and random reboots occurred frequently. I thought back then it had to be software related, so I completed multiple factory resets, and completely removed everything on my phone. It became slightly more usable, but these crashed and random reboots still occurred.
Last week, my phone continued to reboot, but a new problem occurred-it no longer would turn on after the reboot. I tried plugging it into the wall, pressing the volume down + home + power to force bootloader mode, but it wouldn't turn on at all. The fix was I had to remove the entire case, take out the battery and put it back in the phone. After that it would turn on, but only for a few minutes before another random reboot occurred and I had to remove the entire battery again. My phone is now virtually useless as I cant before even the basic functions, calling and texting without it becoming unresponsive or shutting off and not turning on.
I narrowed it down to the eMMC chip. I am almost certain that is corrupt, because during some of the reboots it would fail and throw me into download mode with the error:
mmc0_read_fail
or something along those lines. My last attempt at recovering the phone was to the stock rom PE2 with a PIT file (I had created before I started flashing custom roms). Each time I would attempt to flash with ODIN it would result in a:
mmc0_write_fail
However, I was finally able to get the PIT and PE2 firmware to flash. Now I have a half-working phone that will randomly reboot still and in order to turn it back on, the battery has to be pulled out for a minimum of 15 seconds.
New Issue I just noticed: When the screen turns off when the phone is inactive, it won't turn on again after pressing the power or home buttons. Only solution to this is once again, pull battery and hope I boot into system again.
I am pretty sure there is no fix to this problem on the software side, but let me know if you have a suggestion! Thanks!
Same situation. This thing is a lemon!
Sounds like hardware failure.
Replaced the battery yet? My original didn't last fifteen months before it started shutting the phone down. It's the first thing I think of when someone reports having to pull the battery.
Are you checking battery capacity before the battery pull by plugging in when it shuts down? Mine showed 0%. Before the shutdown, it may have indicated as high as 30%. It gets worse.
You didn't mention capacity when plugged so I thought I'd ask.
Sent from my SM-N910P using Tapatalk
One of my note 4 had same issue. Its a hardware issue. I was able to get the phone working by using a heatgun on the motherboard to try and reflow the solder on the chips. The phone works like brand new after the heatgun but the phone would only work for like 3 or 4 days before crapping out again. Ultimately ended up buying a used motherboard on ebay with a clean esn and its working perfectly again.
My wife's Note 4 started the random reboot thing and screen being unresponsive thing last week. She said it randomly started after installing Snapchat, so she uninstalled it hoping that would fix it. It didnt. I put a new battery in it thinking the original was bad, but still same issues. Then did a factory reset but that didnt work. After a lot of searching I stumbled on to someone who mentioned downloading an app called Wakelock. I did and phone has been running smoothly for several days now.
I also recently did the most recent update hoping that would fix the issue, it didnt but during the install I did get one error of emmc read failure or something like that. May just order a used/new motherboard just in case.
Just be careful when swapping out the motherboard as it essentially is taking apart the whole phone including the removal of the LCD.
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,
This is what have happened:
I was browsing via Chrome, when phone froze. Well, no big deal. It went black, and I couldn't power it back on. I was on rehersal, so I left it on the table for an hour.
Came back to it, tried to power it on, and after 20sec or so of holding Power button, Google appeared. And it disapeared again.
And that is it.
I can access bootloader, and recovery.
From there I tried to flash fresh img, but my device is locked. Went the other way. I downloaded latest OTA and went to adb sideload, and it downloaded it all to phone, but same thing with booting. It stops.
Sometimes it even goes to those circle animations on booting, but than it freezes again, and turns off.
Any hope for my 2 years friend now
Thanks.
@Nuuq: by searching for 'brick' 'bootloop' you find for example this thread Hope, it helps.
Exact same thing happened to me this morning. I was playing Clash Royale, and it froze. Rebooted, and it just went to Google screen and nothing else. I let it sit for an hour, and it started to boot, but froze mid-boot-animation. I can get into bootloader and recovery, so I'm going to flash the Bootloop fix this afternoon and see if it fixes it.
Odd......
I thought this was a CPU bootloop issue, so I flashed the 4-core TWRP, wiped everything, and installed the stock OPR4.170623.006 system, vendor, and thne 4-core boot.img I found in the bootloop thread. I got a little farther, say 5 minutes instead of 5 seconds, but it was still crashing and bootlooping! I couldn't activate the phone, cuz it was rebooting while waiting for my 2-factor authentication text, and when I tried wiping it again, it was rebooting while in TWRP while re-flashing the system. The more I try to fix it, the worse it gets...
I may just give up on the phone, and contact Project Fi support to see if they'll give me a new one.
Same here guys...put inside the the fridge for about an hour and it started, just in time to save my photos on Google photo...but as soon as I start to use it, it freeze, turn off, no reboot. If I reboot, it freezes on circles Google animation...i can enter in bootloader and recovery too...any suggestion?
Same problem - merrily browsing -> crashed and now bootlooping - can get to the bootloader menu but can't get into recovery mode
Running Oreo 8.0
I flashed the 4-core TWRP, and it was crashing even in that. Last night, it sat for 3 hours on the activation page, and never froze, but anytime I try to use it, it freezes. It sometimes turns on, but most of the time it just crashes while booting.
I already use Google Photos, and my texts are synced through Fi hangouts, so I'm not worried about losing anything. I've wiped my phone and started over maybe a dozen times over the past year. Different ROMs, kernels, etc. I just want a working device.
I called Google, and they said nope. They want me to call LG, but my brother has had 2 bootlooping 5x, and LG didn't help with either of his. I doubt LG will help me here, cuz I bought it from the Google Store. I think I have 3 options:
1) pay to gave the CPU reflowed. If I went this route, I would want to upgrade to 3GB or 4GB of RAM at the same time. If I do this, I still have to deal with my battery only holding a 70% of it's charge, and not wanting to spend $50 on a 2 year old OEM batter.
2) Upgrade to a used Pixel. I'm sure with the Pixel 2 coming out, lots of people are going to be upgrading, and I'm sure there will be a bunch of used Pixels showing up. But, you're still buying a used phone that's been out for a year now...
3) Upgrade to the Android One Moto X4. The word "upgrade' is used loosely, as it's VERY similar to our 5Xs. Similar benchmarks, similar screens, similar primary cameras, almost the exact same dimensions, etc. It would be an upgrade with 3GB RAM, bigger storage, SD card slot, 2nd rear camera, better GPS, bigger battery, new (not used), and a few other minor tweaks. Con is that it's so new, there are no ROM/kernels for it yet
I think I just talked myself into a X4 while writing this. We'll see what the wife says.
it happen for me but me i can boot to bootloder but the phone become very slow i just escape from bootloop i turn it on and after 2 week he bootloop again now only fastboot no recovery and no system how i do
squelch41 said:
Same problem - merrily browsing -> crashed and now bootlooping - can get to the bootloader menu but can't get into recovery mode
Running Oreo 8.0
Click to expand...
Click to collapse
Hmm, putting it in the freezer gets it to boot but rapidly crashes again - looks like it is the hardware rather than software
So a few months back, my phone had bootloop like symptoms, but i was able to access it for a few seconds, and after that it started freezing up and restarting, until it "bootlooped". I could enter the power + volume down menu, but rarely in the recovery mode. I hat to keep the phone OFF a few minutes/hours. I've reset it and tried multiple OTA's at that time, no luck
Now, after a few months, i tried again, booted up the phone, set it up like a new phone, it worked for a few minutes, after that it started freezing up again. The battery was 15%, than 4% than 32% (after every restart)
Now, i managed to sideload the latest OTA, the phone is in the previous newly setup phase, and ifi leave it charging (via laptop usb) and lockscreen it took about 5-6 minutes before it started restarting, and again, the battery indicator started to show 5%, 18%, 46% and back down to 14% after the last restart.
i've seen some similar topics here, that said that after a battery change it was usable again, but with no RMA possibilities, and on a tight budget, i would not like to invest in a new battery and service, just for it to be some other hardware malfunction. So if there is anyone able to help, i would really appreciate it.
Thanks
Hey are you still around? I think this may be a issue caused by the emmc chip itself. I bought a pixel for $12 from a guy who was just trying to get rid of a phone (with almost same exact issues of yours). Some people are saying because power button is stuck but that's silly because power button works perfectly fine in bootloader mode.