So i have a weird problem with my note 2. For some reason the phone has no sound whatsoever and when i try to make a call or play sound the phone shuts off or freezes. Also when i turn the screen off after 20 seconds or so the phone will not turn on unless i pull battery and power on.
Started after i pulled the battery last week while phone was on went in to replace the vibrate motor. After i booted touch became super laggy, system kept crashing. And phone kept powering on then shutting off after full boot. Probably a dozen times. Ended up damaging my sd card in the process. I've re flashed a few roms and nothing really helps. When i'm in recovery the phone is fine. I've wiped everything a few times also. Currently on 4.3, I was running sky note F1 update 3. I've tried stock, meanbean and even slimkat 4.4.2 but no success. I swapped my board out into another note 2 to see if parts were defective and still have same issue. I havens flashed a bootloader yet though don't see how that is going to change anything. Anyone have some input or help with this would be great.
Thanks.
i was using my zf2 as usual. suddenly it became unresponsive. i locked my phone and kept it in the pocket.
It started heating like never before. It went on restarting again and again, and battery level was plummeting.
i simply did nothing and switched it off.
Later i switched it on, and the home and the recent apps buttons were not working.
no sound could be heard,
no phone calls can be heard,
factory reset is unfunctional.
Please help as to what do i do?
Try to flash the stock rom if you can access recovery, there are a lot of guides around, if it does not work send it in for service.
Hello all,
My Pixel XL randomly started resetting on its own and then gets stuck in a bootloop. It used to reset 1-3 times a day a do this (Its been going on about a week now), but the last couple of days its been doing this several times an hour. I can get it to stop the bootloop and finishing turning on by pressing the power button a bunch during the loop, but it will shortly reset and start the bootloop.
I can't even power my device off, because before it can finish powering down, it will reset into the bootloop. I have contacted Google, and they weren't much help. They said they can send me a new device, but it will be a week or two. Any suggestions on what I can do in the meantime to try and fix this? I've already done a factory reset and that did not help.
Thanks!
This keeps happening to me. Any luck finding a fix?
Same here. I updated to the latest patch a few days ago and now my Pixel (not Pixel XL) goes through bootloop a few times a day...
I've had similar issues with my Pixel XL recently. It started with a random reboot, after which it just ran really slowly, with apps telling me they weren't responding or the whole thing just freezing up. Shortly after that it went into a boot-loop (boot, input PIN to unlock, screen freezes, auto reboot, rinse/repeat).
For me, a factory reset would solve the issue for a couple of days then it was back to the same problems.
I returned mine to the shop this weekend, and they have sent it off for repair/replacement; in the meantime they've given me a basic Android loan-phone.
Sorry; I'd like to tell you I had a fix for this, but I just wanted to say that I too experienced this issue and simply took it back for replacement/repair. I guess it depends where you bought it (I got mine SIM-free from a shop in the UK) for them to offer something else to tie you over.
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
The last two times I allowed my phone to charge fully, the phone locked up (would not come on when the power button was pressed) and I had to do a soft reset (hold the power button for 30 seconds). This happened on two different chargers with two different cables (one of which is the factory set). Thus, the issue is almost certainly not hardware related.
There have been no changes to my phone, no newly installed apps, etc. There have been a number of app updates, including several Google/Android core apps, and I am wondering if one of those could be the problem. (After the first time the phone locked, I updated the kernel to the latest version, i.e., PQ3A.190801.022. Note also that the phone is rooted with Magisk.)
Has anyone else experienced this problem? If so, what did you do to resolve it? What can I do to try to figure out why this is happening?
groston said:
...What can I do to try to figure out why this is happening?
Click to expand...
Click to collapse
Try replicating it in safe mode to rule out 3rd party apps.
I'm having the same issue the last 2 weeks. I haven't updated any apps and I have auto updates off. No changes to my phone since the end of august and it just started doing this.
Were you able to figure out what was causing it? My issues occur using a 5W Qi charger. So it is definitely not cable/charger related.
Sorry to report, but I have no idea. Since having posted my question, my phone has been behaving properly.
I've got the same issue on 10. I put my phone on a pixel stand at night and when I wake up I have to do a soft reboot to get the screen to turn on. Reverted back to Pie and the issue went away. Flashed the Oct factory image for 10 including wiping data and the issue returned. Booted into safe mode last night. Woke up this morning and had to force a reboot to get the screen to turn on.
darkstar73 said:
I've got the same issue on 10. I put my phone on a pixel stand at night and when I wake up I have to do a soft reboot to get the screen to turn on. Reverted back to Pie and the issue went away. Flashed the Oct factory image for 10 including wiping data and the issue returned. Booted into safe mode last night. Woke up this morning and had to force a reboot to get the screen to turn on.
Click to expand...
Click to collapse
Weird. I'm still on 9 that was working fine and no update that I know of.
I confirmed the issue with both QI charging and cable charging on my phone.
I've taken to making sure my phone is charged before bed and just pulling it off the charger before going to sleep. Since my phone is also my alarm and having it go unresponsive is no good. Only looses about 3% battery overnight.
Well, not sure what happened but the day before yesterday my phone did it's usual lock up while charging requiring a reboot. Unusually after reboot if I logged on too fast it would immediately shutdown. But for some reason this time it took me 7-8 tries to get in. I haven't updated any apps, changed any modules in Magisk or anything. It just went to almost boot looping.
As soon as I got it stable I popped into Magisk and looked at what modules were there. I noticed I had added Substratum previously, to try and do a dark theme, but apparently I never removed or disabled it. I disabled all the modules and suddenly no more problems. Reboots without shutting down after log in and no longer locking up on the charger.
I removed two audio mods (audio compatibility patch and audio modification library), as well as substratum. Three of 5 mods I had downloaded.
I am currently only have Active Edge Mod and V4A legacy FX for mods and my phone is now working fine. If it changes I'll let you guys know.