Database Develop

About your Boot Img errors!

Hi, I have heard a few of you have been getting error when Flashing a boot img recovery and fastboot.
Today I noticed the same thing to my device. I fixed it....
Here's how
1. Download This KDZ
Clockwork Recovery Rom.kdz
2. Download KDZ_UPD_En
From Here: KDZ_upd_fw_en
3. Extract the KDZ zip you downloaded and run KDZ_Updater.exe
4. In the dropdown menu's select 3GQPT and If your phone is running select DIAG
5. Open the clockwork recovery rom.kdz hit the open button and find it in your file directories.
6. Then Select Update now.
[TIPS] - If you are using a PC use the back ports of the PC
- If the update fails restart your PC and do steps 4 and 5 again.
- If your update doesn't finish and your phone doesn't work, keep trying again
Wait for it to finish
After it has finished.
1. Your phone may not boot if you came from a custom rom. Reboot into fastboot and type Command in CMD: (Make Sure you have fastboot and fastboot drivers installed) (My fastboot is in C:\Android
cd C:\Android
fastboot -w (wipe all data)
2. Download CWM recovery img from here
3. Rename the img to recovery.img that you just downloaded
4. Copy that to where your fastboot is setup. eg mine is in C:\android
5. Type commands: fastboot flash recovery recovery.img
6. Then type Fastboot reboot
Now reflash you rom and you should have no errors

airbus360 said:
Hi, I have heard a few of you have been getting error when Flashing a boot img recovery and fastboot.
Today I noticed the same thing to my device. I fixed it....
Here's how
1. Download This KDZ
Clockwork Recovery Rom.kdz
2. Download KDZ_UPD_En
From Here: KDZ_upd_fw_en
3. Extract the KDZ zip you downloaded and run KDZ_Updater.exe
4. In the dropdown menu's select 3GQPT and If your phone is running select DIAG
5. Open the clockwork recovery rom.kdz hit the open button and find it in your file directories.
6. Then Select Update now.
[TIPS] - If you are using a PC use the back ports of the PC
- If the update fails restart your PC and do steps 4 and 5 again.
- If your update doesn't finish and your phone doesn't work, keep trying again
Wait for it to finish
After it has finished.
1. Your phone may not boot if you came from a custom rom. Reboot into fastboot and type Command in CMD: (Make Sure you have fastboot and fastboot drivers installed) (My fastboot is in C:\Android
cd C:\Android
fastboot -w (wipe all data)
2. Download CWM recovery img from here
3. Rename the img to recovery.img that you just downloaded
4. Copy that to where your fastboot is setup. eg mine is in C:\android
5. Type commands: fastboot flash recovery recovery.img
6. Then type Fastboot reboot
Now reflash you rom and you should have no errors
Click to expand...
Click to collapse
You are the best!!!
Gonna try it out!!
I got a problem!!
Everytime i type fastbot (something)
it says fastboot is not a command!!
Any help???
I didn't try it now cause i am in the middle of
doing the battery tweak!!!
But before thats what it said!!
I typed fastboot -w
and it said it is not a command!!!

androidboss7 said:
You are the best!!!
Gonna try it out!!
I got a problem!!
Everytime i type fastbot (something)
it says fastboot is not a command!!
Any help???
I didn't try it now cause i am in the middle of
doing the battery tweak!!!
But before thats what it said!!
I typed fastboot -w
and it said it is not a command!!!
Click to expand...
Click to collapse
Have u got adb installed? if not go to android developers com and download it. Then change you directory to where u installed adb, example, put it in your c drive and type cd C:\android-sdk\sdk\tools >Enter>
then do the commands

airbus360 said:
Have u got adb installed? if not go to android developers com and download it. Then change you directory to where u installed adb, example, put it in your c drive and type cd C:\android-sdk\sdk\tools >Enter>
then do the commands
Click to expand...
Click to collapse
Thanks and I so have fastboot installed but maybe not sdk!!
Edit: i did your steps from 1-6 and now my phone is stuck on the android boot logo!!!!
Is this2.1 stock?? Also there is no mode called 3 GQPT!!
I followed all the instrutions and now my phone is stuck on the android logo!!!
Please help!!! (Its been quite a while)
Edit2: Sorry my fault i didn't do fastboot -w!!
It would be good if you wrote that on your post!!!
And i am thinking of staying on stock 2.1 !!!

tried to install JB, used Blackrose = can't get into recovery

Hello Folks,
I'm still stuck with my nexus one since I don't care that much about phones.
I've seen that jelly bean roms have made a significant progress. Thus I decided to give it a shot.
I started with installing adb and fastboot. :good: After that I rooted the nexus one :good: I've used this how to:
c2med blog, can't post links...
Next, I ran blackrose. :good: I saved the rom on the micro sd. Having done all the preperations I wanted to flash the JB rom.
I started the phone in bootloader mode but - unfortunately - couldn't access the recovery mode (ext4). I only get the Android figure and an exclamation mark.
In the how-to it sais i should use fastboot to flash the recovery made by ext 4.
Problem # 1: Ext4 generated a .zip, not a .img file
Problem # 2: I connect the device in fastboot mode, navigate to the adb/fastboot folder and use ./fastboot devices. The phone is recognized and I see the serial number. Next I try "flash recovery...." but I only get "command not found". Now, I basically have no idea what to do.
Which recovery should I flash? And how?
I'm so looking forward to your answers.

Androdicct said:
Hello Folks,
I only get the Android figure and an exclamation mark.
Which recovery should I flash? And how?
Click to expand...
Click to collapse
What you get is the stock recovery.
Flash 4Ext recovery or Amon RA recovery ( fastboot flash recovery recovery-RA-passion-v2.2.1.img)
Among the several guides to install JB, I suggest you to look at the following post:
http://forum.xda-developers.com/showthread.php?t=1804571
I just finished this morning the following process:
install RA recovery,
install Blackrose and resize partition,
install from SD card Evervolv-Perdo-3.2.0-Nightly-2013.01.13-passion.zip
install from SD card gapps-ev-jb-20120816.zip
I spent a lot of times reading and trying. I had an issue after installing Evervolv-perdo-3.1.0final-passion zip. That's why I switched to the Nightly (JB 4.2).
Once you are set install a2sd from within the terminal emulator on your N1.
In my opinion this is so far the best ROM I ever have had on my Nexus 1.:good:
I am impressed to the extend that I offer to my wife to do the same on her N1. She said no. No to unlock, no to root and of course no to custom ROM.
Good luck

Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...

Androdicct said:
Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...
Click to expand...
Click to collapse
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?

gunner1937 said:
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?
Click to expand...
Click to collapse
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!

Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=611829 : read posts #15 and #16.
In other words open your folder android-sdk-windows installed on the root of your C: hd. Click on the folder platform-tools and download Amon RA recovery in this folder. Left click anywhere on a blank area of this folder then press the key Shift (keyboard) and right click your mouse. In the drop down menu select Open command window. In the CMD, to be sure that the N1 is recognized by the pc (meaning the right drivers are installed) type ADB devices and press enter. You should see a string of numbers like HT9C......
Type adb reboot bootloader and press enter. You are in the fastboot mode ( and mood if I may say so) and the phone shows that it is in the bootloader. You can check again that N1 is recognized by the pc by typing fastboot devices. Same string appears.
Type fastboot flash recovery recovery-RA-passion-v2.2.1.img.
After the installation is completed boot in recovery, select Flash zip from sdcard, select the ROM you have dropped on the card. When the installation is completed go back to Flash zip from sdcard ( you are still in recovery mode) and select the gapps you have dropped on the sdcard.
Go back to Reboot system now. You are then out of the recovery and it takes some times for the N1 to boot to this beautiful JB
Edit:
http://forum.xda-developers.com/showthread.php?t=1804571 this is for posts #15 & #16

Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
As c2med posted in his guide, sometimes, people lose their recovery when they repartition using Black Rose. Hence, its always best to have Amon-RA or 4EXT flashable .img file in your PC so that incase you lose recovery, you can always flash it back.
Once you are in bootloader ( also called FASTBOOT mode) you can flash your recovery.
Then reboot into recovery from FASTBOOT (Shutdown and then restart using the recovery combination)
Once you are in recovery, follow the steps in c2med's guide (wipe cache/dalvik/etc - except sd-card ofcourse) and flash your ROM from sd card.
Then reboot into JayBee

In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img

jolinnard said:
In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img
Click to expand...
Click to collapse
Thank You! That's what I figuered out last night. Of course I also tried "fastboot flash" but forgot the "./". That was the key. Now the JB ROM works like a charm.
New Problem:
I can't install google apps. In fact I don't really need them. I only use a few apps and found the .apk files with google. Unfortunately the "official" Google apps like chrome don't work.
Plus, I wanted to install the camera (laggy in the evervolv - rom) and keyboard from here.
http://forum.xda-developers.com/showthread.php?t=1965290&page=38
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?

Androdicct said:
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?
Click to expand...
Click to collapse
When you're in recovery, select "Flash zip from SD card" and then select "Toggle signature verification" to disable signature verification, and then "Choose zip from SD card" and navigate to the zip file that you want to flash.

Urgent. No OS installed

Hey. I was going to install a RUU for my HTC One with HBOOT 1.54 then the setup gave me ann error saying my CID was wrong now everything is gone and cant boot into OS (it keeps on restarting after 2min).
I have tried to install roms via CMD and its still not working dont know what to do anymore have done almost everything there is, Please help

Can you boot into recovery ? Can you mount the partitions /data and /system ?

Please help, no OS no recovery
Hi i have an internacional version but i can only enter to fastboot like an image, please sorry for my english im from El Salvador
any idea of what can i do?
Thanks.

dh4 said:
Hi i have an internacional version but i can only enter to fastboot like an image, please sorry for my english im from El Salvador
any idea of what can i do?
Thanks.
Click to expand...
Click to collapse
To navigate the bootloader, you have to use the volume keys to move up and down and the power button to select.
Do you have custom recovery installed ? If yes, select "Recovery" from the menu and reflash your ROM.
If you cannot access your custom recovery, try "fastboot erase cache". If that still doesn't work, try "fastboot erase recovery" and re-flash your custom recovery. Make sure to wipe data, wipe cache and wipe dalvik cache BEFORE flashing your ROM.

Hey thanks for the reply man but i dont have rom and backup can i flash GE rom via fastboot?

dh4 said:
Hey thanks for the reply man but i dont have rom and backup can i flash GM rom via fastboot?
Click to expand...
Click to collapse
Here's a little guide I wrote for another thread :
Start your phone in bootloader by typing
Code:
adb reboot bootloader
Select "Fastboot" so that it appears in red instead of HBOOT
On your computer, make sure fastboot sees your device, then type
Code:
fastboot erase cache
Type
Code:
fastboot reboot-bootloader
Download the new firmware.zip
Type
Code:
fastboot oem rebootRUU
Once it's rebooted on a silver HTC logo, type :
Code:
fastboot flash zip [pathonyourcomputer/firmware.zip]
Wait until it is done on your computer. The green line on the phone will never reach the end.
Type
Code:
fastboot reboot-bootloader
Reflash your recovery (I recommend CWM). Might as well play it safe.
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]
Reboot into recovery (select the option in fastboot)
Wipe data/factory reset (you will loose everythng)
*** If there are files you need to keep, you can always use adb pull to get them out before hand (let's say a nandroid backup or something important)
Wipe Cache partition
Advanced -> Wipe Dalvik Cache
Now you have 2 options :
Push
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !
Pull
Select "Install zip"
Select "Install zip from sideload"
Type
Code:
adb sideload [path/rom.zip]
Voila ! You should be good to go !
ROM-wise, I really recommend you get Android Revolution HD. It stays true to HTC Sense while really improving it. You could however flash any ROM; if you really want GE I'd recommend this one; it's modded by the same guy who does Android HD and it's very 'tasteful'
Hit me up if there's anything else !

Please Help Tried Updating to 4.4 Kitkat Bricked

Ok so I tried updating my phone that was already rooted on Android 4.3 S-OFF to 4.4 kitkat with sinless rom sense. Transferred the rom zip to my phone, then proceeded to wipe the system and data, as well as davalik cache with clockworkmod recovery. Attempted to flash the rom and it aborted. Tried a few times and nothing worked. Didn't realize till after that my phone had no OS, and now all I can do is enter the bootloader. Can't enter recovery as the phone will enter clockworkmod then abort and reboot the phone. Not sure what to do at this point as I tried one of the guides and couldn't figure it out. If anyone can help me I'd greatly appreciate it. At least I backed everything up on my computer manually and am using my iPhone 4 until I can get this fixed. Thanks in advance.

Try reflashing recovery then if that works ad b push or usb otg a working Rom to your phone
Sent from my HTC One using Tapatalk

nathlynn22 said:
Try reflashing recovery then if that works ad b push or usb otg a working Rom to your phone
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
How do I reflash recovery when I can't access the filesystem? Do I need to setup ADB and connect to my phone via command line to initiate the transfer? Can you link me to a thread that explains how to setup ADB in a case like this? Thanks

You need to reflash cwm. I'll try find a link. But after recovery is working you would have to use ad b to sideload the Rom. Have you tried from bootloader fastboot erase cache?
Sent from my HTC One using Tapatalk

nathlynn22 said:
You need to reflash cwm. I'll try find a link. But after recovery is working you would have to use ad b to sideload the Rom. Have you tried from bootloader fastboot erase cache?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
My biggest issue is being able to reflash clockworkmod. If I could that out of the way, I already have the rom on the phone storage, so I should in theory be able to reflash I'd think.
I don't have the option to delete cache within the bootloader under fastboot

One Hype said:
How do I reflash recovery when I can't access the filesystem? Do I need to setup ADB and connect to my phone via command line to initiate the transfer? Can you link me to a thread that explains how to setup ADB in a case like this? Thanks
Click to expand...
Click to collapse
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!

hardstuffmuc said:
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
Click to expand...
Click to collapse
Gotcha. Makes sense. Will try and let you know. Thanks so much!

Htc one kiktkat 4.4 update gone wrong
hardstuffmuc said:
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
Click to expand...
Click to collapse
I did all what you said there its still takes me back to bootloader...
and that red message active cmdline overflow (1085bytes) still there...any soulutions to fix this please?

hardstuffmuc said:
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
Click to expand...
Click to collapse
Just tried everything and it worked 100%! Can't thank you enough!

My nexus will not flash correctly

Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!

Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.

Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.

If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard

Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.

Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.

Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...

Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.

You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.

Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".

dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else

Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.

Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.

dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.