Database Develop

[Q] Bricked Nexus 6 PLEASE HELP!!

Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!

chainfires 3d program hasnt worked on a nexus in years. and you do need to boot back up to enable unlocking the bootloader in the developer options. have you tried wiping data in twrp recovery?

zacrivera24 said:
Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!
Click to expand...
Click to collapse
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.

Evolution_Freak said:
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.
Click to expand...
Click to collapse
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same

simms22 said:
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same
Click to expand...
Click to collapse
Yeah, guess I missed that part.

Evolution_Freak said:
Yeah, guess I missed that part.
Click to expand...
Click to collapse
thinking about it now.. with the bootloader locked, would twrp let you flash anything?

simms22 said:
thinking about it now.. with the bootloader locked, would twrp let you flash anything?
Click to expand...
Click to collapse
Yes, it has been done to fix the soft brick I thought we were dealing with here. Only if TWRP is installed though.

Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.

rootSU said:
Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.
Click to expand...
Click to collapse
honestly, i dont remember. its been about 3-4 years since last thinking of that app. if it does, a rom flash would be needed.

[Q] Possibly bricked N6, bootloop, no recovery, locked bootloader . Help me

Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks

Segnale007 said:
Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks
Click to expand...
Click to collapse
Do you have TWRP or stock recovery?

cam30era said:
Do you have TWRP or stock recovery?
Click to expand...
Click to collapse
Nope I do not. I don't even have access to the stock recovery. For some reason when I select the stock recovery the recovery menu does not appear. It just comes up a dead android with a question mark and nothing else..

Segnale007 said:
Nope I do not. I don't even have access to the stock recovery.
Click to expand...
Click to collapse
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.

cam30era said:
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.
Click to expand...
Click to collapse
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..

Segnale007 said:
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..
Click to expand...
Click to collapse
You have nothing to loose by contacting them and asking.

What 5.0.1 factory stock file did you flash?

Mega Montana said:
What 5.0.1 factory stock file did you flash?
Click to expand...
Click to collapse
This one right here https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz

Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?

Mega Montana said:
Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?
Click to expand...
Click to collapse
Depends if he had a 5.1 bootloader before or not. Attempts to downgrade the BL from 5.1 will result in a loop.
If it appears when connecting to the PC as qhsusb mode, then it's fixable. If it appears normally as a fastboot device, then it needs repairing.

Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help

Segnale007 said:
Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help
Click to expand...
Click to collapse
How did you do that with a locked bootloader?

cam30era said:
How did you do that with a locked bootloader?
Click to expand...
Click to collapse
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.

Segnale007 said:
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.
Click to expand...
Click to collapse
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.

cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm

rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
Aahh. That makes sense. I'm still amazed that recovery was this easy.

cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.

Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
Btw I was surprised to see the phone booting with a userdata and cache files from a newer version of android.
Click to expand...
Click to collapse
Most of those who were able to successfully format cache and userdata still had TWRP installed. You are very lucky. Should buy a lotto ticket today.

Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.
Click to expand...
Click to collapse
You can format cache and userdata with a locked bootloader. You cannot flash cache or userdata with a locked bootloader... Unless your bootloader is "bricked" as per the thread you linked to ultimately.
FYI formatting has the exact same result as flashing userdata and cache. So the options are:
1) you formatted which fixed it
2) you were bootloader bricked and had to use a gpt.bin to fix it.

[Q] 5.1.1. OTA Update Error

My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.

I downloaded the factory image and fastboot flashed the files.
Sent from my Nexus 6 using Tapatalk

Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
What error? Also, have you unencrypted?

Evolution_Tech said:
What error? Also, have you unencrypted?
Click to expand...
Click to collapse
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.

Shift2win said:
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.
Click to expand...
Click to collapse
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.

Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
Mine is doing the exact same, I'm also stock and on T-Mobile.

^same here...rooted and T-Mobile.

