Database Users

rom installed not rebooting stuck on unlocked screen

hey anything please i wiped everything and installed zip"rom" from sd and installed secussful and then i clicked reboot and it just stays on the motorola screen with unlocked in the corner and is stuck there what am i not doing or doing wrong its rooted and unlocked

INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"

clod007 said:
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
Click to expand...
Click to collapse
i made a back up with titanium and android recovery....
i pulled the battery installed it 2 or 3 times and same thing
what exactly do i type in my cmd prompt on fastboot

If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"

clod007 said:
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
Click to expand...
Click to collapse
i dont know how to reinstall it but i made back ups of everything

Enter in Android recovery mod
Backup
Chose restore
Atrix - "CM7"

Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight

android-DEP said:
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
Click to expand...
Click to collapse
ok it rebooted and went off the screen now its in a boot loop and flashes the motorola sign then shuts down and keeps going

ok, so the issue was partly the cache not being wiped prior the rom being installed and something went wrong with the installation of the kernel. That happens if the boot.img didnt properly extract and write to partition or its just incompatible with the rom\device.
Visit faux123's thread with kernels for ATT froyo, GB, CM7 & CM9
download the kernel that's compatible for your rom(froyo, gb, cm7 or cm9). Once you download the zip, go in there and pull out the "boot.img" file and put it into the same folder you have fastboot.exe in and boot into fastboot again.
quickly check connectivity with "fastboot devices" to verify and if that checks out, use this command.
"fastboot flash boot boot.img"
it takes like 3 seconds or something to complete so its an easy fix, after its done just do the "fastboot reboot" command.
i had this same exact issue last week plus my recovery was being erased along with this problem so i keep boot.img & recovery.img just sitting inside the fastboot folder just in case
atrix reboot project - it has every single file thats for the atrix and copies of systems, roms, tools, recovery files, mods, tweaks

Try this:
Pull battery
Replace battery while holding volume down until you see fastboot
Tap volume down to until you see android recovery, then press volume up to enter recovery
First try wiping cache/dalvik, if that doesn't work restore nandroid backup, if that doesn't work reflash rom

Nexus 4 stuck on boot screen after update

Need some help.
I just sideloaded the 4.3 update to phone and now it's stuck on the 'X' loading screen.
My phone was rooted, but all stock (including the bootloader). I used the sideload ADB command and everything went fine, but the phone now won't boot.
How do I fix this?

did you data wipe(factory reset) before flashing?? if not, you have too.

I applied the OTA...didn't think I had to
Any idea on how I fix it now?
Really don't want to lose all my data

Install a custom recovery and wipe or apply factory image

favaroooo said:
Install a custom recovery and wipe or apply factory image
Click to expand...
Click to collapse
Is there a way I can fix it without wiping everything?

theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
I do not think because you have to change recovery you must unlock the bootloader and unlock bootloader wipe the phone

theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
no, its the data(and other stuff) causing it not to boot. same thing when flashing custom rom, you wipe when fkashing different roms. and going from android 4.2.2 to 4.3, theres many changes, enough to consider it a different rom.

Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.

theprodigy85 said:
Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.
Click to expand...
Click to collapse
are you flashing a zip or an img file??

simms22 said:
are you flashing a zip or an img file??
Click to expand...
Click to collapse
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...

Try to restore using the factory image

theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
yea, the zip youd want to wipe data/factory reset, then flash the rom. dirty flashing wont help since the changes are big enough.

theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
I bought my ole lady a Nexus 4 for Valentines day, anyway, today she got the OTA update and let it install the update. Now mind you she is 100% stock, adb debugging was not enabled, and her bootloader was still locked. (She would not let me touch her Nexus 4 lol) When the device rebooted it stuck on Android Upgrading finishing boot. So I said well let me see what I can do, this is what I did to fix it.
I use only Ubuntu so this may not work on windows i do not know. I Booted the device to the bootloader, connected it to my laptop via USB. I opened a terminal and typed in "sudo fastboot devices" and entered my password when promted and this gave me the device ID and fastboot letting me know fastboot was working. I then typed in "sudo fastboot reboot" and the device rebooted but was stuck on the bootanimation. I opened the internal storage up on my laptop in my file explorer and made a copy of her internal storage. Next I booted the device back into the bootloader then opened a terminal and typed in "sudo fastboot oem unlock" and the device gave me the unlock warning and the yes or no options. I selected yes so it would factory reset. After it did the factory reset the device reboot and booted to the setup welcome screen. Hope this helps others, also thanks to my good good friend Ljjehl for reminding me to use "sudo".
Edit: If you open the command promt with Administrative permissions in Windows this will work in Windows as well. Go to C:\Windows\System32\cmd.exe and right click on the cmd.exe file and select run as administrator. Then CD to the location with your fastboot.exe command. Thanks to another good friend TheBr0ken.

