Database Users

[HOW-TO] bootloader unlock 4.67.651.3 OTA

1. Unlocking bootloader via htcdev.com (selecting All Other Supported Models)
2. Flashing recovery via fastboot (./fastboot flash recovery cwm-4.0.1.4-supersonic.img)
3. Reboot recovery and flash latest su.
4. Profit.
PROOF:
Code:
[email protected] ~/evo_s-off $ ./fastboot oem get_identifier_token
< waiting for device >
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
===========bla-bla-bla=============
---checking my e-mail for Unlock_code.bin---
[email protected] ~/evo_s-off $ ./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully
OKAY
[email protected] ~/evo_s-off $ ./fastboot flash recovery cwm-4.0.1.4-supersonic.img
sending 'recovery' (3074 KB)... OKAY
writing 'recovery'... OKAY

this is very strange. nobody interested in unlocking bootloader?

there is no official info, but works fine for me.

I'm one of the ones on the newest ota. This helps out a lot, thank you

I already have root, but I am rooting someone else's phone that has new hboot. Thanks!
Sent from my PC36100 using Tapatalk

people with unlocked bootloaders please leave comments here.

Total noob mistake.
OK i ended up updating my evo to the new 4.67.651.3 update. big mistake
I ended up stumbling across this post. (thx wardriva)
I was able to unlock the bootloader and use the ADB method mentioned in this thread to flash recovery.
after looking around I came across brad560's thread and flashed the deodex'ed rom with no problems.
so far everything is working. I also kept looking around and came across the Collection Project (thx Tommytomatoe) and flashed the hot spot hack by SOS. so far its working.
still looking to see if someone has found a workaround with the S-OFF or if revolutionary will support it.
Thx to all the DEV's.

wardriva said:
this is very strange. nobody interested in unlocking bootloader?
Click to expand...
Click to collapse
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)

coldroy said:
still looking to see if someone has found a workaround with the S-OFF or if revolutionary will support it.
Click to expand...
Click to collapse
you don't need S-OFF with unlocked bootloader. you can flash any rom you want with any kernel you wish. i just checked.

Tekn010933 said:
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)
Click to expand...
Click to collapse
what are you talking about? the latest OTA let us unlock bootloader.

wardriva said:
what are you talking about? the latest OTA let us unlock bootloader.
Click to expand...
Click to collapse
my fault, apologies reading to fast and totally thinking rooting instead unlocking??lol!

hmmm. From the little bit I had read on Evo 3d forum, I thought that even with unlocked bootloader, s-on means no flashing of kernels? Or maybe it's different on 3d cuz it uses EMMC ? Does a custom kernel remain after reboot?
Would love clarification from anyone who knows better than I. Thanks.
Also, this comes just in time for evos EOL status lol. Coincidence ?
Sent from my PC36100 using xda premium

Can you still write to the system or uninstall bloatware with the unlocked bootloader (which is still S-ON)?

To answer some people's questions unlocking with the HTC tool allows you to write to boot(kernel), recovery, and system. This means you can flash custom recovery and ROMs to your hearts content. You will still require official HTC signed updates to change: bootloader, radio, nv, pri, wimax, etc because technically you are still S-ON.
Here is the FAQ from HTC on unlocking the bootloader: http://htcdev.com/bootloader/faq
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse

shortydoggg said:
Can you still write to the system or uninstall bloatware with the unlocked bootloader (which is still S-ON)?
Click to expand...
Click to collapse
Just curious about the new bootloader, because based on past bootloaders I've had,
If you are rooted, but still S-ON, you can delete any bloatware (system apps) that you want, but after rebooting the phone it all returns. Why, because there is a backup of how your partitions were on the phone that cannot all be flashed unless you are S-OFF. When you're S-ON, any changes you made to the original partitions, (especially recovery and system if system is done inside the operating system) will be voided the next time you reboot the phone. That is also why you would need to connect your phone to your computer every time you needed to flash a custom ROM (if this is still the case with the new bootloader), because the backup (stock Recovery) is always restored on reboot.
You can change the system partition outside of the operating system by recovery, however; which is the reason why you can still flash custom ROMs (if the new bootloader behaves the same as the older ones).
I'm just curious if anyone with the new (unlocked) bootloader with S-ON can confirm this.

