Database Develop

Flashing Issues/Permission Issues

A few days ago I got my Atrix HD and immediately rooted and subsequently unlocked the bootloader. Later I successfully flashed EcHoFiiVe's paranoidAndroid port... I didn't really like it because of the aspect ratio (too tiny) so I tried to flash back to a stock ROM. I lost and later accidentally deleted the backup I had made of the stock ROM that came on the device so that is now out of the question but for some reason, no matter what I do, I can't make changes to /system from the recovery or from the bootloader using fastboot commands. I've tried inputing
Code:
fastboot erase system -w
and it told me that I didn't have sufficient permissions and that the command failed. Therein lies my problem. Fortunately, I have a runnable backup (PA) I just really wish to try something different and the device is adamantly against the idea. According to the bootloader the device is unlocked with status code 3. Any help will be greatly appreciated!

read this
http://forum.xda-developers.com/showthread.php?t=2226527

frog1982 said:
read this
http://forum.xda-developers.com/showthread.php?t=2226527
Click to expand...
Click to collapse
I've read through that and I can now see a line that I missed that said that it was a common issue for that particular command to not work but I still don't know what to do about my inability to flash a different ROM. I have tried to mount /system before flashing and I've tried wiping /system using the recovery before flashing, all without avail. Do you have any advice on how to wipe the system partition?

you do not have to wipe it just fastboot flash Mex retail to overwrite it and you will be starting over.

frog1982 said:
you do not have to wipe it just fastboot flash Mex retail to overwrite it and you will be starting over.
Click to expand...
Click to collapse
to be clear, are you saying I can just do this:
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
Code:
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot reboot

sparkplugDev said:
to be clear, are you saying I can just do this:
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
Code:
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
yes but make sure you also have the snap-fastboot files in the folder you are working in or in your path

For those getting the not enough memory error while flashing the 5.0 Factory Image

THIS WILL FACTORY RESET YOUR DEVICE AND DELETE EVERYTHING
I unzipped everything in the factory image and the ZIP file inside the factory image and made this a batch file, and ran it...works great! Be sure to boot into the bootloader:
NOT MY FAULT IF YOU BREAK YOUR DEVICE THIS WILL WIPE IT CLEAN!
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot
You may need to boot into the bootloader again and wipe cache/factory rese or reset it from the phone settings itself.
Please put this script in the same folder as all the extracted files mentioned in the script above.
Script: https://www.dropbox.com/s/tfazy6rqamqpazo/flash-all-modified.bat?dl=0
Original Comment Below
http://forum.xda-developers.com/showpost.php?p=56700113&postcount=63
EDIT:
Edited script to remove the reboot bootloaders and also reboot the phone when it is done.

reinert012 said:
I unzipped everything in the factory image and the ZIP file inside the factory image and made this a batch file, and ran it...works great! Be sure to boot into the bootloader:
NOT MY FAULT IF YOU BREAK YOUR DEVICE THIS WILL WIPE IT CLEAN!
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
Script: https://www.dropbox.com/s/tfazy6rqamqpazo/flash-all-modified.bat?dl=0
Original Comment Below
http://forum.xda-developers.com/showpost.php?p=56700113&postcount=63
Click to expand...
Click to collapse
Is everyone who's getting this error on the 16gb model? Or are there people on the 32 gb model experiencing it as well?

cbowens said:
Is everyone who's getting this error on the 16gb model? Or are there people on the 32 gb model experiencing it as well?
Click to expand...
Click to collapse
I do not know, i'm on 16gb myself.

I was getting this error on my 32GB device
So I went ahead and did the flash commands
Now its showing my 32GB device is a 16GB device
Something bad happened

shoemocker said:
I was getting this error on my 32GB device
So I went ahead and did the flash commands
Now its showing my 32GB device is a 16GB device
Something bad happened
Click to expand...
Click to collapse
Boot recovery and factory reset?

reinert012 said:
I unzipped everything in the factory image and the ZIP file inside the factory image and made this a batch file, and ran it...works great! Be sure to boot into the bootloader:
NOT MY FAULT IF YOU BREAK YOUR DEVICE THIS WILL WIPE IT CLEAN!
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
You may need to boot into the bootloader again and wipe cache/factory reset.
Please put this script in the same folder as all the extracted files mentioned in the script above.
Script: https://www.dropbox.com/s/tfazy6rqamqpazo/flash-all-modified.bat?dl=0
Original Comment Below
http://forum.xda-developers.com/showpost.php?p=56700113&postcount=63
Click to expand...
Click to collapse
Worked for me on 16gb. Was getting error flashing system.img. Thanks!

