Database Users

[Rooted OR Stock] Update Procedure For Lollipop 5.0 (OC1)

Build Number: N900AUCUEOC1/N900AATTEOC1/N900AUCUEOC1
Backup anything important you might have on your phone before proceeding any further
Look Here For 100% Stock Non-Rooted Lollipop (OC1):- http://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609
100% Stock Non-Rooted Procedure
[You HAVE to be on NL1 NOT NC2, NJ5 or anything else]
1. Make sure you are on 100% stock non-rooted NL1 currently (ie no ROOT, NO BUSYBOX, NO Xposed etc.)
2. If you are not sure then restore to complete stock using this NL1 files. : Here
3. Now download the following file and save it on the external SD card: Here
4. Reboot into recovery by pressing Volume UP + Power + Home
5. Once in recovery select "apply update from external sd"
6. Then select the above file you downloaded called "N900A_OC1_Stock(100%).zip"
7. Enjoy 100% Stock Lollipop 5.0 (OC1).
8. If you change your mind and want root... then you can! (Just follow the procedure below).
Look at Post #2 For Rooted Lollipop (OC1):- http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
100% Stock Rooted Original Procedure
1. Restore back to complete NC2 stock using this files: Here or Here
2. Root using Towelroot: Here
3. Install busybox: Here
4. Install SS: Here
5. Download the following files and save it on your external SD: Here and Here
6. Now follow steps 1 to 5 from this thread: Here
7. Once that is done go back to flash the above file you downloaded called "SM-N900A_NL1_Modem_Recover_Flashable.zip" and then after flash "N900A_OC1_Stock_Rooted.zip" using Safestrap.
8. Last, from the main menu press "Reboot," reboot into "Download" mode and flash the following files using Odin's AP slot: Here
100% Stock Rooted Alternate/Easier Procedure
1. Restore back to complete NC2 stock using this files: Here or Here
2. Root using Towelroot: Here
3. Install busybox: Here
4. Install SS: Here
5. Download the following files and save it on your external SD: Here
6. Extract the files from "stock-2015-03-24--23-26-50 LRX21V.N900AUCUEOC1" folder in .7z file you downloaded above into your Safestrap backups folder, i.e: ext-sdcard/TWRP/BACKUPS/xxxxxx (the name of your backups folder may vary. If a backups folder does not already exist you must first create a backup using Safestrap's "Backup" function before proceeding).
7. Use Safestrap's Backup Function to back-up User Data.
8. Perform an "Advanced Wipe" and wipe everything but your ext-sdcard.
9. From the main menu press "Restore" and restore the stock-2015-03-24--23-26-50 LRX21V.N900AUCUEOC1 backup.
10. Once complete press the back button twice to access your backups again and restore User Data.
11. Last, from the main menu press "Reboot," reboot into "Download" mode and flash the N900A_OC1_ALL_Other_Stock_Partitions.tar.md5 using Odin's PDA slot: Here
Download/Odin Mode Flash Counter after OC1 update: S2, T2, R2, A3, P2.....
GOOD NEWS..... Downgrade to NL1/NC2 still possible!!!!!​

OC1 Stock Rooted Very Easy Procedure
1. Download this .zip and save it on external sd:- Here
2. Reboot into Safestrap.
3. Wipe everything expect external-sd.
4. Flash the .zip you download above called, "SM-N900A_OC1_Lollipop_Rooted_Rom.zip"
5. Reboot.
6. Enjoy Rooted Lollipop
To access Safestrap (only works if you followed "Very Easy Procedure"
1. Bring up Power Menu.
2. And select "Safestrap Recovery" from the Reboot Menu.
3. Flash/Backup anything you need to do in SS.
4. Once you are done with that....
5. Flash the file called "SM-N900A_OC1_Kernel_Safestrap_Installer.zip" which is located under /sdcard/OC1_Kernel/
Odin: 3.10 http://forum.xda-developers.com/showthread.php?t=2711451​

Only try it if you know how to restore to NC2/NL1. I don't want everyone to jump in at the same time. Let some brave soul try first and report back.
NON-Root method success confirmation:- http://forum.xda-developers.com/showpost.php?p=59667605&postcount=27
Root method success confirmation:- http://forum.xda-developers.com/showpost.php?p=59668138&postcount=37

Here's a Mega mirror of the NC2 Odin files: https://mega.co.nz/#F!wg5wRQrQ!vR7a6pze9dgSWjbaRSyhWA
EDIT: Should be stock, so you will have to go about rooting with towelroot and installing busybox and Safestrap.

Awesome, downloading now!

Nice work
Cowboy from Hell on a twisted trail.
Koffed From my Big Ass Outlaw Phone.

Walter.White said:
Only try it if you know how to restore to NC2/NL1. I don't want everyone to jump in at the same time. Let some brave soul try first and report back.
Click to expand...
Click to collapse
Great work
here is safestrap recovery Lollipop installer
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip 9.1 MB
https://mega.co.nz/#!fAcA3JhL!-hK_TU6NamIJdvgwWdZ90VmOwBdRBxSL70VgC4sILwc

Walter can you run the Stock install on a NC2 non-rooted/stock device? Or does it have to be NL1?

kangi26 said:
Walter can you run the Stock install on a NC2 non-rooted/stock device? Or does it have to be NL1?
Click to expand...
Click to collapse
It has to be on NL1 or it will fail the file integrity check . OTA.zip for NC2 to OC1 is different one 1197.08 MB according to this.. https://www.att.com/esupport/article.jsp?sid=KB423151&cv=820

Just 2 questions!
I just have two questions!
1: can i apply this update from NJ5?
2:If i apply the update on Stock Recovery will it reset my phone?

Walter.White said:
It has to be on NL1 or it will fail the file integrity check . OTA.zip for NC2 to OC1 is different one 1197.08 MB according to this.. https://www.att.com/esupport/article.jsp?sid=KB423151&cv=820
Click to expand...
Click to collapse
Excellent, thanks! I'd hit the thanks button again, but I'm at quota

Javi22610 said:
I just have two questions!
1: can i apply this update from NJ5?
2:If i apply the update on Stock Recovery will it reset my phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=59667172
Cowboy from Hell on a twisted trail.
Koffed From my Big Ass Outlaw Phone.

Javi22610 said:
I just have two questions!
1: can i apply this update from NJ5?
2:If i apply the update on Stock Recovery will it reset my phone?
Click to expand...
Click to collapse
I can tell you that I just learned,
1. No you MUST be on NL1
2. I don't know...........

Yup, the zip contains a bunch of binary patch files.
You must be on NL1 to flash.

Javi22610 said:
I just have two questions!
1: can i apply this update from NJ5?
2:If i apply the update on Stock Recovery will it reset my phone?
Click to expand...
Click to collapse
1. Have to be on NL1.
2. I *think* it will but now 100% sure. So make sure you backup whatever that you need to.

Awesome! Will have to try it tomorrow
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

I know we must be on NL1 and all but I'm running evolution 3.0 which is based on NL1 so can I just flash the OC1 file in ss and Odin the kernel and call it a night?

@Walter.White, could you just load the OTA to the phone after ODIN'ing NC2?

majortaylor said:
I know we must be on NL1 and all but I'm running evolution 3.0 which is based on NL1 so can I just flash the OC1 file in ss and Odin the kernel and call it a night?
Click to expand...
Click to collapse
@majortaylor Nope. It wont work. Every step/warning of those steps is important.
@TeldenW Which procedure?

Keep in mind that the Rooted procedure will become bit easier once... someone provides me with the SS backup of Stock OC1 ROM.

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.

Android N Preview npc56p (flashable & image with no encryption and dm verification)

Android N Preview npc56p (flashable & image with no encryption and dm verification)
This thread is for the first Android N Preview.
For Android N Preview 2 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​** The following are instruction for installing Android N Preview image released by Google on 3/9/2016. After the installation you will have TWRP recovery 3.0.0-1 and the data partition will be erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery
1- You need to have TWRP installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N. If your internal storage is unencrypted before flashing it remains unencrypted. Your TWRP is also upgraded to 3.0.0-1.
Method 2: Flash update using a computer
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.0-1.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root
To obtain root after installing this update you should flash SuperSU 2.70 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726. Note that at least at the moment (as of SuperSU 2.70) the root method is a hack solution which requires a lot of further refinement. Many programs are still unable to acquire root and mount the system partition for R/W. However, it is possible to install the android terminal emulator, do an su, mount /system as rw, and do all the modifications within the terminal emulator. Of course you can always use TWRP to modify the system, for which you don't even need to root the device.

Hot dog! First for once... Thanks!
Sent from my Nexus 6 using Tapatalk

#2

will this wipe internal storage ? or only data partition?

For anyone interested...
I enrolled in the Developer Beta program and the OTA worked for me even though I was rooted with SuperSU v2.68.
However, despite installing TWRP 3.0.1 and then SuperSU v2.68 again, root doesn't stick. Fortunately the only critical previously-root-only app I want is a firewall, and Netguard doesn't need root. I can live for a while without Double Tap To Wake, Wakelock detector, Quick Reboot, etc. And the only app that seems to crash is BBC Radio Player, though BBC News and iPlayer still seem ok (warning about libraries, but still plays). And Battery Bot Pro seems to have lost its status bar display...
So it does pretty much what the warnings say - it's stable but not everything will work.

so if i flash this i will still have twrp once rebooted?

kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.

It would be nice moving forward if Google just made SuperSU/root part of their factory image under developer options. So once you enable developer option, there's a little toggle next to OEM unlock that says "root/SuperSU".
Would make life much easier.

simms22 said:
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
Click to expand...
Click to collapse
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
The zip doesn't include stock recovery so if you flash everything according to the instructions you will have twrp at the first reboot.

This kernel worked great thanks. I'm still decrypted and didn't have to wipe internal storage. I didn't run the .bat I manually flashed the img files. Wiped data with TWRP.

so can we flash this via twrp?

omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
no, those are IMG format, flash via fastboot.
I'd wait for root ready then flash...

omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
It literally says right next to the link, "Note that it is NOT a flashable zip."

PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
it says twrp recovery in title, so I was wondering....

what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721

chapelfreak said:
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
Click to expand...
Click to collapse
I flashed that boot img and now i am encrypted and boot-looping. No access to SD card.

Does this build have new bootloader and radio? If so, is it backward compatible to Marshmallow roms or do we need to flash back M bootloader and radio to get M roms work?
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
I lold at this. :laugh::laugh::laugh::laugh:

Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.

kclive said:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
Click to expand...
Click to collapse
Toggle on and off airplane mode. Turn off wifi and see if it works. I was at work and had to do this a few times

Flashed phh kernel (su-noverity - 3rd one) and installed this superuser. I now have root working.

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)
This thread is for the second Android N Preview.
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​** The following are instruction for installing Android N Preview 2 image released by Google on 4/13/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP installed on your phone.
2- Download this flashable zip..
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 2. If your internal storage is unencrypted before flashing it remains unencrypted.
For some people this didn't work. It seems to be the case when you have been encrypted by your previous Android N installation, in which case TWRP seems to have difficulty reading the file, and that seemingly Preview 2 doesn't play nice with TWRP. It works best when you are unencrypted and your recovery is 3.0.2-0. Thanks to @gammaxgoblin, @blitzerking1, @Michael in ATL, @HueyT, and @PhillyFlyer for debugging and hints.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.71 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133. Despite the fact that SuperSU 2.71 is supposedly re-written for Android N, there are still some apps that seem to have a problem obtaining root. The commonest complaint on this thread so far has been about Adaway. If you want to block Ads just manually do what Adaway does. Download a hosts file from any ad block list server such as http://winhelp2002.mvps.org/hosts.htm, copy the files on your sdcard, boot the phone into recovery, and using the TWRP file manager replace the file /system/etc/hosts with this file and set its permissions to 644 (rw-r--r--).

wouldnt flash first go. redl now
no flash again

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Same happened to me. It would not flash, same error

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
Same error for me as well. I can extract the zip and view the file it is talking about. I also tried on TWRP 3.0.1-0 and TWRP 3.0.2-0
Everything is working perfect for me with the new zip. I have a unencrypted phone and used 3.0.2 TWRP.

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
i tried 3.0.1 and 3.0.2 and i can also see the file

Method 2 works great

Method two works I used it myself

Shall I flash preview 2 directly from marshmallow?

Seems like TWRP is having a lot of troubles with each version of N Preview's encryption. I have same problem with both N6 and N6P, as do others in that forum too....:/

i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.

marius987 said:
i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.
Click to expand...
Click to collapse
Sorry for the stupid question. What do you mean for TB?

cerico76 said:
Sorry for the stupid question. What do you mean for TB?
Click to expand...
Click to collapse
I'm going to assume it stands for Titanium Backup.

Waiting for fixed method #1

outkastz said:
I'm going to assume it stands for Titanium Backup.
Click to expand...
Click to collapse
Ah,yes! Thanx!

Can someone please provide a link to the desktop website for the flashable zip?

Just to help with the installation of method 2, holding shift and right clicking a blank space in your unzipped folder, you can click open command window here. That will save you having to CD all the way to it.
Sent from my Nexus 6 using XDA-Developers mobile app

I did method 1. It upgraded fine. All my data remained. It killed root (expected this) and my TWRP. I was unencrypted before attempting.
I went and downloaded the latest TWRP and flashed via fastboot. Then downloaded latest SuperSU from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and flashed it via my newly installed TWRP. Root confirmed and all is well.
Good to go Thanks!

I've got an "Invalid boot image" issue :
Any tought ?

outpox said:
I've got an "Invalid boot image" issue :
Any tought ?
Click to expand...
Click to collapse
You may have to flash a previous stable release of marshmallow or lollipop from Google first and then try this because something seems to be corrupted in your system.

Is it possible to update to B381 (via OTA update) having a custom recovery?

Hi all,
I currently have a P9 Lite with VNS-L31C432B371 firmware installed.
Recently, I received the VNS-L31C432B381 update via OTA. Unfortunately, when the phone reboots into recovery mode, the update does not even start; instead, I get redirected to the custom recovery (TWRP 3.1.0.-2, system partition read-only) "homescreen".
Is there a way to update to B381 without wiping the entire phone?
Thank you for your time.

The OTA update system uses the EMUI stock recovery so no, there is no way you can update your phone through the updater by using the custom recovery

SALVO9 said:
The OTA update system uses the EMUI stock recovery so no, there is no way you can update your phone through the updater by using the custom recovery
Click to expand...
Click to collapse
Ok, thank you!
Another question: is there a way to obtain the stock EMUI recovery and flash it to execute the update?

_n0153_ said:
Ok, thank you!
Another question: is there a way to obtain the stock EMUI recovery and flash it to execute the update?
Click to expand...
Click to collapse
Yes.
Download your build's update.zip, extract the zip to desktop, you'll then have an update.app (you probably need the full ~2GB build, not OTA, e.g I use B370);
Extract recovery.img from the update.app via HuaweiUpdateExtractor;
boot to bootloader;
fastboot flash recovery recovery.img.
Done.

JHD94 said:
Yes.
Download your build's update.zip, extract the zip to desktop, you'll then have an update.app (you probably need the full ~2GB build, not OTA, e.g I use B370);
Extract recovery.img from the update.app via HuaweiUpdateExtractor;
boot to bootloader;
fastboot flash recovery recovery.img.
Done.
Click to expand...
Click to collapse
Thank you!
I succeeded in extracting and installing the recovery from the update.zip. Unfortunately the OTA failed anyway.
At this point, I think I should just wipe the phone and install the complete update from here.

_n0153_ said:
Thank you!
I succeeded in extracting and installing the recovery from the update.zip. Unfortunately the OTA failed anyway.
At this point, I think I should just wipe the phone and install the complete update from here.
Click to expand...
Click to collapse
Well I , like you, had a custom recovery. The 3-button method didn't work for me and even after restoring the stock recovery I was unable to install the update.
I unpacked the Update.APP file and flashed through fastboot the BOOT, RECOVERY, VENDOR and SYSTEM .img files and I was succesful but now I have the Model number as generic_a15 and Build number NRD90M test-keys. I can only assume some of the other img files carry the information about my phone. At the moment is stable enough but I can't open the Security menu.
If someone has any idea on how to flash the other img files, please let me know

okaar said:
Well I , like you, had a custom recovery. The 3-button method didn't work for me and even after restoring the stock recovery I was unable to install the update.
I unpacked the Update.APP file and flashed through fastboot the BOOT, RECOVERY, VENDOR and SYSTEM .img files and I was succesful but now I have the Model number as generic_a15 and Build number NRD90M test-keys. I can only assume some of the other img files carry the information about my phone. At the moment is stable enough but I can't open the Security menu.
If someone has any idea on how to flash the other img files, please let me know
Click to expand...
Click to collapse
well, if you flash your oeminfo zip, you should get it back

mjz2cool said:
well, if you flash your oeminfo zip, you should get it back
Click to expand...
Click to collapse
I only have old oeminfo.img packages, do you know how I can build one? There is a PRODUCT.img but it is considerably bigger than the oeminfo package that I have seen.
I flashed all the old B370 files, update.zip and update...hw_eu.zip, with DC Phoneix (a non free tool but saved me from.a bricked phone). After that, I flashed the new package and got the Security settings and Developer Options to work again.