shortydoggg said:
Just curious about the new bootloader, because based on past bootloaders I've had,
If you are rooted, but still S-ON, you can delete any bloatware (system apps) that you want, but after rebooting the phone it all returns. Why, because there is a backup of how your partitions were on the phone that cannot all be flashed unless you are S-OFF. When you're S-ON, any changes you made to the original partitions, (especially recovery and system if system is done inside the operating system) will be voided the next time you reboot the phone. That is also why you would need to connect your phone to your computer every time you needed to flash a custom ROM (if this is still the case with the new bootloader), because the backup (stock Recovery) is always restored on reboot.
You can change the system partition outside of the operating system by recovery, however; which is the reason why you can still flash custom ROMs (if the new bootloader behaves the same as the older ones).
I'm just curious if anyone with the new (unlocked) bootloader with S-ON can confirm this.
Click to expand...
Click to collapse
S-ON + Locked means that all partitions(other than data / sdcard) are write protected. The only way to write to the partitions is with an official OTA or RUU signed by HTC. The reason why "deleted" items return after reboot is because the deletion never actually occurred on the partition itself. It was temporary because the write was blocked by the security.
S-ON + Unlocked means that HTC removed the write protection from: boot, recovery, and system.
For HTC's official FAQ see my post immediately before yours.

illogos said:
To answer some people's questions unlocking with the HTC tool allows you to write to boot(kernel), recovery, and system. This means you can flash custom recovery and ROMs to your hearts content. You will still require official HTC signed updates to change: bootloader, radio, nv, pri, wimax, etc because technically you are still S-ON.
Here is the FAQ from HTC on unlocking the bootloader: http://htcdev.com/bootloader/faq
Click to expand...
Click to collapse
Or get a stock(4.67-Android 2.3.5) ROM that has -Signature Verification disabled which will allow you to update the radios and such.
Is how it use to be done

.Elite_The_King. said:
Or get a stock(4.67-Android 2.3.5) ROM that has -Signature Verification disabled which will allow you to update the radios and such.
Is how it use to be done
Click to expand...
Click to collapse
thanks Cap. but I was not rooted before OTA. and after OTA there is no other way to root or flash custom ROM.

WIP Guide for achieving S-OFF after unlocking Bootloader with HTCDev.com
[GUIDE][WIP] How to achieve S-OFF after unlocking 2.18 HBOOT with HTCDev.com - No More Watermark! )
Still working on the details, but a shell of the instructions is there .

Tekn010933 said:
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)
Click to expand...
Click to collapse
DISCLAIMER: I'm a noob in this root world.....and enjoying the freedom to use my phone as I choose.
With that said, if you do not recommend updating OTA, then how would a person do such? I'm asking for my friends who are run stock on their phones.

[REQ][deb]Bootloader version for JSR78D (N7 LTE)

Like topic states, I would like the bootloader version of JSR78D.
Here's how to check:
turn device off
hold down power and volume down until fastboot screen appears
version should be in bottom left of screen
Preferably I would like to also request a nandroid and dump of the bootloader, but having just the bootloader version will do.
If you've already updated to JSS15J: I already know the bootloader version for that, I dont need it again.

Just to add to the original post, all N7 LTE devices ship with JSR78D out of the box and you will get an update to JSS15J after you boot it for the first time. You will need to get the bootloader information before performing that first OTA update. Thanks!
Sent from my Galaxy Note 8.0 using Tapatalk 4

Mine is FLO-03.14, I have the LTE version and already updated to the latest OTA update.

nex86 said:
Mine is FLO-03.14, I have the LTE version and already updated to the latest OTA update.
Click to expand...
Click to collapse
Thanks but we need the bootloader version from before it was updated. Thanks anyway.
Sent from my Nexus 7 using Tapatalk 4

Just a friendly bump...

My LTE (deb) was shipped with JSS15J in Germany. Bought it on release date 28.08.2013.
So I doubt that later produced hardware would be shipped with an older ROM version, you can grab this information.

