Database Users

4.2.1 to 4.2.2 rooted stock rom upgrade nightmare

Hi there, i've got a problem updating, like many it seems and I'm pretty new to rooting etc. so please bear with me.
I have 4.2.1 stock rom, rooted and with twrp v2.4.1.0 recovery. I was originally rooted with CWM recovery (using n7 toolkit) but I have flashed twrp to try and update with no luck either.
Anyway I get an error (see attachment image) via ota or via downloading the zip and copying it to the n7 then browsing for it in recovery and installing it that way. I'm basically wondering if there's a quick fix to this problem and can you please help me with it even if there isnt a quick fix. I really don't want to reset my device and have to set everything back up again.
Also, i dont know if this is related, probably is, I cant boot into recovery using the power off hold volume down trick, getting into fastboot mode and then selecting recovery as it just brings up the google logo forever and I have to reset the tablet due to it doing nothing. The only way I can get into recovery is to clear data from google services framework and do an ota update (1970 thing) and that reboots into recovery. I then get the error 7 message in attached photo.
Plz help?!?!
Thanks in advance

Here's what to do.
First, look at those errors in the image you posted very very carefully.
2nd, use the search function on this forum: try the terms "OTA debuggerd" (without the quotes)
3rd, read those posts.
4th, decide if you want the hassle. You are not obligated to perform an upgrade.
5th, Download from Google the 4.2.2 Factory images and extract the "boot.img" and "system.img" files
(make sure you understand that nakasi == grouper == WiFi N7, and nakasig == tilapia == 3G N7)
Hint: search on Google for "Google Nexus Factory Images"
finally
fastboot flash boot name-of-boot-image-file.img
fastboot flash system name-of-system-image-file.img
This will remove root from the ROM, so you will need to flash a SuperSU or Superuser root kit.
Doing things this way is a band-aid. You need to learn how to make full backups & perform full restores; how to flash individual partitions - using both fastboot & the custom recovery; know exactly what the roles of each partition are; know the difference between a kernel, ramdisk, and boot image; understand how to retrieve a small number of files from prior backups; and to know where the installer scripts are located inside flashable .zip files & be able to read them so you can understand what they do.
Finally, you should understand what apps like Titanium Backup and Carbon are capable of, and how backup of System app&data has different consequences upon restore than similar operations for user-installed apps.
OK - get started.

KRT16O (KitKat 4.4) discussion/resources thread

