Database Develop

[HOW TO] Safely Update Your Radio For Froyo Using Fastboot

UPDATING YOUR RADIO
IMPORTANT - READ ALL OF THIS POST​
I originally wrote this post for Kang-o-rama but, considering everybody will need to update their radio at some stage, though I would x-post it here. Hopefully a mod will sticky, at least for the next three or four weeks.
You phone is designed to support updating the radio image. The radio image is primarily used to control the mobile communication of your phone. Other functions are sometimes offloaded to the radio cpu including, in the case of the Nexus, some video processing. Because of the codependencies between the radio, the kernel and the rom, it is occasionally necessary to update your radio.
Froyo (Android 2.2) requires a new radio and so does CyanogenMod 6.0 and Kang-o-rama 1.0.
Updating your radio is safe if you do it properly and carefully. It is very unsafe if you do not. One of the consequences of a failed radio update is a bricked (useless) phone. This risk is not the same when updating a kernel or a rom.
To update your radio to a suitable version for Kang-o-rama 1.0, Froyo or CyanogenMod 6.0 using fastboot follow the following instructions below carefully. The scope of this guide does not extend to getting fastboot working on your computer and your phone connected. Please see the sticky threads in this forum and search for additional information if you are unsure.
Fully charge your phone
Download the radio image from the link below
Compare the MD5 checksum of the file you downloaded with the one printed below. This is very important, please do it. For Windows or OSX you can use the free HashTab application.
Connect your phone to your computer
Reboot your phone into the bootloader (fastboot mode)
At the command prompt on your computer type: fastboot devices
A value like HTXXXXXXXXXXX should be displayed with the word fastboot next to it
Your phone screen should have FASTBOOT USB on it
If all of the above is not exactly as described DO NOT PROCEED and resolve your fastboot problem
To proceed, make sure your downloaded file is in your current directory
At the command prompt type: fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img - you must type it correctly!
Now, observe the computer and be patient TOUCH NOTHING!!
The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
Watch the little indicator at the top of your phone screen.
Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
Then, and only then, reboot your phone.
Your phone should reboot to your normal home screen and you should get a mobile connection.
Remember, if you're still using an older rom some things won't work. Best you now upgrade to Kang-o-rama 1.0!
Download: froyo-radio-32.36.00.28U_4.06.00.02_2.img
MD5 Checksum: 3321c196d8ec1cf748fd20c3c4068520
Take care.

Reserved for who only knows what...

Is there a zip file that can be downloaded to the N1? I don't have access to a computer,at least not for awhile.

after the cmd says writing radio it finishes and my phone stays on the fastboot screen. I can use the volume buttons to move the selector and reboot but the radio on the fastboot screen still says RADIO-4.06.00.12.7

when u use fastboot , it doesnt reboot itself n u have to reboot it urself and after it has flashed in fastboot u are safe to do anything but only after the red bar on the top right corner disappears. Red one comes after green one. Then u have to type fastboot reboot or use the menu to reboot. It will do nothing magical after than but boot straight to the system. U mixed up recovery flashing and fastboot

how about flash via Recovery ? I think its safer and much more convenient

U r most probably gonna f up using recovery. My experience some days ago with my cliq lol

cronin4392 said:
after the cmd says writing radio it finishes and my phone stays on the fastboot screen. I can use the volume buttons to move the selector and reboot but the radio on the fastboot screen still says RADIO-4.06.00.12.7
Click to expand...
Click to collapse
I'm having this same exact issue. I followed the instructions exactly all the way to reboot.
It's weird because the 720p mod works fine afterwards where before it would crash the phone when trying to record or open the camera settings.

Man please someone anyone help me. i have done exactly what the steps say and fastboot wont comply. all i get is C:\Users\Whoisc_walk>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.
img
error: cannot load 'froyo-radio-32.36.00.28U_4.06.00.02_2.img'
im not really sure what i did wrong. i think it may be the directory but as far as i know its in the correct one. so im getting frustrated so im asking for help
figured it out it was a directory problem