scorpio16v said:
My LTE (deb) was shipped with JSS15J in Germany. Bought it on release date 28.08.2013.
So I doubt that later produced hardware would be shipped with an older ROM version, you can grab this information.
Click to expand...
Click to collapse
Just to confirm, my LTE Nexus 7 also came with JSS15J from Media Market in Germany.
.
.

Dave_S said:
Just to confirm, my LTE Nexus 7 also came with JSS15J from Media Market in Germany.
.
.
Click to expand...
Click to collapse
Getting my device on Monday (LTE) will check for you.

I, too, have bought my N7 in Germany, it came with JSS15J. I have received several updates for the Google Apps, but so far no OTA system update. So I'm still on JSS15J and, I guess, the original bootloader shipped with the device.
Bootloader version according to bootloader screen is FLO-03.14. For completeness: HW version is 'rev_e', Baseband version is 'DEB-G00_1.23.0_0720'

TheManii said:
Like topic states, I would like the bootloader version of JSR78D.
Here's how to check:
turn device off
hold down power and volume down until fastboot screen appears
version should be in bottom left of screen
Preferably I would like to also request a nandroid and dump of the bootloader, but having just the bootloader version will do.
If you've already updated to JSS15J: I already know the bootloader version for that, I dont need it again.
Click to expand...
Click to collapse
Postal service lost my package, so it won't be arriving today
Maybe they find it this week or maybe not, who knows

just unpack new LTE, boot loader FLO-03.05
how to backup the boot loader?

xdacinq said:
how to backup the boot loader?
Click to expand...
Click to collapse
If you have fastboot set up, you can unlock your bootloader with "fastboot oem unlock", reboot your device once, then boot into the latest TWRP recovery via "fastboot boot <IMG file name>". Once in TWRP select "Backup" and be sure "Boot" is selected on the backup screen.

dasmanul said:
If you have fastboot set up, you can unlock your bootloader with "fastboot oem unlock", reboot your device once, then boot into the latest TWRP recovery via "fastboot boot <IMG file name>". Once in TWRP select "Backup" and be sure "Boot" is selected on the backup screen.
Click to expand...
Click to collapse
But TWRP 2.6.1.0 is not available yet for N7 LTE. And 2.6.0.0 may result in multi touch issue. I will try Wug's Nexus Root Kit instead.
Will i be asked if i want to update via OTA or do i get them without influence by myself?

xdacinq said:
But TWRP 2.6.1.0 is not available yet for N7 LTE. And 2.6.0.0 may result in multi touch issue. I will try Wug's Nexus Root Kit instead.
Will i be asked if i want to update via OTA or do i get them without influence by myself?
Click to expand...
Click to collapse
You are not flashing TWRP with that command, you are booting an image just for 1 time, so it's temporary.
fasboot flash xxx xxx.img > flashes an image permanently
fasboot boot xxx xxx.img > boots with that image for once

jak3z said:
You are not flashing TWRP with that command, you are booting an image just for 1 time, so it's temporary.
fasboot flash xxx xxx.img > flashes an image permanently
fasboot boot xxx xxx.img > boots with that image for once
Click to expand...
Click to collapse
ok, understood.
@TheManii do you need the files from my version?

03.05 is the same as flo on JWR66N, because of that I already have a good copy of it.
If there's enough interest I could pack it into a custom recovery flashable update zip.

jak3z said:
You are not flashing TWRP with that command, you are booting an image just for 1 time, so it's temporary.
Click to expand...
Click to collapse
Careful, though! If I read this thread correctly, booting an image even just once can affect your touchscreen firmware. However, the same thread could also offer a remedy if you actually experience problems.
For the record: I have TWRP 2.6.0.0 flashed on my LTE model and haven't experienced any multitouch issues. I have, however, probably never tried to use more than 2 fingers at once.

So would you recommend to install the OTA?

xdacinq said:
So would you recommend to install the OTA?
Click to expand...
Click to collapse
In case you're asking me: I don't feel I have had the device long enough to give any recommendations. All I can say is that mine came with JSS15J out of the box and I haven't had any issues. I've unlocked my bootloader, rooted the device in order to install XPosed and XPrivacy and flashed TWRP 2.6.0.0. I haven't received any OTA updates yet.

