Database Users

Updating to 4.3 Image with fastboot failed.

Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You

Cantacid said:
Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You
Click to expand...
Click to collapse
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647

kzoodroid said:
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647
Click to expand...
Click to collapse
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img

Cantacid said:
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img
Click to expand...
Click to collapse
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691

kzoodroid said:
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691
Click to expand...
Click to collapse
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.

sn0warmy said:
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.
Click to expand...
Click to collapse
In the other walk through flash system image and boot image is replaced by "./fastboot update image-occam-jwr66v.zip". This could help those who are having problems flashing the system image file. I've also seen this method used for windows in that all you flash is the bootloader image then the update image and your done.

-w is to clear the userdata, but the problem is its not pushing the system.img on the phone! Tried without -w and yet the same issue! I have restored my previous rom and madea nandroid for 4.2.2 stock! Might go back to that and try updating ota! Can somebody confirm if i have to lock bootloader and lose root to get an update!
I have no clue why the same steps work for 4.2.2 but not 4.3 image files!
Sent from my Nexus 4 using Tapatalk 4 Beta

One thing I don't think anyone has mentioned (which may actually be the core solution to this problem for everyone) is that you need to update your SDK Platform from 17 to 18 and you need to install "Android Support Repository" in order for 4.3 to properly flash. To do this open terminal and paste the path to the "android" executable file found under sdk/tools. My path was:
/Users/kevin/Desktop/Android/sdk/tools/android
After pasting the appropriate path into terminal hit enter. This will open the SDK Manager. Once SDK Manager is open it will ask to update outdated drivers. One of the drivers being updated is SDK Platform. Before hitting the update button scroll down to the 'Extras' folder and check the box next to "Android Support Repository". Now hit the update button.
After doing this, reboot the computer (may or may not be necessary) and try flashing again by following the steps I provided in post #5. Let me know if that solved it.

Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta

Cantacid said:
Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
sdk/tools is located wherever you extracted the .zip file to. In my case I just put it all in a parent folder on the desktop called "Android".

[Q] Nexus 7 "Booting Failed"

Hey Guys,
So I was trying to downgrade to 4.3 on my Nexus 7, and I was dumb enough to disconnect it before it was complete. I believe it was in the process of deleting user data. Now I have a screen that says "booting failed" on the left, the google logo in the middle, an unlock symbol on the bottom, and a start banner on the top left, but every time I try to hit start, it just stays on the same screen saying booting failed. Same results when I try to boot into recovery. Is there any hope?

You should investigate whether or not you can communicate with it using fastboot. You might need to get it to the bootloader screen (rather than the "failed boot" screen). [REF] Nexus 7 Button Combinations
If you can, then there is all sorts of hope (from what you describe, it sounds like the bootloader is unlocked). All you need to do is do a little reading about fastboot - for instance in the "return to stock" thread here on XDA.
fastboot is the gateway to all things root with the N7.

There might be hope
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.

bmoney83 said:
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
Click to expand...
Click to collapse
I've done exactly the same thing. Any update please?
Thank you