C_walk said:
Man please someone anyone help me. i have done exactly what the steps say and fastboot wont comply. all i get is C:\Users\Whoisc_walk>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.
img
error: cannot load 'froyo-radio-32.36.00.28U_4.06.00.02_2.img'
im not really sure what i did wrong. i think it may be the directory but as far as i know its in the correct one. so im getting frustrated so im asking for help
figured it out it was a directory problem
Click to expand...
Click to collapse
Have to be in the directory where fastboot is.. from there you can flash the Radio.

I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s

silentfishwm said:
I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s
Click to expand...
Click to collapse
Try downloading the img again, check the MD5.
Also make sure your battery is fully charged.

djmcnz, thanks for your help, I double checked the MD5, it's correct and the phone was fully charged. Any other possible cause of this error?
djmcnz said:
Try downloading the img again, check the MD5.
Also make sure your battery is fully charged.
Click to expand...
Click to collapse

silentfishwm said:
djmcnz, thanks for your help, I double checked the MD5, it's correct and the phone was fully charged. Any other possible cause of this error?
Click to expand...
Click to collapse
You are running a rooted phone with a custom recovery image correct?

silentfishwm said:
I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s
Click to expand...
Click to collapse
Is your bootloader unlocked? Or did you root without unlocking the bootloader?
________________________
N1 w/ XDA App

Ooopps.... I'm using a rooted phone with locked bootloader, I'm an idiot
Is there anyway for my phone to make a radio update?
djmcnz said:
You are running a rooted phone with a custom recovery image correct?
Click to expand...
Click to collapse

J.L.C, yes I rooted my phone without unlocking the bootloader...
Any way to update radio in such case?
J.L.C. said:
Is your bootloader unlocked? Or did you root without unlocking the bootloader?
________________________
N1 w/ XDA App
Click to expand...
Click to collapse

silentfishwm said:
J.L.C, yes I rooted my phone without unlocking the bootloader...
Any way to update radio in such case?
Click to expand...
Click to collapse
In that case you have to update the radio though recovery with a zip file.
________________________
N1 w/ XDA App

Thanks J.L.C., I have got the radio updated with an update.zip
J.L.C. said:
In that case you have to update the radio though recovery with a zip file.
________________________
N1 w/ XDA App
Click to expand...
Click to collapse

I have an unlocked g1 for at&t if I update the radio will I have to unlock it again

List of Updates / Firmware for the HTC One (Sprint Varient)

Hey everyone, even though I dont have this device I figured it'd be good to have this thread so I'll start it.
This thread will contain all zips / firmwares for the device as well as changelogs if anyone wants to supply it. The zips will be flashable through bootloader not through recovery (I dont want to deal with the issues of "Well I bricked it because my recovery locked up" or however the hell you manage to break it.)
Download links:
M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7 Firmware zip
Code:
Changelog for 1.29.651.10
- BlinkFeed improvements
- New Sprint Zone client
- Improved Back and Home key sensitivity
Any more files someone wants to provide feel free to PM me or post them here.

Is this the ota that's flashable for us rooted people
Sent from my HTCONE using Tapatalk 2

It's the firmware to flash through bootloader....

Thanks.
Sent from my Nexus 10 using Tapatalk HD

Is this safe for root or is this just a manuel upload instead of waiting for the OTA?

Should we flash the firmware or is it
Ok to just wait for a rooted Rom to be made with the new firmware and just flash that. I guess my question is are we going to be missing any key components by not taking it directly from HTC like newer radios
Sent from my HTCONE using xda premium

Nice to see you here Noob.
And it's OTAs. Official updates.
D3rped out Beastmode! HTC ONE!

gonowhere said:
Is this safe for root or is this just a manuel upload instead of waiting for the OTA?
Click to expand...
Click to collapse
fastboot oem rebootRUU
fastboot flash zip FIRMWARENAME.zip
fastboot reboot
Just installs new firmware for you. Doesnt actually affect your rom. Will wipe recovery though because there is no s-off.
dandan2980 said:
Should we flash the firmware or is it
Ok to just wait for a rooted Rom to be made with the new firmware and just flash that. I guess my question is are we going to be missing any key components by not taking it directly from HTC like newer radios
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
You flash the firmware because I believe the boot.img and tp.img are new. Haven't checked because I dont have an image dump to compare. But without s-off we cant flash selectively.
thronnos said:
Nice to see you here Noob.
And it's OTAs. Official updates.
D3rped out Beastmode! HTC ONE!
Click to expand...
Click to collapse
Still don't have a phone though. Kinda bums me out but because I got fired I can't afford the upgrade now. :/
And I'm less of a newb than you