Thanks for the help...
I just ended up flashing each of the 4.3 components from the factory image. Just annoyed that I lost everything...

I'm stuck at the same screen. I received the OTA update, I didn't do anything special. My phone is unlocked and rooted (or WAS) but that was months ago, the rest is stock.
I think having encryption on my phone may have made it do this. I don't think Google anticipated doing the update properly for encrypted phones. Now I fear I've lost everything because even if I could connect, all data is encrypted...

similar problem
After starting to OTA update it was going smoothly, i was making breakfast, came back to find my screen at the "starting apps" screen frozen. The little circle that rotated wasnt doing anything so i left it there for awhile longer and still nothing. It would not move off that screen so i held power button down and restarted. now its stuck at the X screen also.

Yeah, I'm stuck there too. Already tried Factory Rest, didn't work. So what can I do?

I was on stock 4.2.2 and unrooted. I used the 'Google Services Framework' hack to force the 4.3 OTA update. The update downloaded successfully, phone restarted to apply the update and then restarted again. And now its stuck at the Google screen and keeps on restarting :crying:
I dont have the USB drivers installed on my PC too.

Same Problem
I have a nexus 4 (stock and unrooted),after 4.3 update,it is lagging during phone lock on/off (2 sec/5 sec).Hence I restarted my phone,and it stuck at "x" logo.Did clean data 3 times and then its working.
The problem is,in 2 days,I have experienced and done above thrice?
What could have gone wrong?

Hi guys,
I've just found how to correct this problem. All you have to do is to correctly wipe your phone before flashing factory image.
So :
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
I've just unbrick a n4 this way 15 minutes ago.
I have found the problem in recovery where you can see error log saying "cannot mount cache"
So formating correct the issue.
Hope it can help, fingers crossed.
Sent from my Galaxy Nexus using xda premium

updated to 4.4.1 stuck in boot animation!

Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?

RedBullet said:
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
Click to expand...
Click to collapse
I would recommend flashing the 4.4 stock factory image from here in fastboot mode. Then once your device is booting up properly again I would recommend taking a look at this guide to properly install the 4.4.1 update.

You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.

planet_x69 said:
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
Click to expand...
Click to collapse
Thanks, I eventually got it. I was really puzzled that I couldn't select recovery from the bootloader. All set now though, thanks!

I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?

jalize said:
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
Click to expand...
Click to collapse
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...

RedBullet said:
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
Click to expand...
Click to collapse
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!

jalize said:
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
Click to expand...
Click to collapse
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery

RedBullet said:
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
Click to expand...
Click to collapse
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.

jalize said:
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
Click to expand...
Click to collapse
Hi,
Try flashing it fresh stock again, factory reset your device from recovery, download the stock image file from here, untar it, then unzip the zip inside the tar and you'll get some files (.img). Copy those files to your fastboot folder and then open a cmd there. (Guessing that you're using Windows)
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
If you're using Linux, do the same, but instead of only fastboot use:
Code:
sudo ./fastboot
Then boot it. I had the same problem when I updated mine to 4.4.1, but I did one thing a little different... Instead of fully "stocking" it again, I flashed back 4.3, flashed 4.4 OTA and then let it boot, without wiping my data, after all it was running like this before. Worked. But as I'm unsure of your situation I think it's more secure and easier to fully stock it again.
Hope this helps,
~Lord
PS.: Remember to put your device in fastboot mode!

Reboot loop, can't access Recovery

This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.

StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk

StarShoot97 said:
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?

theesotericone said:
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
Click to expand...
Click to collapse
I said it looks like this, I did not say the button is the reason
When I access fastboot it stays there until I manually select an option