skipm said:
Mine is doing the exact same, I'm also stock and on T-Mobile.
Click to expand...
Click to collapse
n7plus1 said:
^same here...rooted and T-Mobile.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61119896

Evolution_Tech said:
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.
Click to expand...
Click to collapse
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?

neudof said:
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?
Click to expand...
Click to collapse
Fastboot. You need an unlocked bootloader.

I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.

robert_shipley said:
I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.
Click to expand...
Click to collapse
That's exactly my problem, I'm completely stock and have to remain that way since I use my phone at work and they require the AirWatch MDM agent to be installed. I even tried deactivating AirWatch and uninstalling it and I still couldn't get the update to install. I hope there is some way they can either erase and download the update again or just overwrite the current one because this one definitely has problems.

Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.

bchildress said:
Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.
Click to expand...
Click to collapse
Just flash the system image. No need to flash everything. If you've unencrypted, then flash boot image too.

I have the same problem totaly stock, not rooted, untouched! I have the same error. I have 64 gb nexus 6 build number LMY47D.

Ok Guys,
Here is the solution,
1. Download stock image from google developer page, https://developers.google.com/android/nexus/images
2. Flash with long way;' DONT USE FLASH-ALL SCRIPT' (I tried, update fails again)
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
fastboot flash cache C:/image-shamu-XXXXXX/cache.img
(FOR FURTHER INFO PLS SEE THE PAGE; http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008)
3. Just turn on your N6 and it will find update and will be succesfull this time

Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.

Evolution_Tech said:
Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.
Click to expand...
Click to collapse
Hey,
I am Rooted with TWRP Recovery and Elemental X custom kernel, still encrypted with unlocked bootloader. I got the OTA (LMY47Z) notification and I have got the Factory Image as well as the OTA Zip. Can you guide me as to how can I update my Nexus (currently LMY47I) to 5.1.1 without losing any data?
Thanks.

The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.

peerpower said:
The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.
Click to expand...
Click to collapse
Download the OTA Zip, Extract it and check the "\META-INF\com\android\otacert" file to find the version number for your phone.

How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?

How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks

I wonder the same thing. I tried to get rid of the red triange but it's impossible. I've tried a full wipe and flash everything from stock but no dice.
Also i'm unable to boot to recovery. It just freezes... Same thing if I flash back the 5.1.1 image. TWRP is working though.
Any ideas?

Does anyone have a solution to get rid of the triangle WITHOUT twrp or root? I flashed TWRP to see if I could install a custom HOSTS file and the message started popping up on boot, but even after reflashing everything from the official M image and wiping data and cache it still pops up. Any suggestions? o_o

Did you flash userdata too? Tried factory reset on top?

pszyman said:
Did you flash userdata too? Tried factory reset on top?
Click to expand...
Click to collapse
I formatted userdata because I have a 64GB device and the userdata image included is for 32GB. this is what I did without the file names because I'm mobile:
Code:
Fastboot flash bootloader mboot.img
Fastboot reboot-bootloader
Fastboot flash mradio.img
Fastboot flash system msystem.img
Fastboot flash boot mboot.img
Fastboot flash recovery mrecovery.img
Fastboot format userdata
Fastboot format cache
And then I booted and got the device corrupt message. I did all of that a few times to make sure I didn't miss anything and I have no idea what it's detecting as modified. I haven't tried factory resetting from the device itself, I figured formatting userdata would be enough but ill try that tomorrow unless anyone has other ideas.

I had this same issue today too after I flashed twrp. The only way to resolve it was to flash stock and unroot using nexus toolkit to a lollipop stock image. In time I'm sure it will be a smoother process to go to android m with twrp and root, but until then, I'm sticking with lollipop.
Sent from my Nexus 6 using Tapatalk

530farm said:
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
Click to expand...
Click to collapse
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.

Well, the issue is this corrupted message stays even after the full stock reinstall. Some say it went away after the factory reset but returned back after a while later, after spontaneous reboot or so.

thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks

