I ran into a issue whereby the phone went into a boot loop. It's not a total shutdown, but a reboot as it came back within 10 seconds. I running Audible (in the background, not playing), Waze and broadcasting Periscope. After the first reboot, I stop using Periscope. The phone went into another reboot after I startup Waze. After 2 more reboot, I tried to do a graceful shutdown. The phone was stuck on shutting down for a couple of minutes (with the arrow circle stuck). I finally does power+volume down to do a full reboot. Afterward, I powered down another time and make sure comes back correctly.
Not sure if this is caused by too many apps running, the phone does appear to be warm.
The phone is unlocked straight from Google, rooted with Magisk.
dyingearth said:
I ran into a issue whereby the phone went into a boot loop. It's not a total shutdown, but a reboot as it came back within 10 seconds. I running Audible (in the background, not playing), Waze and broadcasting Periscope. After the first reboot, I stop using Periscope. The phone went into another reboot after I startup Waze. After 2 more reboot, I tried to do a graceful shutdown. The phone was stuck on shutting down for a couple of minutes (with the arrow circle stuck). I finally does power+volume down to do a full reboot. Afterward, I powered down another time and make sure comes back correctly.
Not sure if this is caused by too many apps running, the phone does appear to be warm.
The phone is unlocked straight from Google, rooted with Magisk.
Click to expand...
Click to collapse
any chance you are using substratum theme? I had that problem and had to clear the theme to make it go away.
lucky_strike33 said:
any chance you are using substratum theme? I had that problem and had to clear the theme to make it go away.
Click to expand...
Click to collapse
Other than unlocking the phone and rooting, the phone doesn't have much in ways of alternative theme. I'm still using factory everything.
dyingearth said:
I ran into a issue whereby the phone went into a boot loop. It's not a total shutdown, but a reboot as it came back within 10 seconds. I running Audible (in the background, not playing), Waze and broadcasting Periscope. After the first reboot, I stop using Periscope. The phone went into another reboot after I startup Waze. After 2 more reboot, I tried to do a graceful shutdown. The phone was stuck on shutting down for a couple of minutes (with the arrow circle stuck). I finally does power+volume down to do a full reboot. Afterward, I powered down another time and make sure comes back correctly.
Not sure if this is caused by too many apps running, the phone does appear to be warm.
The phone is unlocked straight from Google, rooted with Magisk.
Click to expand...
Click to collapse
There was another thread about random reboots of the Pixel 2 XL, there are threads on the Google Product Forums as well. I would recommend to star them and also to follow the steps in this thread to submit a bug report to Google - https://forum.xda-developers.com/showpost.php?p=74472984&postcount=65
please close this thread.
Related
Phone rebooted on me a couple times yesterday, then started doing it more and more frequently, about every 5 minutes. now, it mostly just sits looping at the HTC splash screen. Usually can't even get to recovery, reboots before it has time to load, or sometimes makes it, but dies before I can select anything. Managed to get it factory reset finally, but no luck. Sometimes it will eventually boot after 10-20 minutes of looping, and stay on for a minute or 2. Everything was bone stock (although bootloader unlocked) before this, had been running fine for months.
Any ideas before I buy a new phone?
lkrasner said:
Phone rebooted on me a couple times yesterday, then started doing it more and more frequently, about every 5 minutes. now, it mostly just sits looping at the HTC splash screen. Usually can't even get to recovery, reboots before it has time to load, or sometimes makes it, but dies before I can select anything. Managed to get it factory reset finally, but no luck. Sometimes it will eventually boot after 10-20 minutes of looping, and stay on for a minute or 2. Everything was bone stock (although bootloader unlocked) before this, had been running fine for months.
Any ideas before I buy a new phone?
Click to expand...
Click to collapse
Try installing a RUU for your version, if it stays on long enough.
If not, take it to warranty.
Good luck!
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.
Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?
What was the latest Build you had when it was working fine?
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.
blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.
Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!
Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies
This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Same HERE !!!!
the samed for me, and still now i can't light it up
sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.
Same deal for me and they are sending a replacement. This is a MAJOR blackeye!
Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!
So I feel like this is different from a typical bootloop (certainly different from ones I've had in the past). Any ideas short of factory reset would be very much appreciated. I just need it to load once more to do a Titanium Backup (and I guess I should install TWRP and do a nandroid backup)!
I've been using my Tab Pro for years now, rooted, works perfectly, and I always leave it on. I thought yesterday, perhaps this is a bad idea, I should turn it off every once in a while. But I wanted to play a game before I did. I click the game icon and then everything froze and it restarted itself.
It gets stuck at the SAMSUNG logo page. Sounds like a typical bootloop. After 20 minutes of waiting, nothing changes, so I hold down the power button and it restarts and actually loads to my home screen! Great! I swipe the screen lock, click on my game -- it restarts, rinse, repeat. Each time it restarts itself it stops at the SAMSUNG page, forcing a second manual reboot that fully loads, but doesn't go 10 seconds before restarting. I try to load different things each time and finally give up.
So I look some stuff up online. There's a suggestion to go into recovery (I could've sworn I had custom, but apparently not?) and "Wipe Cache/Partition." I look up that this is safe and do it (Sidenote: Power+Home+Vol Up only works around every 5th try or so. It glitches out every other time, there's a quick flash and a horizontal line and it restarts again). Now I restart and it worked! It loads and no reboot!
But now, a third of my apps/games have the android guy as an icon and even more of the real icons are all grayed out. I figure one more restart and it would come back. Now I'm back into my weird bootloop. I try wiping cache/partition again and again and it no longer works as a solution...
TL;DR - Tablet keeps restarting to SAMSUNG logo, requires 2nd manual restart. Home screen loads, but then restarts 10 seconds later. Clearing cache/partition made things worse. HALP!
EDIT: My current build is KOT49H.T520XXUANAE. I can't even find the stock ROM for this! Does it exist?
EDIT 2: After letting it charge for an hour (it was already 93%) I went back to it and it had loaded! But the home screen was blank save for the Google search and the Apps icon (which found no apps....). I was able to get into settings and attempted to click Application Manager and then it froze again.
Update: Still in need of help if anyone has any. A wonderful person on the forums linked me to my stock ROM, I pushed that through ODIN, it worked and did the "Android is Updating App XX of 200" thing.
It loaded and didn't crash! Most of the icons came back, but were still grayed out (I have a second partition via Link2SD which, when not rooted, doesn't load!)
So I went to Settings to see if USB debugging was enabled... and it froze. Kind of. It let me bring up the task bar and close settings, but not reload anything. Eventually I was forced to restart because I couldn't do anything. I tried booting into safe mode and still nothing.
Now when it loads, I get repeated "Unfortunately, Samsung keyboard has stopped working." and then the touch screen stops functioning and it restarts. I'm having a great day.
hamstrman said:
Update: Still in need of help if anyone has any. A wonderful person on the forums linked me to my stock ROM, I pushed that through ODIN, it worked and did the "Android is Updating App XX of 200" thing.
It loaded and didn't crash! Most of the icons came back, but were still grayed out (I have a second partition via Link2SD which, when not rooted, doesn't load!)
So I went to Settings to see if USB debugging was enabled... and it froze. Kind of. It let me bring up the task bar and close settings, but not reload anything. Eventually I was forced to restart because I couldn't do anything. I tried booting into safe mode and still nothing.
Now when it loads, I get repeated "Unfortunately, Samsung keyboard has stopped working." and then the touch screen stops functioning and it restarts. I'm having a great day.
Click to expand...
Click to collapse
Few of this probs I did have too.
I would recommend to start from scratch and wipe also your data and sd-card (with TWRP). Install either stock or Custom, but put out your sdcard before re-booting.
Just play around and after that (with no probs hopefully) insert it again.
starbright_ said:
Few of this probs I did have too.
I would recommend to start from scratch and wipe also your data and sd-card (with TWRP). Install either stock or Custom, but put out your sdcard before re-booting.
Just play around and after that (with no probs hopefully) insert it again.
Click to expand...
Click to collapse
I appreciate the response, but as I said, I'm looking for anything shy of factory reset. If I lose all of my apps and data and configuration, I might as well throw out the tablet and buy a new one.
Still trying to figure out the pattern. I got another attempt of it not restarting for 10 full minutes. The keyboard failing is annoying because it doesn't stop, but I can live with it if it means being able to backup my tablet with Titanium Backup. I only got 6 apps backed up before it froze, but I'll get through all of them eventually (I hope). It's just going to be incredibly frustrating.
I've had an M9 for 2-3. After the first year I got my phone, I installed a custom recovery and rooted it but later uninstalled root and custom recovery. It has been fine ever since except recently. Last month, my phone randomly crashed for the first time and got stuck in the infinite bootloop. It was as if everytime it tries to boot up, it crashed during it. If I hit the power, vol up, and vol down button, I make it to the screen with the option to go into recovery, download, etc. But when I actually try to go into either bootloader, recovery, or download mode from that menu, it crashes and goes back to the white htc logo. I've have gotten the phone to bootup a couple times by leaving it in the freezer as it tries to boot up but after using it for 1-5 minutes, it crashes again. If I don't use the phone at all, then it usually wont crash. After a day or 2, the phone fixed itself. Then one morning, my notifications got stuck together and my screen became unresponsive. So I took my death sentence and restarted my phone and now my phone has been doing the same exact thing for a week. I don't know how to fix this problem because getting it crashes trying to go into recovery and trying to do a factory reset is risky since it could crash during the reset. If also manage to make it into safe mode thinking maybe an application or virus is causing this but the phone crashed in SAFE MODE so I don't know what the problem is. I doubt there is any saving this phone because is probably a hard ware problem but who knows. Any help would be greatly appreciated!! Thank you.
Flash back to stock. Stock firmware fixes all sorts of issues.
To begin with, the device was rooted with Magisk 18.1 flashed about 2 years ago, running stock OxygenOS Oreo 8.1. Recovery: TWRP-3.2.1-1-cheeseburger. Kernel: RenderZenith OP5T [OOS-O-EAS-V3.7.0]. This was the setup I was satisfied with and running in about a year (a total of 2 years).
However, after the first year, I've tried to update TWRP to version 3.3.1-20190908-0-codeworkx-signed-forcedecrypt-dumpling in order to flash and update to the newer OxygenOS Pie 9.0. Something went wrong after flashing the newer TWRP and I couldn't get into recovery anymore... all I saw was a black screen when trying to get into it. I haven't bothered about this since the system booted and worked fine, so I gave up on the 9.0 update and stayed on 8.1. I was able to use it like normal another year. Everything was running very smoothly until a couple of days ago...
The battery has discharged to 0% and the device shut off by itself. 30 seconds before the shutdown, the UI was much less responsive and a popup about the device turning off popped up. I've put it in charge the whole night and when I woke up in the morning... couldn't boot into the system anymore. Instead, the phone booted into the 'broken' recovery, with constant lit of light blue LED (started to lit a couple of seconds after booting, only in the 'non-visible' recovery), and a black screen. I've looked up the fastboot/bootloader keys combination and went into it, well from there, I've tried the turn-off, start, recovery, and bootloader option. Turn off = Off. Start = Recovery. Recovery = Recovery. Bootloader = Bootloader.
The next step I've done was to connect it through a PC and run ADB on it in order to flash the old TWRP-3.2.1-1-cheeseburger. Re-booted into recovery straight after successfully flash and the recovery started to work again. The light blue LED stopped to lit any longer and I haven't seen it anymore. The first thing I've done in recovery was to clear the cache, dalvik, and do a nandroid backup, then tried to re-boot into the system. Finally, it booted into the system and I was happy like a kid when I saw the OnePlus boot animation again, however after putting my password and SIM pin code, I can enjoy it without any issue for about 30-40 seconds before the UI suddenly starts to be non-response (touch doesn't work), the screen starts to flash, sometimes (looks more like turning the screen on and off), until I see a "Turning off..." popup 20-30 seconds later (the battery is fully charged and disconnected from the power source) and the device is rebooting itself into the 'working' recovery. This is how it works each time I boot up into the system now. However, the power button is working and I can turn the screen off and on while the screen/touch isn't responding, the power menu can be opened by holding it (before it's too late and the "Turning off..." popup appears), from there I can choose to re-boot or power off. Magically the touch is working here. If the phone has been rebooted/turned off manually, by hitting either reboot or power off in the power menu, it reboots into the system instead and the same **** happens - not to recovery like it does when the "Turning off..." popup appears and it's turning off by the system.
I'd like to get everything back if possible, at least for one or two days, to back up all data, do some screenshots, back up browser bookmarks, history, open tabs, sms and calls, then give a fresh custom 11 to it.
Any help I can get from you guys? Is there a solution that I could try? What about flashing the newest Magisk onto it? Might it help or rather corrupt it more? Anything else? I'm out of knowledge in this situation and I'm relying on you.