bmoney83 said:
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
Click to expand...
Click to collapse
Stuck as in no messages, no output, prompt never returns?
Have you tried soft-booting a recovery to see what happens? e.g.
e.g. TWRP
Code:
fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
e.g. CWM
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
-OR- (non-touch version)
fastboot boot recovery-clockwork-6.0.2.3-grouper.img
(The above are just examples, I'm not recommending a particular version of either custom recovery)
That might be a start. By communicating with a soft-booted recovery (adb shell blah-blah-blah), you can look at the kernel log (e.g. "adb shell dmesg") and see if it is complaining about partitions, filesystems, etc. The only rub with this is that because of the N7's use of an "internal" pseudo-SD card, the custom recoveries try and mount the userdata partition as soon as they start up, so if there is something wrong with that filesystem, the recovery itself might get wedged. I think I saw this with TWRP for instance - the touch interface wouldn't come up when I had a effed-up userdata partition. So, either an older recovery or a non-touch interface recovery might be adviseable here if you have troubles.
good luck

Solved!
Alright, two things helped me out here.
1. I used a different computer and reinstalled everything.
2. When you unzip the stock rom, it still leaves one zipped file in there that also needs to be unzipped into the platform-tools folder.
And now I'm in business!

[Q] N4 stuck in boot loop after OTA update

Hello,
I saw that the OTA update to Lollipop was available on my phone today, so I went ahead and let it download. Upon completion of the download, it restarted and applied patches, then restarted again and has been stuck in boot loop for about an hour. After reading several other threads on how to try to reset the phone, I'm stuck. When I try power + volume up or down, the LED status indicator flashes red and I never get to any kind of other screen. Am I completely screwed? I previously had stock 4.4.2 with no modifications.

Finally was able to get to the bootloader menu. Apparently having the phone plugged into the charger was preventing me from getting there for some reason. I ended up having to wipe the phone to get it to boot

so you can get into clock recovery right? download nexus 4 toolkit..that might save your phone. I suggest you to unroot and flash everything to stock and then unlock again and start everything from scratch. good luck.

Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?

Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
I guess TWRP Recovery has option to enable MTP and you can access the internal SD card by connecting mobile with computer using usb cable.
---------- Post added at 06:37 PM ---------- Previous post was at 05:37 PM ----------
Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
Flash TWRP Recovery using fastboot.
1. If you have otg y cable, connect it and use file manager to copy all the files.
2. OTG method is failed then select “Mount”, then select only “Data” and connect your Nexus 4 to your computer and Enable MTP in TWRP. now you can use adb pull and push commands.

I ended up going the factory reset route, which wasn't really a bad thing. My photos had been backed up in dropbox and the play store remembered all the apps and were able to reload them. The only things I really had to do was reload some music onto the phone and re-enter passwords for apps.

Same story here: sideloaded the OTA zip file, then had bootloop. Tried a few approaches, but none worked. In the end only wiping the data was the solution for me. Lost some userdata in a few important Apps...

I went through this yesterday. The only way to get it to boot is a Factory Reset from Recovery. It works like magic, but sucks you lose the data.

Got the OTA yesterday and also got a bootloop(stuck in boot screen animation). I couldnt afford losing my photos/videos as i had no backup , so i figured out a super easy to get it to boot without wiping data .
I was unrooted with stock recovery running stock 4.4.2, bootloader was unlocked. I flashed CWM recovery through fastboot and wiped chache+ Dalvik from there then simply rebooted the phone .
I had already tried wiping cache from the stock Android recovery,needless to say that didnt work for me.
If anyone else is having the same problem please try the method above and report back, cheers!

I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/for...Q/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexu...image-t2010312 + HelpMyNexus

[Q] Need help! Did OTA update to 5.0, stuck in bootloop!

I need some major help
My N7 2012 was stock, never rooted. I had only installed OTA updates. Yesterday, the OTA update for Lollipop appeared, and I installed it.
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
I've also tried getting it into fastboot, and I can issue fastboot commands. However, I've never unlocked the bootloader. And when I try to unlock it now, I get the screen that says "This will void your warranty are you sure?" But when I select Yes, fastboot's console says "Failed", and it remains locked.
If I go into Recovery, it just says "No commmand"
I need some help from the geniuses on this forum. To me it seems like an app running at startup is causing the crash, so if I could just get it to Safe Mode, I could figure it out and uninstall it. Hell, I'd be fine w/ a total wipe at this point. Just something to get it working again!
Thanks in advance!

Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.

Didn't work
bubba949 said:
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Click to expand...
Click to collapse
I tried using the Nexus toolkit, using Flash to Stock/Unroot in Bootloop mode, and it didn't work. A few sections succeeded, but most of the sections said "FAILED". Even after performing this, it still wants to boot to my normal desktop, so I know it's not re-flashing a thing.
I wish I knew more about this. I can get into fastboot by going to Power+VOL- but because it won't stay on the desktop, adb commands are a no-go. Is there something in the Advanced section of the Nexus Toolkit that will let me do a reflash? I'm afraid of just poking and trying things for fear of truly bricking it.
Thanks.

Sorry just re-read your last reply didn't realise you can't do adb commands, if you get to a point when you can then below may help...
I had a similiar issue caused differently what i did was to go to this link
http://forum.xda-developers.com/showthread.php?t=1907796
Downloaded the bootloader from JWR66V the guy mentions in his thread he mentions the same issue that i had which is when i tried to flash a stock or custom rom i kept getting messages about invalidstate on bootloader then the system and userdata images would fail when i tried to install...
In the end i downloaded the stock JWR66Y rom, replaced the bootloader image with the one mentioned above, i had to flash the seperate parts of the rom as the Nexus Root Toolkit wouldn't accept the MD5 after i replaced the bootloader so make sure the recovery, the modified bootloader, system and userdata are in your SDK tools folder then i did the following in cmd...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Fastboot reboot
And voila it booted up and then upgraded its self and is now stock running 5.0 but its working for 2days it wasn't lol

alastria1 said:
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
Click to expand...
Click to collapse
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
bftb0 said:
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
Click to expand...
Click to collapse
Sounds like something is draining the RAM. Try using the stock launcher as default.

Still crashed
dtg7 said:
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
Sounds like something is draining the RAM. Try using the stock launcher as default.
Click to expand...
Click to collapse
I didn't know that. I tried it, and I was able to boot it into safe mode doing this ... and then it crashed in 15 seconds and rebooted...
At this point, I'm considering just emailing Google, since its their update that did this.

They'll probably tell you to wipe cache partition. And by the way,
alastria1 said:
If I go into Recovery, it just says "No commmand"
Click to expand...
Click to collapse
that is a normal operation, it's supposed to say that. What you need to do to get the actual recovery menu is, with screen saying No Command, hold the power button, then click the volume Up button, them let go of power.
This will get you the recovery options, where you should scroll down to wipe Cache partition (last one I think) and select it by hitting power. Reboot into Android and see if that helped.
If not in the same recovery menu there's an option to wipe everything, factory reset. that might cure your device but it will wipe your data.
There is an adb command to pull your sdcard data off your device, but I've never tried it in stock recovery. it might work, but of course it will probably require you had turned On USB debugging.
adb pull /storage/sdcard0/ yourcomputerfolder
yourcomputerfolder being a location on your laptop, like a folder on the desktop.
try this command when in recovery, I don't think it works in bootloader. also, if it works it will only backup your regular files, not your installed apps.
if not then just do the wipe from recovery.
good luck.

Still a no go...
So, I got into the recovery menu, and did a full factory reset. After it rebooted, it went right back to Nova Launcher (with my usual wallpaper on there), and crashed as before. Getting into safe mode confirmed that it no apps were wiped. Factory reset didn't reset a thing.
Its almost like the flash memory is stuck on read-only mode. No matter what I do, nothing changes the contents of memory.

That is weird. And I suppose you can't do what 'wakers' suggested and flash the individual partitions since it probably requires an unlocked bootloader, which you already tried to unlock unsuccessfully. I'd say you were up sh-- creek without a paddle, but... Google searching, maybe there's still a tiny bit of hope:
See this discussion: http://android.stackexchange.com/qu...p-after-lollipop-flash-no-adb-and-no-fastboot
to summarize the suggestions:
- try holding the power button for over ten seconds to kind of reset... something
- try sending the command: fastboot oem lock
yes I know you never unlocked but try it anyway, it might go thru where unlock failed.
speaking of fastboot oem unlock, I know it failed but maybe you can just keep sending the command a few times, one of them might go thru.
I'd add another suggestion: carefully remove the back and carefully unplug the battery and let it sit for a while. then put it back together and try booting up.
may the force be with you.

Finally resolved
Thanks to the posters for the help. I contacted Google customer support and they're overnighting a refurb replacement for free.

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