What I've done to get back to stock was - flash clean image and next factory reset. No corrupted message. So far so good.

I believe to get rid of it...you will have to lock and unlock bootloader again...which will factory reset in the process. Hopefully someone finds a workaround for a factory reset...I am going to continue to run it with the error message until someone does. I dont want to factory reset. The message doesnt cause any issues to my knowledge...its just a warning to the user.

dansoh said:
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Click to expand...
Click to collapse
kidhudi said:
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
Click to expand...
Click to collapse
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message

inspiron41 said:
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
Click to expand...
Click to collapse
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.

I flashed the kernel from here http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958 and it went away.

PhantomGamers said:
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
Click to expand...
Click to collapse
Custom kernels that have the flag edited out will will get rid of the Corrupt message.

djkinetic said:
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
Click to expand...
Click to collapse
I guess I'll have to resort to that if factory resetting doesn't fix it, sucks though cuz I would have been happy with stock.

Nexus 6 - Google splash screen boot loop after flash of 6.0 factory image (unlocked)

Hi,
I'm hoping for some suggestions regarding my boot looping Nexus 6. Here's the details:
- Brand new device.
- First boot & setup. OK.
- Unlocked bootoader. OK.
- Reboot back into 5.0. OK.
- Tried to flash 6.0, initially using flash-all.bat from shamu-mra58k-factory-5b07088c.tgz. Failed.
- Extracted zip inside shamu-mra58k-factory-5b07088c.tgz and flashed all .IMG manually.
- Phone now stuck in boot loop. Google logo appears, sits there for 5-10 seconds then reboots.
I so far have tried:
- Multiple reflashes of 6.0 factory image. Boot loop remains.
- Multiple flashes of 5.1.1 factory image. Boot loop remains.
- Tried flashing Cyanogenmod cm-12.1-20151021-NIGHTLY-shamu.zip via recovery. Flash successful. Boot loop remains.
- Flashing gpt.bin and reflash 6.0 images. Boot loop remains.
This is the first time I've encountered issues. I've successfully flashed factory images to my Nexus 4 many times over the
last couple of years.
Does anyone have any suggestions re a fix, if at all possible? Any tips/suggestions would be greatly appreciated!
If i need to return it, should I flash to 6.0 and lock? Will they be able to tell that the bootloader has
been unlocked previously?
Thanks!!

I recovered mine in a bootloop with wugfresh bootloop option ticked.
Sent from my Nexus 6 using XDA Free mobile app

yes, i do have a suggestion.. do not use flash-all. flash each partition individually. flaah-all is kinda broken and is not flashing the system.img.

Use this guide
http://forum.xda-developers.com/showthread.php?t=2954008
Use method two. As @simms22 said flash all is kinda borked on n6.
Sent from my Nexus 6 using Tapatalk

seeker02uk said:
I recovered mine in a bootloop with wugfresh bootloop option ticked.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Hi @Seeker02u,
I've tried that a couple of times, no luck. Thanks for the suggestion anyway!

Hi @toknitup420,
I've run through method two numerous times this week with no success. It's still gets stuck on the Google logo and reboots. Thanks for the suggestion and link.
toknitup420 said:
Use this guide
http://forum.xda-developers.com/showthread.php?t=2954008
Use method two. As @simms22 said flash all is kinda borked on n6.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse

Hi @simms22,
I've run through the flashing process manually flashing each .img individually a number of times now, all without success.
simms22 said:
yes, i do have a suggestion.. do not use flash-all. flash each partition individually. flaah-all is kinda broken and is not flashing the system.img.
Click to expand...
Click to collapse

davisco98 said:
Hi @simms22,
I've run through the flashing process manually flashing each .img individually a number of times now, all without success.
Click to expand...
Click to collapse
good, im glad that you finally got it

Uh hey hang on! I'm having the same problem, and I'm going to try your suggestion in lieu of a better option, but reread his reply. He said it DID NOT work for him. ("withOUT success")