ultyrunner said:
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.

StarShoot97 said:
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
Click to expand...
Click to collapse
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk

ultyrunner said:
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
When stock recovery is installed, I am from time to time able to access it (most of the times it just ends in a bootloop)
If I flash TWRP I can't access it, no matter how often I try
I have factory reset my phone, the stuff on the internal is still there and I want to reach this, as I have my chats, SMS, university stuff and so on backed up on the internal storage
I am trying everything - all the regular adb methods, toolkits, every driver, nothing is working
Sorry if you don't understand my situation, but I am in a pinch right now

You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery and cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Edit2: wrong, see my latest reply

RoyJ said:
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery. Perform a factory reset again like you already mentioned you did as well as a cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Click to expand...
Click to collapse
I did this already exactly like you wrote, did it again now, and I am still stuck in the reboot loop (boots up to Google Logo, then shuts itself down; repeat)
Can't reach recovery mode either

You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.

Fastboot twrp 3.0.0-0 then try to access it

RoyJ said:
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Click to expand...
Click to collapse
Yes, I think so too. I flashed the phone with the full Stock image, the bootloop is still there.
Looks like my precious is dead
At least I have my most important data like phonenumbers, pictures and SMS saved to the cloud
Gonna RMA it tomorrow
Goodybe my precious, I hope you'll be fine :crying:

Got my device back today, the mainboard was damaged, so I had no chance to get my data from the phone
Hey, at least my warranty has been renewed 'till 2018

StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
Try flashing TWRP 3.0.2-3 or boot into twrp through fastboot. Using
fastboot boot recovery <twrp filename>.img
I think booting to twrp using this command will work.
And here's the link to Twrp 3.0.2-3 , as its not available on Official Twrp page.
https://idlekernel.com/twrp/nexus/twrp-3.0.2-3-angler.img

I had the same problem with my 5X, nothing worked I tried every possible solution described above and more. Nothing. I figured out that there was nothing to loose and followed directions from YouTube videos (links below) and it worked. Used heat gun at max temp for about 2 mins from each side. It's been about 12 hours since then, phone works flawlessly. Here are the links:
https://www.youtube.com/watch?v=SD25mdrgAys
https://www.youtube.com/watch?v=Cqh2x-TGnCY
Be careful handling the motherboard after you heat the first side, let it cool first before you start working on the second side. The same with the second side do not pick it up until it's cool.
5X, Pure Nexus Rom 7.1.2 June 5th security update, Elemental X Kernel,

has anyone found solution to this?????

sudden bootloop (can't get into recovery mode) n I didnt update to android 7,

so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help

jay0514 said:
so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help
Click to expand...
Click to collapse
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21

5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
ohhh i see
yeh I dones't let me get to the recovery mode in the options from bootloader
and what are the commands to format cache and data in fastboot??

5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'

jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...

5.1 said:
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...
Click to expand...
Click to collapse
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S

jay0514 said:
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S
Click to expand...
Click to collapse
Sorry... Known issue with the N6P... Have you checked the tread I linked you in my first answer?
Good luck...

jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
Fastboot flash-all.sh is for Mac computers so presumably you have a Mac. Flash-all.bat is for windows. You need to unzip the Google image and move everything into the same folder where you have the fastboot program. Just open a command prompt window inside that folder and type the command. That's how I do it in Windows. Presumably the process is similar with a Mac. You will still have a zipped archive after you unzip the Google image but you want to leave that one as is. So far flashing flash-all.bat has gotten me out of every boot loop I've gotten into on my 6P but my phone never spontaneously bootlooped. I was always doing something (updating a rom, trying to restore a nandroid backup) that resulted in a bootloop. The fact that your phone boot looped without warning is probably a bad sign. If you still have warranty I would try to flash stock and see if you can RMA phone. If that isn't possible you might want to try staying on stock or using a different rom and seeing if the random reboots still occur. Good luck.

Well that really sucks. Sorry for your loss but it is a long running phone failure problem. I'm on my second 6P because this. Even worse to me is the fact your were running almost the exact same setup I am now. I refrained from running 7.x.x to try and minimize my chances of another BLOD so now w4on knows what to do. Lol
Sent from my Nexus 6P using XDA-Developers Legacy app