reinert012 said:
Boot recovery and factory reset?
Click to expand...
Click to collapse
I just did a factory reset through the settings in the rom itself and that did the trick - thanks for your help

xmishka said:
Worked for me on 16gb. Was getting error flashing system.img. Thanks!
Click to expand...
Click to collapse
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
theretroandroid said:
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
Click to expand...
Click to collapse
So I just did a fastboot reboot after that. Phone is booting. Fingers crossed.
If it boots successfully, is there anything else that I need to do after that?

theretroandroid said:
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
Click to expand...
Click to collapse
Just use your volume keys on the phone so it says Start and then hit the power button or fastboot reboot via the cmd prompt.

theretroandroid said:
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
So I just did a fastboot reboot after that. Phone is booting. Fingers crossed.
If it boots successfully, is there anything else that I need to do after that?
Click to expand...
Click to collapse
Nope, just give it a few min to boot up all the way.

I m getting this error while flashing user data, mine is 32gb one
EDit- just did factory reset from recovery, now it works fine.
Damn you google , you a sec I thought my emmc has got corrupted

reinert012 said:
Nope, just give it a few min to boot up all the way.
Click to expand...
Click to collapse
It booted fine and is working. Setting it all up now. Thanks so much.

This thing didn't work for me at all it started the twrp then it got into bootloop with the twrp i dont know why

I just did a factory reset using the phones settings menu.
Sent from my Nexus 9 using Tapatalk

anshmiester78900 said:
This thing didn't work for me at all it started the twrp then it got into bootloop with the twrp i dont know why
Click to expand...
Click to collapse
Boot into bootloader and run the script again, make sure all the files are in the right place. I will run it again with TWRP installed and see what happens.

anshmiester78900 said:
This thing didn't work for me at all it started the twrp then it got into bootloop with the twrp i dont know why
Click to expand...
Click to collapse
I ran my script with TWRP installed and it worked perfect...please make sure ALL of the files in the script are in the same folder as the script.

reinert012 said:
I ran my script with TWRP installed and it worked perfect...please make sure ALL of the files in the script are in the same folder as the script.
Click to expand...
Click to collapse
I just flashed back to kitkat full stock
ALso now can you please be precise with the steps . Please . What files and where do i have to put them . Just confirming it from you as i got a bit confused with the first post

Er, mine also failed because of lack of memory, but it still booted up into lollipop. Should I reflash using your updated script?

anshmiester78900 said:
I just flashed back to kitkat full stock
ALso now can you please be precise with the steps . Please . What files and where do i have to put them . Just confirming it from you as i got a bit confused with the first post
Click to expand...
Click to collapse
1. Download the factory image from Google.
2. Extract those contents into your platform-tools folder wherever that is.
3. Go to the extracted folder, copy ALL the contents back to your platform-tools folder
4. Extract the contents from image-hammerhead-lrx21o.zip (this was in the extracted folder from step 2, which you copied in step 3) and make sure it's in the platform-tools folder again.
5. Make sure script is in the platform-tools folder too, and run it.
I just ran through this on my phone again....works fine.

reinert012 said:
1. Download the factory image from Google.
2. Extract those contents into your platform-tools folder wherever that is.
3. Go to the extracted folder, copy ALL the contents back to your platform-tools folder
4. Extract the contents from image-hammerhead-lrx21o.zip (this was in the extracted folder from step 2, which you copied in step 3) and make sure it's in the platform-tools folder again.
5. Make sure script is in the platform-tools folder too, and run it.
I just ran through this on my phone again....works fine.
Click to expand...
Click to collapse
Alright going to give it a try
---------- Post added at 05:54 AM ---------- Previous post was at 05:45 AM ----------
UPDATE:
Thanks a lot mate it worked . now my phone is booting up, I hope i dont get that problem where storage is reduced to half as i have 32gb model
anyways thanks a lot again
UPDATE 2:
my storage is reduced to 12.6 gb, how to fix this mate ?

