Database Develop

[Q] Attempted to Downgrade and now bricked [solved]

First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
**EDIT**
If you have done the same bone-head move I made, then follow these simple steps.
1. Use RSD lite to update to 4.4.4
2. Follow this guide to then root your device once you have updated to 4.4.4
This works because your bootloader is unlocked, thanks to sunshine.

wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing system.img]
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.

wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
RSD 422 means a downgrade. What did it "say"?
Downgrading is the no no.
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
http://forum.xda-developers.com/showpost.php?p=55491148&postcount=10

samwathegreat said:
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing system.img]
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.
Click to expand...
Click to collapse
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
But I followed the rest of the directions and it still will only boot into fastboot.

wisenick said:
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
Click to expand...
Click to collapse
Did you really put spaces in between boot and loader? And Moto and boot?

samwathegreat said:
Did you really put spaces in between boot and loader? And Moto and boot?
Click to expand...
Click to collapse
No sorry, auto correct on the wife's phone.

wisenick said:
No sorry, auto correct on the wife's phone.
Click to expand...
Click to collapse
A "Permission denied" error sounds strange to me....don't recall having seen that one before.
Though I'm rather certain that your downgrade attempt (big no-no) is the culprit, I'm curious if @jcase might have any suggestions...

1) I don't think you are bricked, this should be fixable. This is due to you flashing older firmware to a device that has been updated, nothing to do with sunshine.
2) your title makes it sound like sunshine to blame, this is really bad for me. SunShine CANT brick motorola (nor htc) phones. We simply have too many safety checks, and verification. If you were able to flash and boot TWRP (which you were because you took a backup) then it can't be sunshine. It would be great if you changed the title to be more accurate.
Having said that, I have no problem helping you recover your phone, it certainly isn't bricked
I'm out from 10amPST to 2pmPST tomorrow, but please email me jcase AT cunninglogic DOT com, and I will have you up on your feet in minutes. Probably setup teamviewer and I will just remote in and do my best.
wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse

samwathegreat said:
Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.

jcase said:
...nothing to do with sunshine.
2) your title makes it sound like sunshine to blame...
Click to expand...
Click to collapse
That is what I first thought when I read the subject...
 @wisenick, you even mention in your OP you don't blame Sunshine, so why mention it in the subject?
Can you change the subject of this thread to "Attempted to Downgrade and now bricked" or "Attempted to downgrade and now phone wont boot"? That would be more accurate.

piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Just checked the XML and it is gpt then bootloader. I'll see if that fixes things.

Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.

Verttex said:
Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.
Click to expand...
Click to collapse
Thank you but I've tried that. It says that it flashed but when I try to boot into recovery it simply boots into fastboot

piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Double checked the order and according to the xml , its gpt first. However I still get an error when I try to flash motoboot

Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?

wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
If Sunshine unlocked your bootloader, you should be able to do whatever.

wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
Yes you lost root! but
If you used sunshine, you turned your consumer phone into a developer phone, meaning you will always be able to root it trivially and properly.

True. if your back in android w/o root
Download Supersu in a zip file
boot to bootloader
fastboot flash new recovery
reboot into the new recovery
flash supersu zip
you have root! Easy w/ an unlocked bootloader!

[Q] how to go back to stock kitkat??

Spice Dream UNO (Android One)
i have unlocked the bootloader of my spice dream uno, philz recovery and im running the 5.1 phillipines version (i think so) of android 5.1...
Can anyone make a guide on reverting back to the stock kitkat for my phone as i got it on my first day so i can make the official OTA update to android 5.1??
I searched for this but it seems after reverting the phone ends up with some IMEI problems. so im asking here to make a safe guide for people out there including me using SPICE DREAM UNO to have a safe return to kitkat so we can make the official 5.1 update.

