Database Users

New Factory Image and Custom Recovery

So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?

geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess

MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.

bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr

Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...

MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.

geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.

MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.

I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img

Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.

mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????

mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?

rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.

In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.

mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.

How do I install the January security update on a rooted, unlocked Nexus6p?

Hello, dumb question. Like the subject says, how do I flash the OTA update on my phone? When I try to do it via the phone (notification tray), it gives me an error after the attempted flash.
I assume I need to download the OTA somewhere and sideload it. Where can I get it? My current build number is MMB29M
Thanks in advance
EDIT: I assume I just flash the system.img from the latest factory image?

Easiest way would be to download the factory image, edit the flash-all.bat to remove the -w flag (this is what tells it to wipe userdata) and flash the factory image.
Once you've flashed and booted, install TWRP, then flash systemless root in TWRP. If you have Xposed installed currently, you don't need to change anything with Xposed or your modules, just flash the Xposed installer again once you've flash TWRP and rooted, all your modules will still be installed and working once you flash the Xposed zip from TWRP.
This is what I have done for each of the security updates each month. If you can stand to wait, the new one for February will probably come out in 2-3 weeks, so it might save you from doing the process twice in a short period of time.
If you remove that -w flag from the batch file, the whole update process takes about 30 minutes, depending on how many apps you have to wait for it to optimize after flashing.

fury683 said:
Easiest way would be to download the factory image, edit the flash-all.bat to remove the -w flag (this is what tells it to wipe userdata) and flash the factory image.
Once you've flashed and booted, install TWRP, then flash systemless root in TWRP. If you have Xposed installed currently, you don't need to change anything with Xposed or your modules, just flash the Xposed installer again once you've flash TWRP and rooted, all your modules will still be installed and working once you flash the Xposed zip from TWRP.
This is what I have done for each of the security updates each month. If you can stand to wait, the new one for February will probably come out in 2-3 weeks, so it might save you from doing the process twice in a short period of time.
If you remove that -w flag from the batch file, the whole update process takes about 30 minutes, depending on how many apps you have to wait for it to optimize after flashing.
Click to expand...
Click to collapse
That's what I am using right now. However, with each month's update this process will take a lot of time. What I want to try is to apply the OTA update (which has much less size in MBs). That will work much faster. The only problem is that by using TWRP you will get stuck in the recovery. Did you tried to write back the original recovery and then take the OTA? Are there any chances to work with a systemless root?

foomanjee said:
Hello, dumb question. Like the subject says, how do I flash the OTA update on my phone? When I try to do it via the phone (notification tray), it gives me an error after the attempted flash.
I assume I need to download the OTA somewhere and sideload it. Where can I get it? My current build number is MMB29M
Thanks in advance
EDIT: I assume I just flash the system.img from the latest factory image?
Click to expand...
Click to collapse
If only there was a guide pinned at the top of the general section...
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sent from my Nexus 6P

Heisenberg said:
If only there was a guide pinned at the top of the general section...
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sent from my Nexus 6P
Click to expand...
Click to collapse
You mean there is a guide for that, how could I have missed it?

dratsablive said:
You mean there is a guide for that, how could I have missed it?
Click to expand...
Click to collapse
Not looking at the stickies?
Or not searching...

brichardson1991 said:
Not looking at the stickies?
Or not searching...
Click to expand...
Click to collapse
I forgot my <sarcasm> tags.

7.1.1 (NMF26F, Dec 2016) - 7.0.0 (NRD91P, Dec 2016)

It's out. Download factory images on the official site. Yay!
Link : https://developers.google.com/android/ota#top_of_page

changelog? does it fix the battery loss over night?

i have a question.
i'm on N5D91L with twrp installed. do i have to flash NRD91P and then NMF26F or can i skip the NRD91P?
thanks for the help!

Turtl3z said:
i have a question.
i'm on N5D91L with twrp installed. do i have to flash NRD91P and then NMF26F or can i skip the NRD91P?
thanks for the help!
Click to expand...
Click to collapse
You don't have to flash NRD91P. Android updates are always cumulative; you never have to flash versions other than the latest.