So we can flash this through CMD WITHOUT HAVING STOCK RECOVERY. It will just erase twrp and we need to reflash twrp again??? Then flash stock rooted.
Sent from my HTCONE using xda premium

Dev-Host is borked

First of all, thank you for sharing it! I was waiting for CyanogenMod to update their ROM but they haven't yet.
I clicked on the link but it doesn't download the file after clicking on "download"
Any advice?
Thanks!

chamo311 said:
I clicked on the link but it doesn't download the file after clicking on "download"
Any advice?
Thanks!
Click to expand...
Click to collapse
Mine took me to a page not found the first time, but refreshing the page worked. Also, make sure you're clicking the right "download" button, as I had a couple ads with larger download buttons related to the ads.
Now my turn for a question. I tried flashing it and it failed. Anyone have an idea why? Here's what fastboot reported:
Code:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.063s
C:\Android>fastboot flash zip M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7
-Firmware.zip
sending 'zip' (15538 KB)...
OKAY [ 1.809s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.059s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.044s
No harm done, but I'm still on 1.29.651.7

Thanks! I downloaded it!
Hmmm no idea, I haven't flashed mine yet....I'm away from a computer. I'll let you know.
Thanks again!

kzibart said:
Mine took me to a page not found the first time, but refreshing the page worked. Also, make sure you're clicking the right "download" button, as I had a couple ads with larger download buttons related to the ads.
Now my turn for a question. I tried flashing it and it failed. Anyone have an idea why? Here's what fastboot reported:
Code:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.063s
C:\Android>fastboot flash zip M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7
-Firmware.zip
sending 'zip' (15538 KB)...
OKAY [ 1.809s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.059s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.044s
No harm done, but I'm still on 1.29.651.7
Click to expand...
Click to collapse
when you get that error just retype the fastboot flash command again immediately after you recieve the error and it should go then.

Aldo101t said:
when you get that error just retype the fastboot flash command again immediately after you recieve the error and it should go then.
Click to expand...
Click to collapse
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.

kzibart said:
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
Click to expand...
Click to collapse
Have you checked the MD5 of the .zip?

kzibart said:
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
Click to expand...
Click to collapse
YES, i tried this also and got the same results.

Aldo101t said:
YES, i tried this also and got the same results.
Click to expand...
Click to collapse
Same here......FAILED for me too

aschlect said:
Same here......FAILED for me too
Click to expand...
Click to collapse
Are you guys SuperSu instead of Koush's Superuser?

jaytv said:
Are you guys SuperSu instead of Koush's Superuser?
Click to expand...
Click to collapse
Yes, I am SuperSU

HELP! Only have bootloader access!

So like a moron I installed ViperRom 5.0 with regular old CWM. Now as a result I'm stuck at the bootloader with no access to recovery.
I have no idea what to do now. PLEASE HELP!!!!
S-ON
Hboot 1.55.0000

Can you not boot into recovery from the boot loader or reboot and hold the volume down button?
Sent from my HTC One Max using Tapatalk!

gimmeitorilltell said:
Can you not boot into recovery from the boot loader or reboot and hold the volume down button?
Sent from my HTC One Max using Tapatalk!
Click to expand...
Click to collapse
I only have access to my bootloader......can't get into recovery or boot into the rom.
My terminal window keeps hanging on "waiting for device" so I don't think USB Debugging was enabled.....
The only thing that is looking bright is that my computer is recognizing my phone in Fastboot.
I'm completely clueless on what to do now.....
Please anyone help

Maybe try flashing recovery again?
Sent from my HTC One Max using Tapatalk!

Does it say fastbootusb? If not press the power button to select fastboot.

BD619 said:
Does it say fastbootusb? If not press the power button to select fastboot.
Click to expand...
Click to collapse
I can get to fastboot USB but from there I'm honestly lost...

nickhernandez said:
I can get to fastboot USB but from there I'm honestly lost...
Click to expand...
Click to collapse
I can help you remotely PM if interested

i'm in the same boat, but when I go to flash another recovery in fastboot my phone freezes after it fails to flash.
sending 'recovery' (9786 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Then my phone freezes and I have to reboot into bootloader.
Never mind solved it.

Morghan said:
i'm in the same boat, but when I go to flash another recovery in fastboot my phone freezes after it fails to flash.
sending 'recovery' (9786 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Then my phone freezes and I have to reboot into bootloader.
Click to expand...
Click to collapse
I had to run RUU to fix mine

[Q] N6 is just DEAD,,, NOT OPERATING AT ALL(HELP!)

Hello, everyone.
So, about an week ago, I posted a thread to ask for your help regarding my broken N6. Since then, nothing has changed(but got worse, I guess...?). Here is what is happening with my N6 right now.
1) It powers up(thank god) but goes straight to the boot-loader screen(I believe this means that my device doesn't have system image file within the device)
2) On boot-loader menu(Start, Restart bootloader, Recovery mode, Power off, Factory, Barcodes, BP Tools, QCOM, Bootlaoder logs), only few are working(Restart bootlodaer, Power off, Barcodes). When I try to perform other than these, it just goes back to main boot-loader screen.
3) I tried to use both Nexus Root Tool kit and manual installation of each image but doesn't work for both of them(From this, I believe that my phone is just BROKEN)
With this happening, conclusion that I can think of is
1) There is no 'Recovery' available in my device(that's why I can't do anything to recover my device)
2) ADB is not functioning.
Only solution that I can think of from this point is that contact Motorola and replace my device(which is what I am currently doing but Motorola has huge problem with their customer service that I am waiting for their answer for about 2 weeks now)
If possible, would there other options that I can repair this device by myself?
I appreciate your attention.
Sincerely.

