Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
MATTHEWLONG said:
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
Click to expand...
Click to collapse
This has been an ongoing thing with the 6P and 5X, there are multiple threads on this bootlopop issue some recoverable, some not. Check this out see if it helps..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Thanks for the support, I will take a look.
I've read too many threads about 7.1 and the beta program causing boot loops and bricks....this is ridiculous!
Do you have a nandroid on hand? If so, try restoring it and see if that works.
I have only boot looped twice with this phone. Each time I went into TWRP and did a full wipe (everything except internal storage). I completed the full wipe three times consecutively. After the third wipe I boot into fastboot and flash the latest stock images from Google. Reboot.
Let the phone sit for 10-15 minutes then boot back into fastboot to flash custom recovery (TWRP). Then boot into recovery to flash SuperSU. Reboot. Let phone sit for another fifteen before continuing with setup.
I know wiping the device three times probably doesn't do anything extra than wiping once before flashing but it's what I've always done and what's always worked for me.
Related
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
My Nexus 6p just rebooted randomly, and it's stuck in a bootloop. I am on 6.0.1 (ignore the thread name, it's a typo), I did not upgrade to 7. I am rooted and bootloader unlocked. I can access recovery (TWRP). Can anyone help?
I just attempted to update to the latest build of 6.0.1 (since I had been putting it off) via fastboot, and that still didn't fix it. Still bootloops. Hoping to avoid a factory reset if possible.
Factory reset didn't help... Tried to format the data, didn't work.
Sadly it sounds like your 6P bit the dust. You can see if any of the posted possible solutions in this thread help, but...
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Yeah, I don't know... I thought if I could boot to recovery, it would be easy to fix. But no matter how many times I wipe, factory reset, format, use adb to reinstall, it keeps bootlooping.
Yeah sounds like the boot loop of death. If you formatted data and fastbooted the factory image and still no go, that's pretty much that.
Great. I'm just over a month outside the warranty period and they want me to pay $160+ to get a replacement. And the replacement will have just a 90 day warranty, and if this issue occurs again, which is likely, I'll have to pay $160 again. Never getting Huawei again.
So I have researched everywhere I can, watched videos, etc. and I cant figure this out. Wondering if I bricked my phone.
Originally my phone was stuck on the boot animation screen for Essential. For hours. So I factory reset it using the stock recovery. After that phone would boot and either get stuck on the essential Logo, or stuck on the boot animation. I reset the phone a bunch of times, and on 1 of them I was able to get to the phone set up screen which I quickly got through and made sure I was in developer mode, and had OEM unlocked turned on. While I was in the setup screen all kinds of services kept force closing, and about 30 seconds after setting up the developer stuff to unlock the bootloader the phone finally froze and went to the boot animation screen and just stayed there.
Next I unlocked the bootloader following the steps on here, then unlocked critical_processes or whatever it is called.
Next I tried to flash a stock essential rom from the roms dump page. When trying to wipe user date I get "error. Cannot generate image for userdata". I then flashed the stock rom, and restarted and experienced the same exact thing as before. Either stuck on logo screen, or stuck on boot animation....for hours.
Last I tried flashing to the stock rom recommended in the lineage OS thread, and then flashed TWRP again, and flashed Lineage, and once again I am stuck on the essential logo screen. If i go into recovery it now goes to the Lineage recovery so I am assuming the install worked.
I am completely stuck now and can not figure out what to do next, or if I am just stuck with a hard bricked phone. Any help would be appreciated.
Update: So after restarting the phone about 7-8 times I actually got Lineage OS to load up and was able to set the phone up. That lasted about 2-3 minutes before the phone froze, went back to the Lineage startup animation and then restarted. Now it won't go past the Essential logo screen.
I'm new to the PH-1. I went in circles because all I wanted was the AOSiP ROM. Then no touch, tried flashing the September "hyp" and "rpm" partitions. Didn't help... And on it went.
I finally dug out of my hole by sideloading the essential.com OTA in stock recovery.
That's what I would try if I were you. But then, I'm new to the phone [emoji23]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
I'm new to the PH-1. I went in circles because all I wanted was the AOSiP ROM. Then no touch, tried flashing the September "hyp" and "rpm" partitions. Didn't help... And on it went.
I finally dug out of my hole by sideloading the essential.com OTA in stock recovery.
That's what I would try if I were you. But then, I'm new to the phone [emoji23]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Sideloading it using the factory recovery is the only thing I didn’t do. Everything I flashed through fastboot. Guess I’ll try sideloading it next.
minttoast said:
Sideloading it using the factory recovery is the only thing I didn’t do. Everything I flashed through fastboot. Guess I’ll try sideloading it next.
Click to expand...
Click to collapse
Did that work for you?
I was having these same kind of problems - all guides never said a thing about flashing unlock_critical - after I did that (and all other requirements to unlock and flash roms) then sideloaded I think it was .092 factory zip - I was able to start flashing things like old school android that I am used to. Still need to figure out why they are saying to use magisk on a boot.img and then flash manually but that may just be certain roms.
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