dasmanul said:
Careful, though! If I read this thread correctly, booting an image even just once can affect your touchscreen firmware. However, the same thread could also offer a remedy if you actually experience problems.
For the record: I have TWRP 2.6.0.0 flashed on my LTE model and haven't experienced any multitouch issues. I have, however, probably never tried to use more than 2 fingers at once.
Click to expand...
Click to collapse
You read correctly.
This post has a more detailed explanation of what is going on:
http://forum.xda-developers.com/showthread.php?t=2428194
TWRP 2.6.0.0 = JSS15J touchscreen firmware
TWRP 2.6.1.0 = JSS15Q touchscreen firmware
This has nothing to do with whether you boot into it temporarily vs flashing it on your tablet. As long as you run ANY kernel (including the kernels bundled into TWRP/CWM/etc.) it will try to upgrade your firmware if the one in the kernel is newer, and then that is the firmware your tablet uses until a newer one comes along. Going back to your old kernel/ROM will NOT restore your older touchscreen firmware but there are solutions for that now.

[Q] Everyone keeps talking about bootloader downgrade

But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?

Zalmoxis12 said:
But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?
Click to expand...
Click to collapse
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.

simon_lefisch said:
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.
Click to expand...
Click to collapse
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?

Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
http://searchenterpriselinux.techtarget.com/definition/boot-loader

Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
bootloader loads all the partitions and makes sure they work together, two examples of the stuff bootloader handles:
-bootloader boots
-bootloader then loads kernel making sure nothing wrong and if there is then you get no boot and instead you are thrown to fastboot to fix the problem
-after kernel loads bootloader loads system if corrupted/missing you get stuck in a bootloop unless you have custom recovery then you get stuck in recovery
-bootloader loads rest of partitions while the system/kernel begin to boot rom
when doing ota:
-phone reboots and loads bootloader
-bootloader loads ota into a partition on phone designed to decompile and apply ota into system/kernel partitions
-bootloader makes sure that system/ota are correct and compatible to apply update
-bootloader does root check process in the rtf partition and if rooted bootloader cancels ota process
so in short bootloader is most important asset, it is what decides the kernel to boot(you can mod a bootloader so that you can have too kernels and this is also how you create multi boot for boot more than one rom), it boots the rom, and it handles all other partitions in more than one way

Stock unrooted device in soft-brick bootloop running 7.1.1

Hi,
So quick summary of what happened. I went to make coffee, came back to desk and my N6P has been stuck in boot loop.
It was running the latest Android 7.1.1 build (NPF26F)
I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked.
I tried wiping data / factory & cache from fastboot and recovery with no difference in result.
I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build.
The latest OTA i can find is: 7.1.1 NMF26F (angler-ota-nmf26f-61b4a915.zip)
I also tried the official 7.0 NBD91K (angler-ota-nbd91k-32c2eac8.zip) with the same result.
Is there a different OTA I can use or can I force it to sideload an older version or any other suggestions?
I really don't want to have to deal with my telco. I'll be without a phone for weeks if I have to :'(

I have a phone with the same problem. Haven't gotten an answer yet. I am starting to wonder if it's an issue with the build.

bkgovols said:
I have a phone with the same problem. Haven't gotten an answer yet. I am starting to wonder if it's an issue with the build.
Click to expand...
Click to collapse
When you say haven't gotten an answer yet.... you posted it somewhere? I bet an easy fix for google would be to release a newer full OTA... but unless they respond in a day, i'll be returning phone...

gunigugu said:
Hi,
So quick summary of what happened. I went to make coffee, came back to desk and my N6P has been stuck in boot loop.
It was running the latest Android 7.1.1 build (NPF26F)
I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked.
I tried wiping data / factory & cache from fastboot and recovery with no difference in result.
I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build.
The latest OTA i can find is: 7.1.1 NMF26F (angler-ota-nmf26f-61b4a915.zip)
I also tried the official 7.0 NBD91K (angler-ota-nbd91k-32c2eac8.zip) with the same result.
Is there a different OTA I can use or can I force it to sideload an older version or any other suggestions?
I really don't want to have to deal with my telco. I'll be without a phone for weeks if I have to :'(
Click to expand...
Click to collapse
You can unlock bootloader if you have fast boot. The computer needs to recognise your phone. Then just follow the steps in the beginner's guide.