I am on official 7.0 right now. Is it possible to go the easy route and just flash Cache, System and Vendor img? Don't wanna reflash TWRP/root.

chinesecooler said:
I am on official 7.0 right now. Is it possible to go the easy route and just flash Cache, System and Vendor img? Don't wanna reflash TWRP/root.
Click to expand...
Click to collapse
don't need to flash cache. just flash boot, system and vendor and you should be good to go.

metpage said:
don't need to flash cache. just flash boot, system and vendor and you should be good to go.
Click to expand...
Click to collapse
Thanks but I am trying to avoid flashing boot.img as it means I will have to flash recovery and root again.

chinesecooler said:
Thanks but I am trying to avoid flashing boot.img as it means I will have to flash recovery and root again.
Click to expand...
Click to collapse
You can use flashfire to save root

sideloading now
EDIT: done and running.

chinesecooler said:
Thanks but I am trying to avoid flashing boot.img as it means I will have to flash recovery and root again.
Click to expand...
Click to collapse
You wouldn't have a working camera if you skip out on flashing the 7.1.1 boot.img.
Sent from my Nexus 5X using Tapatalk

Same radio same bootloader as previous versions or need to upgrade ?

Thanks all. I was stuck at the boot animation after only doing Cache, System & Vendor.
Had to reflash the whole set (except userdata), TWRP and SU.

For anyone worried about re-rooting and all... Download the Full Firmware package and flash it with FlashFire, just did it and it works perfectly, if you have any mods like the google assistant or "surround sound" mod, you will need to re-flash them but thats all.... easy as pie....
EDIT.... You will also need to re-do your build.prop edits if you did any....

new twrp

Hi guys, if I flash the new 3.3.3 which changed how it installs in the system, will I be able to get official Ota as in stock recovery??
Thanks

ujh said:
Hi guys, if I flash the new 3.3.3 which changed how it installs in the system, will I be able to get official Ota as in stock recovery??
Thanks
Click to expand...
Click to collapse
No. You'd still upgrade the same way you did before.

hartleyshc said:
No. You'd still upgrade the same way you did before.
Click to expand...
Click to collapse
Wiping everything, reflashing official rom and twrp? So what's the meaning of the new twrp feat?

ujh said:
Wiping everything, reflashing official rom and twrp? So what's the meaning of the new twrp feat?
Click to expand...
Click to collapse
Normally the way to upgrade as long as you are doing official is to download the OTA and do a local update.
Then install TWRP. I never wipe to upgrade.

tech_head said:
Normally the way to upgrade as long as you are doing official is to download the OTA and do a local update.
Then install TWRP. I never wipe to upgrade.
Click to expand...
Click to collapse
OK, since I only had custom roms and twrp and read somewhere that twrp didn't support official Ota I thought that to flash new Ota I had to wipe clean everything and reflash : x

ujh said:
OK, since I only had custom roms and twrp and read somewhere that twrp didn't support official Ota I thought that to flash new Ota I had to wipe clean everything and reflash : x
Click to expand...
Click to collapse
No.
If you are on the stock OOS or the Beta OOS as long as you stay on the same stock or beta; you download the OTA and do a local install.
This preserves your data and you only need to install TWRP and Magisk again.
I don't understand people that whine about having to install TWRP or Magisk again since it only takes about 5 minutes to do correctly.
I just do an OTA local install and hook the phone up to my computer and re-install TWRP, etc.

tech_head said:
No.
If you are on the stock OOS or the Beta OOS as long as you stay on the same stock or beta; you download the OTA and do a local install.
This preserves your data and you only need to install TWRP and Magisk again.
I don't understand people that whine about having to install TWRP or Magisk again since it only takes about 5 minutes to do correctly.
I just do an OTA local install and hook the phone up to my computer and re-install TWRP, etc.
Click to expand...
Click to collapse
Not whining at all. I said wipe everything, meaning EVERYTHING.