Adb has no impact on bootloader. What do you mean doesn't work when you fastboot the factory image?
Sent from my Nexus 6 using XDA Free mobile app

your problem is the use of toolkits. stay away from them, unless you know what you are doing!
your phone doesnt have any rom on it. you can.. 1. flash the factory img via fastboot, like you are supposed to do(not via a toolkit), or 2. unlock the bootloader, flash a custom recovery then while in the custom recovery adb push a rom, gapps, and supersu and flash them that way. what you did does not give you the right for a trade in.

The two previous posters are correct. You just need to fastboot flash the factory rom and factory recovery. It is fairly simple, if you take the time to read how to do it. There are posts all over XDA for beginners on how to do this. And I cannot stress how correct @simms22 is. Toolkits may seem to make things easy, but when there is a problem, you need to know how to manually fix it. I just personally stay away from toolkits. And I was in your shoes. I didn't know jack about flashing roms and such. Just reading XDA got me to where I am. (and i am still learning!)

Like the others have pointed out, you are fine. You have access to your bootloader screen, this is a Nexus. Take a deep breath. Take some time and read this site about flashing a factory image. Please do it the best way - manually with fastboot commands. If you get stuck come back here and someone will help. It really is easy. Please repeat after me "I will avoid all toolkits from now one".
Start with this and read lots.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Flashing the factory image should still work from boot loader with fast boot.
Follow the second link for manual flashing after downloading the zip from the first link.
https://developers.google.com/android/nexus/images
If you run into the missing system.img problem here is the link to fix it:
http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/
This way you can start from the beginning.

Problem with flashing factory image manually.
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.

chg911225 said:
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.
Click to expand...
Click to collapse
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?

simms22 said:
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?
Click to expand...
Click to collapse
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s

chg911225 said:
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s
Click to expand...
Click to collapse
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.

simms22 said:
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.
Click to expand...
Click to collapse
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s

​
chg911225 said:
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s
Click to expand...
Click to collapse
i have no idea, but this is a good thread to read and post questions about fastboot in http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500

RIP. What did you do to your N6?