tropical cactus said:
You can unlock bootloader if you have fast boot. The computer needs to recognise your phone. Then just follow the steps in the beginner's guide.
Click to expand...
Click to collapse
No, unfortunately, you can no longer unlock nexus devices from just the bootloader. You need access to Android OS.

gunigugu said:
No, unfortunately, you can no longer unlock nexus devices from just the bootloader. You need access to Android OS.
Click to expand...
Click to collapse
Install Android SDK or find adb mini bundle. Download latest factory images from Google's website. Run this command to sideload the factory image. You DON'T need unlocked bootloader for this command.
HTML:
adb sideload yourFactoryImagesFile

gunigugu said:
Hi,
...I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked....
Click to expand...
Click to collapse
You never went into Developer Options and toggled the "allow OEM Unlock"? If not, you will not be able to unlock bootloader via fastboot.
And are you positive you did a proper "factory reset" from recovery? From stock, this should get you out of a boot loop. The naming convention Google used for DP2/Public Release was screwed up and I've seen others reporting the inability to flash OTA's but the solution was to flash the full Google image. As someone else suggested, until a new OTA hits with a newer (higher) number, you may be out of luck. Maybe someone with more experience can help with perhaps altering the OTA signature?

fapste said:
Install Android SDK or find adb mini bundle. Download latest factory images from Google's website. Run this command to sideload the factory image. You DON'T need unlocked bootloader for this command.
HTML:
adb sideload yourFactoryImagesFile
Click to expand...
Click to collapse
Unfortunately as mentioned in original post 'I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build'

