Database Users

Nexus Bootloop (tried flashing and wiping)

Hi,
I have a rooted nexus 6p, all was well until it decided to reboot and boot-loop when I opened my music app. I get as far as the white Google logo then the phone restarts and I'm back to the normal warning then Google logo then reboot.
I have managed to get into the recovery screen (with the android laying down) but when i choose recovery mode the phone just starts boot-looping again.
I am wondering if I have somehow managed to hard brick it?
I have tried to flash the latest OS onto my phone but it said no signature.
I did managed to wipe the device also.
Thanks for any help.

Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?

istperson said:
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
Click to expand...
Click to collapse
When my phone started playing up I was still on MM 6.0.1, I tried to flash N after the boot-looping started.
Thanks

6P bootloop help request.

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.

7.1.2 bootloop problem

Hi all, I ve updated my device to 7.1.2 beta via OTA the day before. Several hours ago, it started bootlooping after experiencing a battery drain.
Locked, out of warranty, cannot get into recovery mode.
I am giving up this device but does anyone know how can I restore my data from the phone?

Vince.L said:
Hi all, I ve updated my device to 7.1.2 beta via OTA the day before. Several hours ago, it started bootlooping after experiencing a battery drain.
Locked, out of warranty, cannot get into recovery mode.
I am giving up this device but does anyone know how can I restore my data from the phone?
Click to expand...
Click to collapse
If you are fully on stock and an OTA boot looped your phone I would contact Google and see if they will do anything to help you. Even out of warranty Google should accept responsibility for screwing up people's phones with their OTA. I had the same problem with the OTA but my bootloader was unlocked so I could flash a factory image and get my phone back. I was able to get to fastboot menu by playing with the power and volume keys for a while. If you can get to that menu you might be able to factory reset your phone or side load the Feb OTA. I don't think you can recover your phone data in the phone's current state.

if you have only access to Fastboot so you cannot backup any data unless somehow install recovery boot to recovery.

Geeks Empire said:
if you have only access to Fastboot so you cannot backup any data unless somehow install recovery boot to recovery.
Click to expand...
Click to collapse
Why are you spamming this forum? Please leave your personal advertisements out of your posts.

can't you sideload the ota file of a 7.1.1 rom? you should be able to access bootloader screen.
if it's not the bootloop of death that's been happening around here (included me) you can download an ota file from google factory image page and sideload it

jhs39 said:
If you are fully on stock and an OTA boot looped your phone I would contact Google and see if they will do anything to help you. Even out of warranty Google should accept responsibility for screwing up people's phones with their OTA. I had the same problem with the OTA but my bootloader was unlocked so I could flash a factory image and get my phone back. I was able to get to fastboot menu by playing with the power and volume keys for a while. If you can get to that menu you might be able to factory reset your phone or side load the Feb OTA. I don't think you can recover your phone data in the phone's current state.
Click to expand...
Click to collapse
Maybe i could donate to the websiteand we can get a thread up and runnig becuaseit took my over an hourto find a fix i havnt even tried yetin regards to the 71.1.1 bootloos onthe Goggle screen as well as the spash scrren, ihave sence lost the spalh screen now its juts black and white google

Some people have reported that the Skipsoft Toolkit got them out of a bootloop. I haven't tried it myself but I think you are giving up too easily. I've gotten lost of phones into boot loops but I don't panic because there is usually a way out. That isn't always the case with the 6P since there is the boot loop of death issue, but I still wouldn't give up just yet.

Help with bricked phone

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.

Nexus 10 stuck in boot animation even after wipe/sideload

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