I might help you
cybercop007 said:
Spice Dream UNO (Android One)
i have unlocked the bootloader of my spice dream uno, philz recovery and im running the 5.1 phillipines version (i think so) of android 5.1...
Can anyone make a guide on reverting back to the stock kitkat for my phone as i got it on my first day so i can make the official OTA update to android 5.1??
I searched for this but it seems after reverting the phone ends up with some IMEI problems. so im asking here to make a safe guide for people out there including me using SPICE DREAM UNO to have a safe return to kitkat so we can make the official 5.1 update.
Click to expand...
Click to collapse
See.... i know there might be many problems with SPflash tools to work with many users as u may have got many disappointments as i have got. I tried Running it but never get it done with sp flash tools... So i would tell you a fastboot method which you can do to restore your stock kitkat rom by some easy commands....
FIRST Of all ....
REQUIREMENTS:
1. You should have fastboot adb folder in ur pc...
2. STOCK ROM (sprout) google it you would find it in xda
PROCEDURE:
1. Go to fastboot mode in ur mobile (i presume that u know how to do that or if u don't know just google it)
2. Open the Adb fastboot folder
3. Press SHIFT+rightclick -> Open command window here
4. Copy the stock rom files into adb fastboot folder.
5. Check if your smarthphone is connected or not by typing: fastboot devices
6. Now perform these commands one by one:
fastboot format userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
fastboot flash cache cache.img
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot flash preloader preloader_sprout.bin
fastboot flash recovery recovery.img
fastboot flash secro secro.img
fastboot flash system system.img
fastboot flash userdata userdata.img
7. Now unlock your bootloader by typing: fastboot oem lock
or you could do this with All in one tool for our device
8. reboot ur device ... and voila..... it stock kitkat....

NO Update!!
bvipul said:
So i would tell you a fastboot method which you can do to restore your stock kitkat rom by some easy commands....
fastboot flash preloader preloader_sprout.img
Click to expand...
Click to collapse
its "fastboot flash preloader preloader_sprout.bin" anyway this method brought me back to kitkat. Thanks.
Now i go to about phone -> system updates and click "Check for update" it shows your system is up to date and the Last checked for update as the current time. Did Indian android ones(Spice dream uno) get lollipop update or not?? Why isn't the update available for me??

stage process
cybercop007 said:
its "fastboot flash preloader preloader_sprout.bin" anyway this method brought me back to kitkat. Thanks.
Now i go to about phone -> system updates and click "Check for update" it shows your system is up to date and the Last checked for update as the current time. Did Indian android ones(Spice dream uno) get lollipop update or not?? Why isn't the update available for me??
Click to expand...
Click to collapse
I think u didn't the procedure or have not seen the news about the update coz ..u should know that ..update procedure is not available for all right now..
It is in a weekly manner...they are giving updates to a small number of users right now...but there is a news that....every android one devices would get updated by the new lollipop till 23rd of march...so wait for it for some more time......

Lollipop??
bvipul said:
See.... i know there might be many problems with SPflash tools to work with many users as u may have got many disappointments as i have got. I tried Running it but never get it done with sp flash tools... So i would tell you a fastboot method which you can do to restore your stock kitkat rom by some easy commands....
FIRST Of all ....
REQUIREMENTS:
1. You should have fastboot adb folder in ur pc...
2. STOCK ROM (sprout) google it you would find it in xda
PROCEDURE:
1. Go to fastboot mode in ur mobile (i presume that u know how to do that or if u don't know just google it)
2. Open the Adb fastboot folder
3. Press SHIFT+rightclick -> Open command window here
4. Copy the stock rom files into adb fastboot folder.
5. Check if your smarthphone is connected or not by typing: fastboot devices
6. Now perform these commands one by one:
fastboot format userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
fastboot flash cache cache.img
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot flash preloader preloader_sprout.bin
fastboot flash recovery recovery.img
fastboot flash secro secro.img
fastboot flash system system.img
fastboot flash userdata userdata.img
7. Now unlock your bootloader by typing: fastboot oem lock
or you could do this with All in one tool for our device
8. reboot ur device ... and voila..... it stock kitkat....
Click to expand...
Click to collapse
for flashing stock lollipop rom the commands and the procedure are same?? since i find some more extra files are present in the stock rom folder i was wondering whether there is a difference between the kikkat stock flashing procedure and lollipop procedure.

cybercop007 said:
Spice Dream UNO (Android One)
i have unlocked the bootloader of my spice dream uno, philz recovery and im running the 5.1 phillipines version (i think so) of android 5.1...
Can anyone make a guide on reverting back to the stock kitkat for my phone as i got it on my first day so i can make the official OTA update to android 5.1??
I searched for this but it seems after reverting the phone ends up with some IMEI problems. so im asking here to make a safe guide for people out there including me using SPICE DREAM UNO to have a safe return to kitkat so we can make the official 5.1 update.
Click to expand...
Click to collapse
Just flash the stock rom via the flash tools no worries

[Q] Unable to upgrade rooted Nexus 6 to 5.1.1

I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin

rambo8wtv said:
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
Click to expand...
Click to collapse
no matter how many times you try, you will never ever be able to update your rooted n6 via ota. if any system files changed from stock, an ota will download but will always error out. you can update several ways.. a. you can flash a 5.1.1 ROM via twrp. or b. you can fastboot flash 5.1.1.

2 things.
1. You must be 100% stock, no root, no custom recovery to OTA
2. The 5.0.2 message if you look probably.mentions deestroy..this is.because TWRP is using 5.0.2 sources - butnits irrelevant anyway give point 1

I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?

rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
twrp can not flash the ota or system img. you flash the system img via fastboot(not adb) and while you're in your bootloader.

rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
You cannot use the OTA file no matter what vehicle you use.

danarama said:
You cannot use the OTA file no matter what vehicle you use.
Click to expand...
Click to collapse
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data

starfish_001 said:
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
Click to expand...
Click to collapse
He'll probably want to not flash recovery. And if he has a custom kernel, may not want to flash boot either.

Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.

rambo8wtv said:
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
Click to expand...
Click to collapse
here too, many people try it with adb then claim it doesn't work. but its fastboot that you need, and while you are in the bootloader. adb will never work in the bootloader, only fastboot.

Updating from 5.1.1 to 6.0

Lol. I'm totally lost. I usually don't make these types of threads. I'm trying to update to 6.0. I'm assuming I would need to update the Bootloader to 6.0 before hand. How would I go about doing so? Would I need to flash the factory images straight from google? ?Currently running 5.1.1 dirty unicorns v9.8. Thank you.

houstonsveryown said:
Lol. I'm totally lost. I usually don't make these types of threads. I'm trying to update to 6.0. I'm assuming I would need to update the Bootloader to 6.0 before hand. How would I go about doing so? Would I need to flash the factory images straight from google? ?Currently running 5.1.1 dirty unicorns v9.8. Thank you.
Click to expand...
Click to collapse
So, what you wanna do is download a stock image for the version of Android you're trying to flash, make SURE it's for your device! And assuming you know where to get fastboot and how to use the tool correctly, enter these commands!
fastboot flash bootloader bootloader[press tab]
fastboot reboot-bootloader
fastboot flash radio radio[press tab]
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format userdata
fastboot format cache
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot reboot
EDIT: Also worth noting that flashing system.img takes a few minutes, it may seem to hang, this is normal!
Sent from my Nexus 6

Okay. I appreciate that!! I just wanted to make sure I was taking the right steps to do so lol. Thank you!!

H4X0R46 said:
So, what you wanna do is download a stock image for the version of Android you're trying to flash, make SURE it's for your device! And assuming you know where to get fastboot and how to use the tool correctly, enter these commands!
fastboot flash bootloader bootloader[press tab]
fastboot reboot-bootloader
fastboot flash radio radio[press tab]
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format userdata
fastboot format cache
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot reboot
EDIT: Also worth noting that flashing system.img takes a few minutes, it may seem to hang, this is normal!
Sent from my Nexus 6
Click to expand...
Click to collapse
Okay so is flashing the latest 6.0 MRA58X okay? I'm on AT&T by the way.

houstonsveryown said:
Okay so is flashing the latest 6.0 MRA58X okay? I'm on AT&T by the way.
Click to expand...
Click to collapse
The latest Android version is 6.0.1. But if you want to flash that version, it's fine! As long as you make sure it's for your device! If you're using a Nexus 6, make sure it's for the "shamu"! And glad I could help! No problem!

H4X0R46 said:
The latest Android version is 6.0.1. But if you want to flash that version, it's fine! As long as you make sure it's for your device! If you're using a Nexus 6, make sure it's for the "shamu"! And glad I could help! No problem!
Click to expand...
Click to collapse
okay last thing. will the old root method still work on 6.0?

houstonsveryown said:
okay last thing. will the old root method still work on 6.0?
Click to expand...
Click to collapse
For 6.0, you will need a custom kernel. In short, Google added these "system is corrupt" messages to their stock kernels for Android 6.0, you will need a custom kernel. I used elementalx personally, you can get that at elementalx.org if you choose to, for Android 6.0.1, that's a different story. Let me know if you need any other help on this! PM me if you need to!

While upgrading from 6.01-7.0 crashed at 83% Now Stuck at Google logo image w/Unlock

Any help appreciated here, I have been searching the forums all morning, but haven't found the same issue as mine (lots of stuck at google ?'s but none from failed upgrade) last night I decided to take the plunge and update my N6 from build 6.0.1 (MOB31H, Oct 2016) to 7.0.0 (NBD90Z, Oct 2016)
I typically use the WugFresh NRT to upgrade via factory image. Last night I decided to give the OTA images a try.
Everything was going smoothly until I bumped my keyboard tray and my phone became disconnected while still flashing. It was almost done too.....it was at the point of flashing the system image and was interrupted at 83% and it failed install.
I then attempted to recover from this by flashing entire factory image for 7.0 but it doesn't seem to want to mount my device. I then tried to go back and flash 6.01 to device using the softbrick/bootloop function from the NRT toolkit. It seemed to partially work as the size of the word google on the screen changed during boot went smaller (so I assume the boot.img was able to flash?) but I am still stuck at the google logo with the unlock at the bottom. Bright side is device is bootloader unlocked.
If I try the recover from bootloop function on the NRT it seems to have trouble sending files to phone (goes through all the process just doesn't take it looks like it sending files but before each at beginning it doesn't seem to connect to device.
I can access bootloader, and recovery. In recovery I tried to wipe/cache (wipes but doesn't help), tried factory reset (wipes but still stuck at Google), tried to mount system through selecting via recovery and it fails.
Not sure which image I should try to flash now to recover 6.01 or 7.0 or if I can even recover from this? Any suggestions are appreciated.
When I first got my phone I did create a backup using the NRT but that was on I think 5.0 or 5.01 and I no longer have twrp installed, should I try putting twrp on it and restoring that back up? It was a long time ago and I am not sure if it will cause radio or boot img issues...since I have upgraded so far past without making another backup with a newer version.
I have read that some others with similar issues that were told to use the N beta to get a clean flash.....only issue is there is no longer a N beta for Nexus 6......it now only shows 7.01 for 6p, 5x, and pixel.
Should I try flashing twrp and a ROM? And after see if I can get to load that way then go back and flash stock image?
Any help or suggestions are appreciated.

On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit

Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
just a silly question really , can this work on on a locked bootloader /not rooted device ?

touns_j said:
just a silly question really , can this work on on a locked bootloader /not rooted device ?
Click to expand...
Click to collapse
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.

wavechapter said:
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
Click to expand...
Click to collapse
alright , i thought twrp could be replaced with stock recovery

Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
Thank You Dirty_Jerz! I really appreciate the help.
I am now back up and running on 7.0!