ujh said:
Not whining at all. I said wipe everything, meaning EVERYTHING.
Click to expand...
Click to collapse
Sorry, was not talking about you specifically.
Going from a custom ROM to OTA, you do need to wipe.
Going from any ROM to any other ROM, you need to wipe.
you can always "dirty flash" but there is no guarantee for wonky behavior.
On the other hand people want to take the OTA and preserve root.
Rooting take five minute so I don't understand the jumping through hooks to keep root.

MR3 Global March 2020 Security Update

It's available via OTA

JDBarlow said:
It's available via OTA
Click to expand...
Click to collapse
Are you able to use arter kernel with this update?

kountry83 said:
Are you able to use arter kernel with this update?
Click to expand...
Click to collapse
should be able to, I don't see why it wouldn't work

Arter works fine with it. I updated this morning.

Do you have to have stock recovery + locked bootloader to install?

BeardKing said:
Do you have to have stock recovery + locked bootloader to install?
Click to expand...
Click to collapse
I had Arter's kernel installed. I thought it would be enough to reflash stock kernel but that doesn't work. Don't think we should have to relock bootloader just to flash a system update....
Peace

chris5s said:
I had Arter's kernel installed. I thought it would be enough to reflash stock kernel but that doesn't work. Don't think we should have to relock bootloader just to flash a system update....
Peace
Click to expand...
Click to collapse
What do you mean by flash the system update? Sorry I'm new here, but what exact steps did you do? I am currently on a rooted MR2 with Arter 's kernel.

Received security updates notification a few hours ago.
Still no P-MR3 factory image on Razer dev site.
If need relock bootloader to update I guess I will wait a period. (I hope we can get Android 10 update

finixs said:
Received security updates notification a few hours ago.
Still no P-MR3 factory image on Razer dev site.
If need relock bootloader to update I guess I will wait a period. (I hope we can get Android 10 update
Click to expand...
Click to collapse
compared to MR2, we probably will need to wait for months until razer puts the factory images on their dev-page...
I really can't understand what takes so long for that last step. Just upload that crap and you're done, razer

Can the update be flashed in TWRP without disturbing Magisk or Arter's kernel? I've grabbed the update zip via a link I found by generating a bug report in the developer options and searching for "System_Update". I'm just wondering if it's safe to flash over everything.

Don't really need to relock bootloader and such, Just flash Stock recovery and the update will go through Smoothly, and then you can Reflash your twrp/magisk.

Monopod said:
Don't really need to relock bootloader and such, Just flash Stock recovery and the update will go through Smoothly, and then you can Reflash your twrp/magisk.
Click to expand...
Click to collapse
Didn't work for me. What system mods did you have in place? Kernel, root, etc?
Peace

chris5s said:
Didn't work for me. What system mods did you have in place? Kernel, root, etc?
Peace
Click to expand...
Click to collapse
Arter97 R12 Kernel with Twrp and magisk root.

Monopod said:
Arter97 R12 Kernel with Twrp and magisk root.
Click to expand...
Click to collapse
Did you just fastboot flash stock boot image?
Did you install f2fs.zip or any other mods?

chris5s said:
Did you just fastboot flash stock boot image?
Did you install f2fs.zip or any other mods?
Click to expand...
Click to collapse
No mods not even F2fs and Vold, for the stock boot image I simply fastboot flash it.

I flashed f2fs, wondering if that's why I can't flash update even after flashing stock kernel? ?
Peace

https://github.com/RadekBledowski/Razer_Phone_mods/blob/master/magisk_patched.img?raw=true
here's magisk patched version
to flash arter kernel you have to flash it via zip not fastboot so flash it first via fastboot and flash it again but in twrp as zip

So what I see is you can update without reloacking your bootloader by... (I'm asking if this is right)
1. Fastboot flash stock boot.img
2. Update normally
3. Reflash magisk, your custom kernel and what not.
Correct?

I've tried flashing back to stock kernel but it didn't work for me.

I usually perform the "reset to factory" task from the razer images (properly commenting the line that erases userdata)
After that you just are with original stock and you can update via OTA as usual.