Code:
KRT16O Factory Image available in Downloads section (below)
KRT16O OTA (flo/WiFi) available in Downloads section (below)
As first mentioned by mandrsn1 in this post KRT16O "KitKat" is rolling out now.
I did not want to hijack that thread, but wanted to have a simple continuously updated first post that summarizes experiences and consolidates resources like OTA URLs, Factory Image flashing, etc.
You will soon be seeing comments from folks about how KRT16O affects the remaining Multi-touch and Random freeze/reboot issues on google product forums:
Google Nexus 7 product forum
KRT16O touchscreen experiences (near the end of thread)
KRT16O touchscreen experiences (2nd thread)
Mixed improvement with WiFi turned on and Bluetooth keyboards
pil-gss wakelock issue appears fixed
If you need to refer to the old JSS15R thread, it is here.
Initial impressions
Magnetic smart wake when wifi lost or deep sleeps appears to be fixed
Fix is in 4.01 bootloader - not necessary to flash 4.4 KitKat ROM (thx meekrawb)
Some bluetooth keyboard improvements
GPS/pil-gss wakelock issues appears to be fixed
New touchscreen software.
Mixed results, will likely depend on screen, some fixed, some not, improvement from JSS15R
ghost touches with aligned fingers mostly gone
stuck touches seem to be gone or greatly reduced
may still have missed touches
may still have slight jitters with aligned finger dragging
Does NOT include GEL (Google Experience Launcher)
install extracted N5 GEL and new Google Search if you want the new experience (thx jxr94)
use Nova Launcher if you want transparent status bars
Root can be installed in the same ways as 4.3
If you use NRT (Nexus Root Toolkit) follow this procedure (thx ruggie0)
Logistics (only for people trying to downgrade or mix/match rom/kernels)
You cannot "dirty" flash from 4.4 rom/kernel back to 4.3 rom/kernel, you'll need to wipe data/factory reset
4.3 kernels will not boot 4.4 rom
New FLO-04.01 bootloader.
New boot animation, sounds, icons.
New Easter Egg (thx magnumlove)
settings->about tablet->android version (rapidly tap 4 times)
Tap "K" a few times to make it spin, then see the final prize
New ART (Android Run Time) replacement for Dalvik VM
Enable using settings->developer options->select runtime
Apps should be odexed (stock is odexed)
First boot will take a while (possibly 15+ minutes)
New cloud/network print options
The new tap and pay setting only shows up if you already have NFC enabled. (thx albundy2010)
To get tap and pay working you need to get the N5 version of Wallet (thx ruggie0)
Quick benchmark1, benchmark2 of 4.4 and stock Dalvik (thx Vanillalite)
Quick benchmark1, benchmark2 of 4.4 and ART (thx Vanillalite)
Change summary:
JSS15R(4.3_r2.3)->KRT16O(4.4_r1.1) AOSP - TBD
Bootloader version: FLO-04.01
Android version: 4.4
Build/ROM version: KRT16O
Kernel version: 3.4.0-gb0eacf3 / Wed Oct 23 17:41:58 PDT 2013
Mini guides:
adb sideload (install OTA using stock recovery, no need to unlock, preserves user data)
flashing factory images (factory image restore, must be unlocked, option to preserve or wipe user data)
restore stock recovery (if you've installed custom recovery and want to go back to stock)
installing OTA-compatible root/SuperSU (will install SuperSU and fix so that it works with OTAs)
entering safe mode, bootloader, stock recovery (button press sequence can be tricky for fallen android)
Universal ADB drivers (use these if you have trouble with adb recognizing device)
Downloads:
KRT16O
KRT16O Factory Image - flo/WiFi (thanks Zaphodspeaks)
KRT16O Factory Image - deb/LTE (thanks Zaphodspeaks)
Source: pure stock
Format: flash in fastboot/bootloader
Guide: flashing factory images
Caveats:
requires unlocked bootloader
options to wipe or preserve user data
JSS15R->KRT16O OTA - flo/WiFi (thanks kenned88)
Source: pure stock
Format: flash with stock recovery (adb sideload) or as regular update.zip in TWRP/CWM
Guide: adb sideload
Caveats:
MUST be running unmodified JSS15R
does NOT require unlocked bootloader
if you are rooted with SuperSU 1.51 or earlier, OTA will fail near the end. See this post for explanation/fix.
if installing via twrp/cwm suggest installing SuperSU update.zip PRIOR to rebooting to preserve root and custom recovery
preserves user data
KRT16O repackaged TWRP/CWM-flashable - flo/WiFi (thanks scrosler)
Source: slightly modified stock
Format: flash as regular update.zip in TWRP/CWM
Caveats:
this is stock functionality but not pure stock binaries so will not work with future OTAs
bootloader 4.01 flash is a SEPARATE install (needed for magnetic smart wake fix)
this is pre-rooted with init.d support
odexed and deodexed versions
preserves user data
Stock kernel/recovery (unzip and flash via fastboot/bootloader)
fastboot flash boot boot.img
fastboot flash recovery recovery.img​
flo/WiFi
stock JWR66N kernel
stock JSS15J kernel
stock JSS15J recovery
stock JSS15Q kernel
stock JSS15Q recovery
stock JSS15R kernel
stock JSS15R recovery
stock KRT16O kernel
stock KRT16O recovery
deb/LTE
stock KRT16O kernel
stock KRT16O recovery
Bootloader - flo/deb (unzip and flash via fastboot/bootloader)
fastboot flash bootloader [filename]​
Bootloader v3.14
Bootloader v3.15
Bootloader v4.01
Root/SuperSU
UPDATE-SuperSU-v1.75.zip - install in TWRP or CWM for root (recommended for 4.4)
UPDATE-SuperSU-v1.55.zip - install in TWRP or CWM for root
Custom Recovery (unzip and flash via fastboot/bootloader)
fastboot flash recovery twrp.img​
TWRP 2.6.3.1 (recommended for 4.4)
Stock missing/modified JSS15R files
flo/WiFi
update-JSS15R-debuggerd.zip
update-JSS15R-thermald.zip
update-JSS15R-audio.a2dp.default.so.zip

Very Nice! I appreciate you taking the time to put this together and explaining things in detail as always! I now see why Nexus was always the way to go!

I installed this using the nexus root toolkit and it was successful. Appears TWRP is still installed as it used TWRP to install the zip. Will continue to do things to see what works and what doesn't.
Edit - Shutdown and chose to boot to recovery mode, got an android and red exclamation mark. Trying to see if I can reinstall Twrp now.

Finally! Thanks:good:

sfetaz said:
I installed this using the nexus root toolkit and it was successful. Appears TWRP is still installed as it used TWRP to install the zip. Will continue to do things to see what works and what doesn't.
Edit - Shutdown and chose to boot to recovery mode, got an android and red exclamation mark. Trying to see if I can reinstall Twrp now.
Click to expand...
Click to collapse
If you install the SuperSU update.zip immediately (prior to reboot) after you install the KRT160 update.zip, you will preserve root and preserve TWRP.

Initial impressions
New FLO-04.01 bootloader.
New boot animation.
New touchscreen software.
Change summary:
Bootloader version: FLO-04.01
Android version: 4.4
Build version: KRT160
Kernel version: 3.4.0-gb0eacf3 / Wed Oct 23 17:41:58 PDT 2013

The new tap and pay setting only shows up if you already have NFC enabled.

Still downloading..
Sent from my Nexus 7 using xda app-developers app

Added link to TWRP/CWM flashable KRT160 ROM (does not require you to be on stock)
KRT160 repackaged TWRP/CWM-flashable (thanks scrosler)
Source: slightly modified stock - Format: flash in TWRP/CWM
Caveats:
this is stock functionality but not pure stock binaries so will not work with future OTAs
this is rooted with init.d support
odexed and deodexed versions
preserves user data

Does anybody else get stuck on the boot animation when enabling ART?

touch is NOT fiexd!
It does boot with art enabled.
Does boor-ts-10 stil woks if enabled again ?

iPWNtehNOOB said:
Does anybody else get stuck on the boot animation when enabling ART?
Click to expand...
Click to collapse
Are you deodexed or running stock odexed?

im on supersu 1.69...
should i have to reflash to 1.55 as noted? or i cab simply reflash 1.69 after kitkat?
juuz wanna be certain

oTeMpLo said:
touch is NOT fiexd!
Click to expand...
Click to collapse
There is new touchscreen software included with this release.
Time will tell how it affects the various screens out there.
On the unit I'm testing on, the ghost touches when aligning fingers are pretty much gone. However there are still missed touches and slight jitter when sliding with fingers aligned. As with previous releases, best to let it settle in. Some problem might go away or other problems might show up.

lomonic said:
im on supersu 1.69...
should i have to reflash to 1.55 as noted? or i cab simply reflash 1.69 after kitkat?
juuz wanna be certain
Click to expand...
Click to collapse
1.69 should be fine. 1.55 works fine also. Only 1.51 and earlier have issues. There was a 1.6x release that had a placeholder update.zip from the author, but that is probably fixed by now.

thx sfhub for all that you've done.
system installed and is now rebooting. optimizing apps screen now.
I have also booted with ts-unlock prior to install... lets see how the new touch software works

oTeMpLo said:
touch is NOT fiexd!
It does boot with art enabled.
Does boor-ts-10 stil woks if enabled again ?
Click to expand...
Click to collapse
I've heard it could take a while for the initial boot when switching to ART
Sent from my Nexus 7 using Tapatalk 4

sfhub said:
Are you deodexed or running stock odexed?
Click to expand...
Click to collapse
Completely stock odexed.

Added KRT16O stock recovery/kernel to first post (unzip and flash with fastboot)
stock KRT160 kernel
stock KRT160 recovery

My update fails becaus audio_effects.conf has been modified. Could someone please send me the audo_effects.conf file from stock 4.3 please?

[Q] Updated directly to 5.0.1 from 4.4.4 (Skipped 5.0.0 update) Bootlooping problem

I have got a very different situation here. I was using 4.4.4 (KITKAT). I skipped 5.0.0 (LOLLIPOP) OTA update cause there were lots of rumours about the device going into a bootloop. Last week I DIRECTLY (HOW IS THIS EVEN POSSIBLE??) got a "5.0.1" OTA. I mistakenly installed it. So basically I skipped "5.0.0" update and directly installed "5.0.1" and now my Nexus 4 "UNROOTED" device is bootlooping. What should I do?
1. Should I downgrade to 4.4.4 with deleting/editing "-w" thing in "flash-all.bat"? I read somewhere that downgrading wipes all the data. What are my options going back to KITKAT?
3. What should I do to backup? I don't want to flash all my data.
4. Will the deleting "-w" thing work on "5.0.1" factory image?
5. Will the deleting "-w" thing work on "4.4.4" factory image?
6. Do I have to download SDK to perform all the tasks?
Any reply would be greatly appreciated. Thanks in advance. Cheers!

First download official nexus 4 5.0.1 factory image from here https://developers.google.com/android/nexus/images and extract all files till you have separate img files like boot.img, system.img etc.
Then download and install Wugfresh toolkit and install all necessary drivers.
Finally use the toolkit to install all img one by one, except the userdata.img.
At the end you will have a full stock working 5.0.1 system, with no data loss.

[Q] 5.1.1 OTA error on install

Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks

Had the same issue.... Just flashed the update without wiping the use info, so far seems to have worked... Not yet noticing much improvement though so don't get to excited.... Will keep watching it to see if it still crashes in sleep mode whilst sitting in the desk doc/charger...
Sent from my Nexus 7 using XDA Free mobile app
---------- Post added at 07:40 AM ---------- Previous post was at 07:32 AM ----------
Update: loads of system & none system apps still hanging and force closing some without the usual report/wait/OK option
So far:
- Google map
- Android System
- Facebook
- BBC iPlayer
- Chrome
Probably worth a full wipe and re flash to remove any gremlins.....
Sent from my Nexus 7 using XDA Free mobile app

FIXED
JustinSB said:
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Click to expand...
Click to collapse
I just flashed the system.img from my 5.1.0 archive (the recovery had already been flashed from the first time I tried it), waited half an hour for the OTA to flag up again & it all worked perfectly & upgraded exactly as it should. I haven't tried to root it again yet, as I want to see if it makes a difference.
So that's it, if your Nexus 7 2012 wifi won't let you install the 5.1.1 OTA, flash system.img & recovery.img from the 5.1.0 archive & you will be good to go, with all of your existing software, settings & data still intact. Naturally, you will need to re-root it though.

I flashed the 5.1.1 recovery, boot, and system images and then did a full wipe in recovery. Upon booting into the system, I was offered to restore my previous apps and data which all worked well but took a while to download and install the apps. I had to spend some time setting up the screens but 5.1.1 is running very well (better than 5.1) and I've since flashed twrp to get root. I do believe the wipe is important to get the best performance from the update.

I agree with the poster above me. Not wiping the device, cobbling together some unapproved update scheme pulled out of your ass, then complaining the performance sucks is just plain stupid. Do it right, and it will run butter smooth. But hey, I'm perfectly OK with snapping up several N7's DIRT CHEAP when all the idiots who can't follow instructions start dumping them on eBay and Craigslist thinking they're "broken". I have two cars that could use an in-dash install.

JustinSB said:
Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks
Click to expand...
Click to collapse
JustinSB,
Since you've already flashed your ROM's stock recovery, I *think* the problem you're encountering is the same one I had when I moved from 5.0.1 to 5.1: The rooting procedure you're using installs a non-stock kernel, which resides in the boot.img partition and is detected in the pre-flash checking phase of things in the OTA update.
If it were me, and I wanted to save a significant amount of time on the update (i.e. keep my userdata and bootloader partitions the same), I'd download the 5.1.1 image archive, uncompress/untar/unzip all the archives, and do the steps outlined here. They involve wiping the cache, recovery, boot, and system partitions and flashing the latter three with the updated images. Definitely do not fail to do any of those steps. Fwiw, and as I note later in that thread, I didn't re-flash the bootloader as it's the same in both ROMs.
All I did to finalize things was to boot to twrp via fastboot and generate a Nandroid back up, and then re-root using the CF-Auto-Root procedure. Afterwards I was set and experienced no particular system slowdowns. The whole process took about 15 minutes, including waiting for the dalvik-cache to reinitialize. I typically do not flash twrp, I just boot to it from fastboot as needed.
As a poster has pointed out in his non-diplomatic way, this is not the recommended path to updating, so if you encounter problems going this route, you can always do the full reset thing and re-load all of your userdata from a back up as a second option.
Which ever path you decide to follow, I wish you good luck.
cheers,
john

Well, I guess I'm going to do the unthinkable and reply to my own post to say that I've just followed the procedure I described above, this time to update from 5.1 to 5.1.1. It also took a total of 15 minutes with the longest portion of that time taken by the dalvik-cache reinitializing during the first reboot.
Good luck to you, OP. I hope that you upgrade goes as smoothly.
cheers,
john

Can I Ota update while rooted on stock firmware

I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop

I would like to know the same thing

Naruto101 said:
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
Click to expand...
Click to collapse
stkman32 said:
I would like to know the same thing
Click to expand...
Click to collapse
No you can't take an OTA if you have any modifications to /system (root). Have a look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?

Thanks for answering my question

roughriduz said:
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Click to expand...
Click to collapse
No way around it, any modifications will cause the update to fail.

Heisenberg said:
No way around it, any modifications will cause the update to fail.
Click to expand...
Click to collapse
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.

roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
User data should never be affected during an OTA anyway.

This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle

GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I am rooted now so I'll wait a while before updating an ota until there's a big deal of info. However, in the past if I was sticking with stock there's usually at least one developer who posts the updates with root and stuff built in so you can easily flash with twrp. So I'm kind of waiting for that. That or cataclysm or another awesome rom that's close to stock.

GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I wait for factory image for that build and flash over the new images when they become available (provided that root can still be achieved). Some will do a clean wipe and start fresh with the new build and reload in their apps and user data, others will just dirty flash the updated system (and boot/bootloader or whatever else was changed too).
If you think about it, it really isn't all that different from taking an OTA, the difference is that we're applying the commands to flash instead of having it automated. It's not that big of a trade off in my book.

I have 2 questions...
What is the easiest way to make flashing updates a breeze if I have mods in /system partition? I have heard of "freezing" them. Or is the only option... to delete every mod and flash updates? If so, should I keep a note of every change I make to/system?
And last... Should I make a backup of any file i am replacing or overwriting in /system? And if so, do I have to put them back how they were before flashing an update?

Delete

If you're rooted then you need to download the full factory image, extract system and vendor and flash those. Reflash SuperSU.

roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.

amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
Click to expand...
Click to collapse
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!

JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. Latest factory image is the latest factory image from the nexus factory images page. It's not an update like ota, but rather the entire image they would return you to stock if all is flashed.
2. Flashing a modified boot does not give you root. You still have to flash SU, so saying the modified boot contains root isn't right.
3. I flash boot first unless there is an updated bootloader.

JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. This can be whatever the latest factory image is at the moment. It’s currently MDB08M. All the OTA does is update your phone to whatever build it was made for. Factory images already have previously released updates built into them. You can upgrade but avoid downgrading unless you want to factory reset your phone.
2. I’m referring to the boot.img without root by @mrRobinson found https://www.androidfilehost.com/?fid=24269982086992320 although this process can be used for systemless root also. For systemless root you wouldn’t flash SuperSU in TWRP but instead sideload the SuperSU APK as per Chainfire’s instructions and use the matching systemless root boot.img
3. I don’t think it matters but as long as you have the matching modified boot.img with the system.img installed before you restart, you should be fine.

amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit..
Click to expand...
Click to collapse
What the heck did I do wrong here? I just tried to apply the November OTA update to my MBD08K build, it didn't work, and now I am in the process of doing a full reset and rebuild of my phone (flash-all of factory images from Google)
Here are the notes I made as I attempted to follow the procedure in this thread:
Code:
- Download latest build for MBD08K from https://developers.google.com/android/nexus/images?hl=en
- Extract boot.img, system.img, vendor.img to C:\adb (or wherever where adb and fastboot are
installed). You have to
- Right-click, open command window here
- Ensure USB debugging is enabled on phone (grant permissions on phone if you get the popup)
- In command prompt, "adb devices"
- Should see serial number and "device"
- type "adb reboot bootloader"
- Should get to bootloader screen with little android man lying down with hatch open
- type "fastboot devices" - should see your serial # again and "fastboot" beside it.
- type "fastboot flash boot boot.img"
- type "fastboot flash system system.img"
- type "fastboot flash vendor vendor.img"
- Use volume keys to boot into recovery (in my case TWRP)
- Swipe to allow modifications
- Install -> SuperSU.zip that you should have on your phone from last time.
- Reboot system
I saw a red "your phone is corrupt" scary message on startup... took a while to boot. Couldn't get past the dancing circles.
Interrupted boot, rebooted to fastboot, tried to flash old modified boot.img
Booted again, got encryption unsuccessful warning
Flashed most recent boot.img again, stuck booting forever
try again:
- flash system.img
- flash vendor.img
- flash boot.img (modified)
reboot to recovery - your device can't be checked for corruption (yellow warning instead of red)
- swipe to allow modifications
- reboot with TWRP, swipe to install SuperSU
- Encryption unsuccessful. Prompt to factory reset. Click OK. Boots through TWRP.
Give up, start flashing factory images.
EDIT: I might be the stupidest person alive. I think I should have been using the files for MDB08M. Arggghhhh. Someone please confirm I am an idiot.
Edit 2: Factory reset worked, I am at MDB08M. Now rooting again... grr. At least I backed up all my apps & settings to Google Drive with TB.
Edit 3: Rooted and restoring all apps with TB. If anyone has any insight into where I F'ed up I'd appreciate it.