OP how did you install your fastboot. I would assume you did it from within a toolkit. That is probably your problem. If that is the case, please do this. Go here and install the .exe: http://developer.android.com/sdk/index.html#Other
It's big I know it but just do it please.
Make sure everything (SDK) gets installed in a folder path like c:\android or something you will easily remember. This is very important because it is within this folder you will place the extracted factory image files (.img). Place all full unzipped .img files in this folder.
Please follow method #2 in this excellent guide:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

zetsumeikuro said:
RIP. What did you do to your N6?
Click to expand...
Click to collapse
One day it just shut down by itself and since then it's like this. I just contact Motorola and they are going to ship me new device with different color(idk y they are still having problem with their stocking their devices in because what I had was Cloud White 32Gb but only model that were present when I contact them was Midnight blue with 32Gb, other options are all out of stock. really wished they had a white color...)

This phone is a damn Nexus, it can't die. It's user error.
Sent from my Nexus 6

Broke the Bootloader???

Long time lurker first time poster, but I need help!!!
Getting tired of waiting for my OTA 7.11 and after a long night at work decided rather than just manually flashing the file that I would use the NRT. I must've encountered an error as it left me in Fastboot so I try to manually flash everything with it being stuck on the "Google" pre-boot screen. I try again with the version that I was on prior to update (NBD91X) and still the same results. Looking at the log from my Command Prompt I notice upon flashing the bootloader I have this error:
sending 'bootloader' (4071 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
(bootloader) Motoboot: invalid GPT
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.408s
I am only able to boot into Fastboot and unable to boot into Recovery. What are my options to getting my N6 back?
Thank you all for the help.

Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!

5.1 said:
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
Click to expand...
Click to collapse
Thanks for your reply. Even after getting a fresh download of adb/fastboot files I'm still encountering this error when trying to flash the bootloader;
c:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
c:\Users\matt\Downloads\platform-tools>fastboot flash bootloader C:\Users\matt\D
ownloads\platform-tools\shamu-n6f26r\bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
(bootloader) Motoboot: Preflash validation for aboot
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.433s
Any other suggestions?

bootloader is locked correct?

SynisterWolf said:
bootloader is locked correct?
Click to expand...
Click to collapse
The bootloader has been unlocked from the day I took it out of the box. I still have the little "unlocked" icon at the bottom of the "Google pre-boot" screen that it stays stuck at when I try to boot the phone.

Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry

5.1 said:
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
Click to expand...
Click to collapse
I just issued the command and got this back:
C:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
C:\Users\matt\Downloads\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
I hope I'm not screwed like the thread you suggested. At this point if I could just get a fresh install I'd be happy with that. Otherwise I guess I could start looking for an N6 replacement...I've put my sim card in my old MotoX 2013 and boy is this phone smaller than I remember.
AGGHHHHH!!! Thanks for your help and please let me know if there is anything else you could suggest for me to try.

Try: fastboot getvar all
Paste the result. Just hide you imei...

5.1 said:
Try: fastboot getvar all
Click to expand...
Click to collapse

I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????

coremania said:
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
Click to expand...
Click to collapse
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.

the200sx said:
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
Click to expand...
Click to collapse
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335

coremania said:
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
Click to expand...
Click to collapse
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks

Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...

5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
I'll give it a shot

the200sx said:
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Click to expand...
Click to collapse
Ok, I didn't remember this right, the developer preview ota sideloading with adb was for fixing the Google ota update which bricked some devices as the n previews were released.
But you have nothing to loose, so you may try to do this. Here's a working download in the link, if you don't sideloading the userdata your data may stay intact. https://www.reddit.com/r/nexus6/comments/49txh3/bricked_nexus_6_after_android_n_ota_update_stock/

5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
It looks like it pushed the TWRP recovery but I still can't seem to get it to boot it into recovery. Only the main fastboot screen pops up trying to Power + Vol and when I VOL select it recovery, it will just reboot back to the main fastboot screen.

Damn... Try:
fastboot erase cache
And try to boot in twrp again?

5.1 said:
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
Click to expand...
Click to collapse
That didn't work either. However it made it take a split-second longer to restart, which gave me a moment of hope. Hope Crushed!!!

Last question... When you power your phone, does it stay on Google logo, or boot animation forever? Or directly bootloader?
If one of the first two, is the phone detected on your computer device manager? If yes, how?