v12xke said:
You never went into Developer Options and toggled the "allow OEM Unlock"? If not, you will not be able to unlock bootloader via fastboot.
And are you positive you did a proper "factory reset" from recovery? From stock, this should get you out of a boot loop. The naming convention Google used for DP2/Public Release was screwed up and I've seen others reporting the inability to flash OTA's but the solution was to flash the full Google image. As someone else suggested, until a new OTA hits with a newer (higher) number, you may be out of luck. Maybe someone with more experience can help with perhaps altering the OTA signature?
Click to expand...
Click to collapse
Yup never did it :'(
Didn't think I needed to unlock / root my devices anymore since I can get all the functionality out of stock android these days. Though now I feel like I'm being punished for not unlocking it :'(
I'm positive I did a factory reset from recovery. I do believe flashing a full google image would fix the issue, but im unable to from fastboot as device is locked and sideload images appear to be older :'(

Really sorry to hear this, and I know being without the phone even for a day or two is inconvenient at best. Could be critical for your work or school. Most every bootloop I have encountered, I've been able to fix by re-flashing the kernel. Either stock or custom... like EX Kernel. Have you ever played with WugFresh's NRT? You can temp flash TWRP and maybe temp flash or flash the kernel? This probably won't work with a locked bootloader If you could just start the OS, you could toggle the OEM unlock. At a minimum, TWRP will give you a file manager, MTP file transfer, wiping and other tools. If you have time, it may be worth a try. Other than that, successfully altering the signature of the OTA may work, but I've not seen any work on this, but have never had to look. I'd keep searching for ppl having the difficulty of going from DP2 to Public Release (older/newer) and see if there was another solution other than flashing the full image, which obviously you can't do right now. Good luck, and let us know if you make any progress.
Edit : Read here for possible help. This may work in conjunction with getting TWRP installed via NRT.

gunigugu said:
Unfortunately as mentioned in original post 'I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build'
Click to expand...
Click to collapse
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images

fapste said:
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
Click to expand...
Click to collapse
Many ppl have had problems sideloading the OTA coming from DP2 to Public Release NPF26F->>NMF26F and not just the 6P. Because the Public release numerically is "older" the OTA will not flash. When unlocked, the solution was to flash the full Google image, rather than the OTA. Why in their infinite wisdom Google did this I have no idea. Options are very slim when your bootloader is locked and you are stuck in a boot loop. OP cannot flash a full image when the NMF26F OTA is parsed as being "older".

fapste said:
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
Click to expand...
Click to collapse
I believe it's because the latest OTA on https://developers.google.com/android/ota is 7.1.1 (NMF26F) and my phone is already running 7.1.1 build (NPF26F).

v12xke said:
Many ppl have had sideloading OTA coming from DP2 to Public Release NPF26F->>NMF26F and not just the 6P. Because the Public release numerically is "older" the OTA will not flash. When unlocked, the solution was to flash the full Google image, rather than the OTA. Why in their infinite wisdom Google did this I have no idea. Options are very slim when your bootloader is locked and you are stuck in a boot loop. OP cannot flash a full image when the NMF26F OTA is parsed as being "older".
Click to expand...
Click to collapse
This guy gets it!!! Yeah, I've unlocked a lot of my older devices and am comfortable with 'messing' my devices, but I didn't with the 6p as the stock experience is great now. But now I feel like I'm being punished because my device is dead with no recourse for action. Unless google release a newer full OTA.

If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".

v12xke said:
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
Click to expand...
Click to collapse
This will work on a locked device? I'll give it a crack and report back.

v12xke said:
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
Click to expand...
Click to collapse
Yeah failed :'( (remote: unlock device to use this command)

[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work i encountered a problem like this too

boxguy1 said:
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work i encountered a problem like this too
Click to expand...
Click to collapse
Firstly your link is broken: It's http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Secondly as I've mentioned a few times including the OP. The device is locked. You need access to Android OS to unlock. It can not be done just from bootloader. So this does not work, but thanks for posting the suggestion anyway.

Deleted
---------- Post added at 05:53 AM ---------- Previous post was at 05:34 AM ----------
gunigugu said:
Firstly your link is broken: It's http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Secondly as I've mentioned a few times including the OP. The device is locked. You need access to Android OS to unlock. It can not be done just from bootloader. So this does not work, but thanks for posting the suggestion anyway.
Click to expand...
Click to collapse
Sorry I thought it would have worked you should wait until the January security patch as all the other users said best of luck

Downgrade from 7.1.1 to anything lower with a locked bootloader?

In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!

matistight said:
In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
Click to expand...
Click to collapse
Hi... Did the bootloop came from nowhere or what were you doing when it happened?
What error do you get when you sideload the ota?
Tried formatting cache or factory reset?
Edit: You can't downgrade with a locked bootloader.

matistight said:
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
Click to expand...
Click to collapse
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.

v12xke said:
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
Click to expand...
Click to collapse
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N

matistight said:
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
Click to expand...
Click to collapse
If you erase or corrupt the bootloader then the phone is hard bricked (if it already isn't). I think you need an unlocked bootloader to do that anyways. Any flashing or erasing command in fastboot is going to need an unlocked bootloader. Even if you did somehow manage to delete the bootloader, without the phone being unlocked you can't flash a new one = hard brick.
If your phone is BL locked, you can't access Android, recovery doesn't help, you're mostly out of luck. Some people have said that using MSkips toolkit recovered their phones, but others had no such luck. There's a lot of people in the same boat as you. Others have tried calling Google about the issue despite their warranty status. Your phone is locked and a stock OTA took it out, from the sounds of it. Maybe they'll be willing to work with you. The worst they can do is say no, can't hurt to try. Good luck!

Why do you want to downgrade?

rchtk said:
Why do you want to downgrade?
Click to expand...
Click to collapse
Never really like 7.x and it has been the only OS that has bricked my phone without being rooted.

Unfortunately you can neither use an OTA to downgrade nor flash a factory image without BL unlocked.
And I'm not sure that would help either. Your device corrupted itself for a reason and that might be the flash failing (which the Nougat update exhibited, but Nougat isn't the root cause probably). You could rather wait for a higher OTA and hope.
Any recovery log to post?
How old is the phone? 1 year?