Just so everyone's aware, I got this boot loop too today with the following scenario:
Completely stock 6p, upto date with latest MM, never been rooted, flashed, whatever.
Signed up for beta N programme today
Immediately got the N OTA update
Installed it - it rebooted post install but back into MM not N.
Rebooted - it got stuck on the Google logo for 30 minutes
Rebooted - permanent boot loop
I can get into the recovery menu and bootloader, and have tried sideloading the latest 7 OTA but still have the bootloop. Reset/cache clearing all tried.
Annoyingly my bootloader is locked - I've never tried doing anything other than installing standard OTA updates from Google so was unaware that unlocking it might save my bacon until it was too late.
I guess it's a phone call to Google tomorrow....
Update - sideloading this installed OK but I still have the boot loop:
6.0.1 (MTC20F) Link 5a1e93e9974908a0683a4ac8a732b81023f4b01182fd3ead3f091f54300de5ce
So all is not lost. I have an unlocked bootloader, but everything else the same as you. Doesn't really matter as I'm unable to flash anything....even updated my android SDK.
Anyway, I too signed up for Android beta program this morning, and instantly got the N update. Boom bootloop. Non stop. Most I could get it was 20 minutes after a factory reset.
What has worked for me (since 12pm today) was a factory reset and upon signing in to setup. I didn't. I set it up like it was brand new and didn't take ANY restore of apps or data from Google. I added my Gmail after and it's up and running with no reboots for 8 hours now.
It really sucks. The only thing I was able to salvage were my ringtones and notification sounds. It's like starting with a brand new phone ( froyo days without titanium backup). Google has a list of all your apps in the store but reinstalling all of them and logging in is a real pia. Been at it all day. But I do have a functioning stable Android 7.
Related
I originally had OOS3.0.2, and I tried to get Beanstalk rom installed. Beanstalk didn't load correctly, and I softbricked my phone. I managed to go through the recovery of downloading the qualcomm drivers and that weird updating program and then sideload an older version of OOS (2.2). I went to this link and did method 1 https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/. But when I get things fixed up, I can't seem to update to CM13, or even to do a normal update with root, without root, with twrp, without twrp. Nothing. Strangely enough, no matter what I've been doing, the data I had from the very original pre-screw-up time is still all there. Every time I try an update it hangs on the 1+ screen and stays there. How can I get past this? I can't seem to upgrade, and I'm stuck in lollipop.
Well I was still able to get into my phone and do a stock recovery from the Update and Restore option from the phones settings menu, so that fixed it.
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Probably something went wrong in the update process and conflicted with something else.
Anyway: hard reset.
The "no command" screen is just a security screen and it's normal, you need to bypass it to enter to the recovery with a button combination (that now I don't remember, but I never remembered it even though I used to enter in recovery after pressing random buttons combinations lol).
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
cybrdude said:
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
Click to expand...
Click to collapse
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
cybrdude said:
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Click to expand...
Click to collapse
Press power + volume up to get recovery menu.
Was having a similar issue. I'm all stock, unlocked bootloader. Signed for N preview and instantly got the OTA download. It installed and pretty much within a few minutes the bootloops started. couldn't even power down without it rebooting on its own. I got it to power down without turning itself back on through recovery/power down. I let it sit and cool down. Upon reboot.....was doing well, and started to boot loop again. I REALLY did not want to factory reset.
Heisenberg said:
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
Click to expand...
Click to collapse
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
So for me, a factory reset and setting up a brand new phone (no backups of any kind....even from Google) have seem to do the trick. Unfortunate that I lose my wifi password backups. Asking some people for their wifi passwords again is a PIA. Especially the ones who don't know them, and it's a 27 key password from their cable company. Anyone know how to pull just the wifi backups from google?
My thought is one app or setting was causing my problem so I'm slowing adding everything one at a time. PIA really. I don't miss the Froyo days that's for sure.
cybrdude said:
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
Click to expand...
Click to collapse
What happened to your old account?
Hey all! I'm having a strange issue regarding boot looping that I can't seem to find an answer to on here or anywhere else, I hope you guys can help.
So my T-Mobile Samsung Galaxy S5 (SM-G900T), purchased in May 2014, while perusing Facebook the other day, randomly shut down in the middle of perfectly normal use and started bootlooping. I had never had the problem before. The device had been rooted for months (I forget what method I used) but it was running a stock Lollipop rom. The first thing I did was factory wipe and cache wipe through Android stock recovery. It worked!... for a couple hours. Then the bootloop started again.
I went and sought a new stock rom, believing that somehow mine had been corrupted, and flashed it via Odin. I also flashed TWRP. Clean wipes, new rom, dalvic/etc. wipes, and booted into stock Marshmallow. It worked!... for a couple hours. Then it started bootlooping again. I went into TWRP and tried to wipe just caches and whatnot, but it wouldn't start again. Long battery pulls sometimes allowed the phone to boot, but it started looping again after ~5-10 minutes.
So I installed the Twisted Lollipop but couldn't even get that to boot. I went back and found the earliest available firmware for my device (as I bought mine right after it came out) and flashed it. Wipe wipe flash wipe whatever, and a succesful boot. It was looking good! I was able to install a number of OTA updates. I was at Android 5.1 when I decided to call it a night and hold off on the further OTAs for today. Today I got up and got ready for work, all's well. As I'm getting ready to leave, I allow Google to update some apps, and begin installing Facebook, Spotify, Cap Metro (for my area's public transit system) and maybe something else, I don't remember. Anyway, as the updates are downloading or installing and I'm checking my email, boom, crash, bootloop.
What's going on here? I've never heard of hardware causing boot loops, but could it be that? I dropped my phone (although protected by a Spigen case) earlier this summer and it cracked the screen-- could it have messed with the motherboard in some substantial way? I had noticed it getting hotter and the battery lasting less than usual, but I attributed that to the device's age.
Any help, any advice, any direction you could give would be extremely appreciated. I don't have the capital to replace the phone right now, and I use it all the time. Thanks folks!
I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?
jsm11482 said:
I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?
Click to expand...
Click to collapse
Mine does it aswell, but after like 20 min it boots up. I flash mine with the "Nexus Rool Toolkit" with the option "Flash Stock + Unroot", in your case i wull put the radio button on "Softbrick/Bootloop". Then follow the steps on the screen and then when it reboots the programm will tell you that you need to wait like 20 min. And then it should be up and running again
So I've finally got to upgrade from A10 to A11. I was unable to follow the guides for doing local upgrades, because of my previously mentioned "No changelog" and "System Update Installation Failed" message the moment you selected the upgrade package. I tried multiple downloads and verified hashes, this wasn't a corrupted download. So I ended up having to Wipe data to get to a stock A10 and then upgrade using local upgrade. That was Sunday. Since then, I've rooted, restored my apps, lived happily on A11....for about 1-2days before I'd wake up a bootloop. The phone would just be sitting on the spinning Oneplus logo without me knowing why we got here. Even stranger, I had NoLimits installed, so I should be seeing that instead of Oneplus.
Attempting to fastboot boot any of my boot images still keeps me in a boot loop, not much to do other than to wipe and try again....So wipe, on A11 stock, root, restore apps and go on my way....Worked great yesterday. again all apps were restored, things were working, no issues. And then I woke up this morning to find issues with Facebook app (images not loading). Okay, whatever, something may be corrupt, just wait for an update from them. Multiple apps in Playstore need an update, great...do those. But then Oneplus Gallery refuses to update...hmmm. Catlog/Logcat refuse to open with insta-crashes. Facebook nolonger has the corrupt image issue, it just insta-crashes.......uh oh......maybe a reboot?.....rebooted and then stuck on NoLimits bootscreen for about 2 minutes....after 2 minutes it reboots and I'm back to being stuck on Oneplus boot image.
So I'm out of ideas now. about to wipe and go back to A10, because I can't for the life of me find a connection to all of this and its getting tedious to restore apps (especially 2fa apps).
Any help would be appreciated.
Hi!
I have had annoying bootloops when making a call.
It connects to a call and then boom, goes dark and reboots by its self. Very annoying.
I have 2 SIM cards on use, dont know If that matters.
Iam suspecting the network connection change during call -setting has something to do with it...
Hope there is an update coming soon to fix this.
Yea I have 2 sims as well (TMo and GoogleFi) so that's an interesting point. We finally now have dual-sim (US/Glo).
I'm currently testing out how long i can go with my current setup: Just A11 + Root + NoLimits....wait about 2-3days, then try LuckyPatcher (best way I know to remove ads), 2-3days, and then continue testing other ideas).