[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064

[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Sorry for my bad english! I hope someone can help me!
Here I put the files I've already uploaded! USE AT YOUR OWN RISK!
https://mega.co.nz/#F!VMQHFJxB!7aSAkqkYI1SX7GI_S5yItw
USE AT YOUR OWN RISK! YOU MUST HAVE UNLOCKED BOOTLOADER
How-to:
-Copy all the files from the IMG's And BIN folder and the TWRP Recovery "twrp-2.8.3.0-titan.img" to your "platform-tools" folder
-Copy the TWRP Backup to your SD Card Backup's folder
Enter to fastboot in your device and run this commands in order (I exclude "fastboot flash partition gpt.bin" and
"fastboot flash motoboot motoboot.img")
fastboot flash logo logo.bin <--- From Retail US Firmware
fastboot flash boot boot.img <--- From XT1064 Nextel México
fastboot flash recovery twrp-2.8.3.0-titan.img <--- Flash TWRP Recovery include in the Link
-Enter to TWRP Recovery using your device, Wipe System/Data/Cache and Restore the System Partition from the Backup.
-Power Off the Device and enter to Fastboot again.
fastboot flash recovery recovery.img <--- Original Recovery from Retail US Firmware
fastboot flash modem NON-HLOS.bin <--- Modem from XT1064 Nextel México
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn <--- From XT1064 Nextel México
fastboot erase cache
fastboot erase userdata

ejsmsupersoyelm said:
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Click to expand...
Click to collapse
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.

reefuge said:
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.
Click to expand...
Click to collapse
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...

ejsmsupersoyelm said:
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...
Click to expand...
Click to collapse
It's hard to say but motoboot.img and gpt.bin it's normally a one way upgrade only, if you flash newest, it can be hard to go back. Yes the should flash but you wont gain much and may lose OTA updates in future.
So there is no need to flash these for restoring TWRP back ups, I strongly suggest you leave yours alone.
ADB flashing really is just for OTA upgrades and using to get a custom recovery on phone, once you have a custom recovery you can make custom roms to flash from that.
Adb flashes system from OTA as 4 parts that combine into /system folder - so thats why you cant flash 1 big img via adb
again you need to learn how to make a flashable custom rom to use via TWRP, look for a guide there are many.
but i will give you a idea how to do
using your xt1064 mexcio TWRP back up - ALL you need for now is Boot.emmc.win and system.ext4.win nothing else
rename boot.emmc.win to boot.img and change system.ext4.win to system.ext4.tar and find a guide on how to extract the tar to a system folder ( I use cygwin )
then take a meta-info folder from a custom xt1064 rom and adjust the updater-script to work with your rom - zip these 3 files up into your new custom rom.
this is a very simple idea, there are more steps so search for a guide on here

I just need the motoboot.img file, would provide for me?

Where do radio and kernel come from flashing img's?

I know how to fastboot flash .img files and understand it includes the radio and kernel components. I'm rooted and have TWRP recovery. But which .img file contains the radio and which the kernel? I ask because I'll be going from the latest T-Mo rom (LYZ28J) to Project Fi having just received my sim. If I flash just the system.img from LYV48E (Fi rom) will I have the correct kernel and radio or will I have to flash boot.img also or something else? Since kernels and radios can be flashed separately I'm just not sure where everything comes from. I would appreciate some clarity.

Groid said:
I know how to fastboot flash .img files and understand it includes the radio and kernel components. I'm rooted and have TWRP recovery. But which .img file contains the radio and which the kernel? I ask because I'll be going from the latest T-Mo rom (LYZ28J) to Project Fi having just received my sim. If I flash just the system.img from LYV48E (Fi rom) will I have the correct kernel and radio or will I have to flash boot.img also or something else? Since kernels and radios can be flashed separately I'm just not sure where everything comes from. I would appreciate some clarity.
Click to expand...
Click to collapse
have you ever unzipped a factory.img .tar file to see what files it contains?

Groid said:
I know how to fastboot flash .img files and understand it includes the radio and kernel components. I'm rooted and have TWRP recovery. But which .img file contains the radio and which the kernel? I ask because I'll be going from the latest T-Mo rom (LYZ28J) to Project Fi having just received my sim. If I flash just the system.img from LYV48E (Fi rom) will I have the correct kernel and radio or will I have to flash boot.img also or something else? Since kernels and radios can be flashed separately I'm just not sure where everything comes from. I would appreciate some clarity.
Click to expand...
Click to collapse
simms22 said:
have you ever unzipped a factory.img .tar file to see what files it contains?
Click to expand...
Click to collapse
If I were a betting man, I'd be backing the horse called "Wish I'd done that before posting"

Tiptonian said:
If I were a betting man, I'd be backing the horse called "Wish I'd done that before posting"
Click to expand...
Click to collapse
Hahaa. Unzip and you shall receive. LMAO

simms22 said:
have you ever unzipped a factory.img .tar file to see what files it contains?
Click to expand...
Click to collapse
Not sure what you mean by this. I have the system, boot, recovery, and userdata .img files. I don't know which one has the kernel or which one has the radio. You imply I can unzip, for example, system.img to see what files are there, but I cannot unzip it or any of the .img files. My main question still is unanswered which is which .img files do I need to (m)fastboot flash to insure I have the correct (stock) kernel and radio for the Project Fi rom? I may just flash them all, flash TWRP, re-root and start clean, but I wanted to consider the option of keeping data. Any helpful answers?

Tiptonian said:
If I were a betting man, I'd be backing the horse called "Wish I'd done that before posting"
Click to expand...
Click to collapse
prdog1 said:
Hahaa. Unzip and you shall receive. LMAO
Click to expand...
Click to collapse
So glad my post was such a source of amusement for you. Sorry I didn't make it clear I know how download factory images, unzip the .tgz file to get the .tar file. Unzip the .tar file to get to the .zip file. Unzip the .zip file to get the boot, recovery, system, and userdata .img files. But no one actually tried to answer my question.

Groid said:
So glad my post was such a source of amusement for you. Sorry I didn't make it clear I know how download factory images, unzip the .tgz file to get the .tar file. Unzip the .tar file to get to the .zip file. Unzip the .zip file to get the boot, recovery, system, and userdata .img files. But no one actually tried to answer my question.
Click to expand...
Click to collapse
kernel is boot.img, radio is radio.img

Thank you for your reply. I suspected boot.img is the kernel but wanted to make sure. I notice that the radio-shamu-. . .02.78.02.img and boot-shamu. . .71.10.img are in the shamu-lvy48e folder in the .tar file with the flash batch files. The enclosed .zip file has the system, boot, userdata, recovery, and cache .img files along with the text file specifying the bootloader (kernel) and baseband (radio). I now understand that the boot.img is the kernel which is the same version my current one in LYZ28J, so I need not flash it. The radio is different based on the android-info.txt file. So, the last piece of the puzzle for me is will I get the updated radio by flashing the system.img or must I separately flash the radio-shamu -. . .-02.78.02.img?

Groid said:
Thank you for your reply. I suspected boot.img is the kernel but wanted to make sure. I notice that the radio-shamu-. . .02.78.02.img and boot-shamu. . .71.10.img are in the shamu-lvy42e folder in the .tar file with the flash batch files. The enclosed .zip file has the system, boot, userdata, recovery, and cache .img files along with the text file specifying the bootloader (kernel) and baseband (radio). I now understand that the boot.img is the kernel which is the same version my current one in LYZ28J, so I need not flash it. The radio is different based on the android-info.txt file. So, the last piece of the puzzle for me is will I get the updated radio by flashing the system.img or must I separately flash the radio-shamu -. . .-02.78.02.img?
Click to expand...
Click to collapse
youll get the updated radio in the factory.img, but you can always flash the radio itsrlf via fastboot(fastboot flash radio radioname.img).

Groid said:
Thank you for your reply. I suspected boot.img is the kernel but wanted to make sure. I notice that the radio-shamu-. . .02.78.02.img and boot-shamu. . .71.10.img are in the shamu-lvy48e folder in the .tar file with the flash batch files. The enclosed .zip file has the system, boot, userdata, recovery, and cache .img files along with the text file specifying the bootloader (kernel) and baseband (radio). I now understand that the boot.img is the kernel which is the same version my current one in LYZ28J, so I need not flash it. The radio is different based on the android-info.txt file. So, the last piece of the puzzle for me is will I get the updated radio by flashing the system.img or must I separately flash the radio-shamu -. . .-02.78.02.img?
Click to expand...
Click to collapse
If have updated SDK will get everything in flash-all.bat. If not and have to do all separate they are all separate. Bootloader, radio, boot, system, cache, userdata. There is no radio in system.img. It is the radio. img. On first unzip get bootloader, radio, flash-all and the folder for the rest of the images. If want radio fastboot flash radio (radio.img).

Thank you for answering my question about whether or not the radio gets updated by flashing system.img. Unfortunately, I cannot get ADB to work properly. I initially seem to have it working with the ADB devices statement from the command prompt, it returns the serial #, but when I try to execute the batch file ADB seems to be disconnected. At least I have experience with (m)fastboot and will just flash the radio and system .imgs since the bootloader is the same. I'll keep TWRP recovery, format cache, update supersu for root and I should be good to go.

Groid said:
Thank you for answering my question about whether or not the radio gets updated by flashing system.img. Unfortunately, I cannot get ADB to work properly. I initially seem to have it working with the ADB devices statement from the command prompt, it returns the serial #, but when I try to execute the batch file ADB seems to be disconnected. At least I have experience with (m)fastboot and will just flash the radio and system .imgs since the bootloader is the same. I'll keep TWRP recovery, format cache, update supersu for root and I should be good to go.
Click to expand...
Click to collapse
well, adb doesnt work in the bootloader, and its only fastboot that can flash those files..

Thanks, I was responding to using adb to sideload with the flash(all).bat. Fastboot works fine for me so I don't really miss using adb commands.

How to flash security OTA update with Nexus Root Toolkit?

Hello!
I looked for this, but can't seem to find a clear answer. The other thread on this is over 3,000 posts (can't look through all that).
I am currently on 6.0.1 with February 1 security update on rooted Nexus 6, stock, with TWRP recovery. I want to apply the latest security patches using NRT....How to?? What is my easiest method to doing this? Thanks in advance, cheers!

The easiest method is not to use NRT. Much as I'm a fan of it, having contributed to Wug several times, the manual method is simpler. Boot into bootloader, start a CMD session, flash system.img & boot.img, and radio.img if you want to be particularly careful, and reboot. Job done. No data loss, everything as normal apart from the new security patches.
If the above isn't familiar, you need to read these forums a lot more. Not trying to be funny - I had to before I had the balls to offer advice to others.

Would we have to flash SuperSU again to reroot?

iluvatrix said:
Would we have to flash SuperSU again to reroot?
Click to expand...
Click to collapse
yes

dahawthorne said:
. Boot into bootloader, start a CMD session, flash system.img & boot.img, and radio.img if you want to be particularly careful, and reboot. Job done. No data loss.......
Click to expand...
Click to collapse
.....with the newest twrp-recovery (v3.0.0.1) it is possible to flash the boot.img and system.img, directly from the internal memory.

so what we do is dl the factory image , extract the boot.img and system.img , drag over to phone internal memory, boot twrp 3.0.0.1 then flash?

"flash the boot.img and system.img, directly from the internal memory"
"boot twrp 3.0.0.1 then flash?"
I don't believe you can install an img file in TWRP, and I've never tried. If you extract everything from the factory ROM image, including the zip within the zip, you'll find boot.img, system.img & radio.img. Copy them across to your PC folder where ADB.exe & fastboot.exe live, open a CMD window, boot your phone into bootloader mode, attach via USB, and separately fastboot flash the 3 img files. Then install TWRP, and from there you can install SuperSU v2.70 if you want to root.

dahawthorne said:
"flash the boot.img and system.img, directly from the internal memory"
"boot twrp 3.0.0.1 then flash?"
I don't believe you can install an img file in TWRP, and I've never tried. If you extract everything from the factory ROM image, including the zip within the zip, you'll find boot.img, system.img & radio.img. Copy them across to your PC folder where ADB.exe & fastboot.exe live, open a CMD window, boot your phone into bootloader mode, attach via USB, and separately fastboot flash the 3 img files. Then install TWRP, and from there you can install SuperSU v2.70 if you want to root.
Click to expand...
Click to collapse
You can flash images in TWRP 3.0.0-1
Recovery, system and boot. My PC is down and that's how I flashed N preview. Works great
Sent from my Nexus 6 using XDA Free mobile app

iluvatrix said:
so what we do is dl the factory image , extract the boot.img and system.img , drag over to phone internal memory, boot twrp 3.0.0.1 then flash?
Click to expand...
Click to collapse
Yes ?
---------- Post added at 01:11 PM ---------- Previous post was at 01:06 PM ----------
dahawthorne said:
...
I don't believe you can install an img file in TWRP, and I've never tried...
Click to expand...
Click to collapse
Try and you will believe. ?

That's why we're here - to learn...
Thanks, people.

31ken31 said:
You can flash images in TWRP 3.0.0-1
Recovery, system and boot. My PC is down and that's how I flashed N preview. Works great
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do we then have to re-root after going this method? Also, will everything be the way it was before flashing (no data loss, no settings loss, etc.)?

Shaundiesel said:
Do we then have to re-root after going this method? Also, will everything be the way it was before flashing (no data loss, no settings loss, etc.)?
Click to expand...
Click to collapse
None and yes flash appropriate su to restore root
Sent from my Nexus 6 using XDA Free mobile app

http://forum.xda-developers.com/showpost.php?p=65136208&postcount=13
Works like a charm Every time.