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 you update Bootloader and Radio when flashing new ROMs?

Hey!
I've been flashing ROMs since the Nexus 5 and I actually just wondered how do you pals/gals flash the bootloader and radio whenever a update on the ROM gets available?
As far as I know, developers do not include the Radio and Bootloader when they update their ROMs and those need to be either flashed manually.
Once example is - as of the moment, Google just posted a new build "MMB29P" which has a new BL and Radio.
Anyone knows a tip on how to do this a smoother way?

smoother?
Just download it and flash it.

Download the factory image here
https://developers.google.com/android/nexus/images
Extract the tgz file once it's finished downloading. You will see the bootloader and radio images along with a zip that includes the rest of the stock files.
I assume since you know how to flash roms, you'll already know about fastboot. You just boot into the bootloader and use fastboot to flash the new bootloader and radio.
fastboot flash bootloader bootloader-angler-angler-02.45.img
and
fastboot flash radio radio-angler-angler-02.50.img

are you SURE there is a new bl/radio in the update?
afaik, it's a security update

Soulfly3 said:
are you SURE there is a new bl/radio in the update?
afaik, it's a security update
Click to expand...
Click to collapse
definitely new baseband version, hopefully to address the H/LTE issues many are having.
looks like new BL also

uicnren said:
smoother?
Just download it and flash it.
Click to expand...
Click to collapse
Yep, What I do before is flash to stock / relock Bootloader - then wait for OTA - then reflash the custom ROMs again. Yup .. not smooth at all but this is the reason why I started this thread

mattkroeder said:
Download the factory image here
https://developers.google.com/android/nexus/images
Extract the tgz file once it's finished downloading. You will see the bootloader and radio images along with a zip that includes the rest of the stock files.
I assume since you know how to flash roms, you'll already know about fastboot. You just boot into the bootloader and use fastboot to flash the new bootloader and radio.
fastboot flash bootloader bootloader-angler-angler-02.45.img
and
fastboot flash radio radio-angler-angler-02.50.img
Click to expand...
Click to collapse
Thanks for this! I will give it a try once PureNexus or Chroma provides an updated ROM.

Can anyone confirm if they can be done on the device, using flashify or something similar.
I'm on Linux here at work, and i'd rather not go through the pain by installing adb and the tools I have at home - but I want to be on the latest bootloader. As I spend most of my time on my Linux machine at work, it would be easy enough if I could find a way to do it on linux with ease.

Just to clarify,
If you are on a Custom ROM/Cyanogenmod 13 and a Radio/Baseband/Vendor update comes out can you flash these updates without factory reset or flashing back to stock. That's without?
And is Radio=Baseband=Vendor all the same thing just different brands names naming scheme.

Pheoxy said:
Just to clarify,
If you are on a Custom ROM/Cyanogenmod 13 and a Radio/Baseband/Vendor update comes out can you flash these updates without factory reset or flashing back to stock. That's without?
And is Radio=Baseband=Vendor all the same thing just different brands names naming scheme.
Click to expand...
Click to collapse
You can flash a radio anytime to see if different one improve your signal yes.
The vendor you flash must match what your running currently, can't mismatch vendors.radio and baseband are the same thing vendor is entirely a different thing
sent from my Nexus 6P, Note 5, Nexus 6 or Note 4

force70 said:
You can flash a radio anytime to see if different one improve your signal yes.
The vendor you flash must match what your running currently, can't mismatch vendors.radio and baseband are the same thing vendor is entirely a different thing
sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
Click to expand...
Click to collapse
So, in the main index for our phone I can flash the radio updates on Cyanogenmod and it won't affect my phone apart from the radio? Aren't the apart of the vendor though?

Pheoxy said:
So, in the main index for our phone I can flash the radio updates on Cyanogenmod and it won't affect my phone apart from the radio? Aren't the apart of the vendor though?
Click to expand...
Click to collapse
Find the bootloaders/radio you want (make sure it's the correct one) and flash via fastboot. Here's a guide if you need any help https://www.youtube.com/watch?v=jwEJJIQEt3Y

Pheoxy said:
So, in the main index for our phone I can flash the radio updates on Cyanogenmod and it won't affect my phone apart from the radio? Aren't the apart of the vendor though?
Click to expand...
Click to collapse
No the radio and bootloader have nothing to do with the vendor partition. And yes you can flash radios without it affecting anything but the radio. You'll find all radios in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
And instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

aval1392 said:
Find the bootloaders/radio you want (make sure it's the correct one) and flash via fastboot. Here's a guide if you need any help https://www.youtube.com/watch?v=jwEJJIQEt3Y
Click to expand...
Click to collapse
Heisenberg said:
No the radio and bootloader have nothing to do with the vendor partition. And yes you can flash radios without it affecting anything but the radio. You'll find all radios in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
And instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks just double checking, coming from a S3 LTE.

keplenk said:
Yep, What I do before is flash to stock / relock Bootloader - then wait for OTA - then reflash the custom ROMs again. Yup .. not smooth at all but this is the reason why I started this thread
Click to expand...
Click to collapse
You're going way out of you're own way doing updates like that. Why on earth are you relocking bootloader and taking ota. Just flash the image.
Sent from my Nexus 6P using Tapatalk

keplenk said:
Yep, What I do before is flash to stock / relock Bootloader - then wait for OTA - then reflash the custom ROMs again. Yup .. not smooth at all but this is the reason why I started this thread
Click to expand...
Click to collapse
I agree with the previous poster, you're making it much harder than it needs to be. All you need to do is flash the factory images to update. While you're flashing back to stock you just flash the updated build instead, that's it. Plus even if you did for whatever reason want to take the OTA there's no need to lock the bootloader.

Boot loader help
Heisenberg said:
No the radio and bootloader have nothing to do with the vendor partition. And yes you can flash radios without it affecting anything but the radio. You'll find all radios in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
And instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
If updated from mmb29v to mch19l am I suppose to update the boot loader also.thanks in advance

1981greg said:
If updated from mmb29v to mch19l am I suppose to update the boot loader also.thanks in advance
Click to expand...
Click to collapse
Updated how?

Heisenberg said:
No the radio and bootloader have nothing to do with the vendor partition. And yes you can flash radios without it affecting anything but the radio. You'll find all radios in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
And instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Is there no way to do this via a flashable zip? Reason I ask, my computer died. Don't have access to one with adb setup and they don't want me to do so... (Why is it TWRP can't do these images like in prior nexus devices?)

mrcooter said:
Is there no way to do this via a flashable zip? Reason I ask, my computer died. Don't have access to one with adb setup and they don't want me to do so... (Why is it TWRP can't do these images like in prior nexus devices?)
Click to expand...
Click to collapse
Unfortunately not.

WiFI wont work after root

I should start this off by saying that i have no idea how to root a device and i am now currently aware of how stupid my actions were.
I've searched the forums for about 2 hours now and i've yet to find a solution to this problem which is stressing me out like you wouldn't believe.
about i year ago i tried to root my Moto X Pure edition but i failed miserably so i returned to stock and lived without. This morning i decided i would try to root again but it isn't going so well.
I followed this guide: http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380 And everything worked fine until i noticed that my wifi wasn't working.
I then decided to flash back to the original boot image which i found from this site: http://androiding.how/systemless-root-moto-x-style-marshmallow-mph24-49-18/ But my wifi still refuses to turn back on
By now I'm a bit stressed out and not thinking straight. I then recalled that device encryption can screw with the rooting process so i decided to factory reset (how stupid can i get.)
So now im sitting at the welcome screen and my XT1575 cant find a wifi network so im going to have to restore my device over cellular data.
What do i do!?!?!?!?!!?!?
EDIT: i just realized the first link i posted was for the XT1572. I feel so stupid. how do i restore original functionality to my device?

I have had this issue before but on a Moto X Style (XT1572). You need to flash the modem again through fastboot/ADB. You first need to download the full stock firmware and extract it on a PC. Reboot your phone into bootloader mode and run the following command through command prompt/terminal:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
You may need to do this twice as it doesn't work always first time. Refer to this post for more information:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
HTH,
Ooms

dj_ooms said:
I have had this issue before but on a Moto X Style (XT1572). You need to flash the modem again through fastboot/ADB. You first need to download the full stock firmware and extract it on a PC. Reboot your phone into bootloader mode and run the following command through command prompt/terminal:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
You may need to do this twice as it doesn't work always first time. Refer to this post for more information:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
HTH,
Ooms
Click to expand...
Click to collapse
I've learned a lot in the past two hours. I did try to reflash the modem multiple times with multiple different files without any success. I don't think the method i was following works for XT1575 specifically.
I am currently back on stock with wifi working. I like the idea of a systemless root, but i couldn't find a method that works for the Pure. So i guess i will continue to run stock until i get a new phone (that might be a while.)

UC_Nightmare said:
I've learned a lot in the past two hours. I did try to reflash the modem multiple times with multiple different files without any success. I don't think the method i was following works for XT1575 specifically.
I am currently back on stock with wifi working. I like the idea of a systemless root, but i couldn't find a method that works for the Pure. So i guess i will continue to run stock until i get a new phone (that might be a while.)
Click to expand...
Click to collapse
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms

dj_ooms said:
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
Click to expand...
Click to collapse
Thanks for the suggestion. Before I try rooting again though, is there a way to completely backup my phone to my computer without using twrp? its a pain logging into all my app and setting everything up every time i try to root my phone.

UC_Nightmare said:
Thanks for the suggestion. Before I try rooting again though, is there a way to completely backup my phone to my computer without using twrp? its a pain logging into all my app and setting everything up every time i try to root my phone.
Click to expand...
Click to collapse
The only app I am aware of without root is Helium. I haven't tried it personally but I think you need to have an app running on your PC and the phone connected to it. I personally use TWRP with Nandroid Manager and Titanium Backup. These both need root though. You could always make a backup through TWRP prior to flashing the pre-rooted ROM, then flash the ROM as always recommended. If you run into issues, just restore the backup through TWRP, then flash the stock recovery back through fastboot/ADB to be backup to your original state.
HTH,
Ooms

dj_ooms said:
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
Click to expand...
Click to collapse
Maybe i am missing something but why would i want to flash stock recovery after i flash for example "XT1575 Rooted 6.0 Odexed with May security update" from the first link you provided?

UC_Nightmare said:
Maybe i am missing something but why would i want to flash stock recovery after i flash for example "XT1575 Rooted 6.0 Odexed with May security update" from the first link you provided?
Click to expand...
Click to collapse
I think i can answer my own question now. TWRP is a "custom recovery" and after i use TWRP i can flash something over it so that i can be stock. The terminology around these parts is quite confusing

i've gone and ****ed everything up again. I flashed twrp and then tried to install a zip from the first link you provided but my phone refused to unlock
I did a factory reset from within twrp and reinstalled the zip but now my wifi isnt working again.
Is rooting always such a pain in the ass?

UC_Nightmare said:
i've gone and ****ed everything up again. I flashed twrp and then tried to install a zip from the first link you provided but my phone refused to unlock
I did a factory reset from within twrp and reinstalled the zip but now my wifi isnt working again.
Is rooting always such a pain in the ass?
Click to expand...
Click to collapse
When rooting, there is always a risk. I have been flashing phones for over 10 years and it is always a learning experience. Even now i have occasionally done something and thought I've completely mucked up my phone. You just need to make sure you follow exactly what is stated as the procedure and if you run into problems, there is always someone at hand to help in this great forum.
Out of curiosity, did you follow the standard procedure for installing a new ROM? You will lose all data doing the standard procedure but can restore most stuff from your Nandroid backup. The steps I always do is:
1. Make a backup
2. Wipe data, system, dalvik/art and cache partitions
3. Flash your ROM
4. Wipe dalvik/art and cache again
5. Reboot
Click to expand...
Click to collapse
That is the standard recommended procedure for flashing all ROMs in TWRP. I have an EU XT1572 and have successfully used this ROM on my phone. The ROM contains everything you need including the modem. The modem is for the US XT1575 but worked fine on my phone. For sanities sake, I flashed the EU modem after and still had everything working.
Just another point, your phone needs to have been updated to Marshmallow before you can run one of these ROMs. If you are on Lollipop you may run into issues, especially from a radios perspective.
Another thing to point out is that all ROMs are started that you flash at your own risk. Developers will not be held responsible for anything going wrong. As long as you follow the guides and don't flash a ROM for a completely different device, you shouldn't run into any issues and more often then not can bring your phone back to a functional state if you do.
HTH,
Ooms

Flash twrp
Make backup
Flash su 2.62-3
Done.

Or...
1. Flash the factory image
2. Flash TWRP
3. Flash this attachment in TWRP, which will force install SuperSU 2.78 SR-1 systemless-ly. I've shared and posted about it before in this thread.
Nothing's changed with the attached zip here, except it has the latest version of SuperSU included as of this post.

December build are up

Go to the Google site guys...build is up...looks like one to rule them all

Here is a link to the OTA https://developers.google.com/android/ota#sailfish
Or if you want the factory image
https://developers.google.com/android/images#sailfish

Interesting there aren't separate builds...

Do they post a changelog anywhere? Curious what changes are in store.

pjd2011 said:
Interesting there aren't separate builds...
Click to expand...
Click to collapse
More interesting... it looks like the 6P will have a separate build for Verizon this month...

Waiting for non verizon build like the one from November

This build NMF26O seems to have a newer baseband than the Canadian update (NPF26J). Hopefully LTE issues sorted for those who have it.

I haven't finished extracting it...is the bootloader the same or has it changed?
Doing everything from my phone while the wife does the Christmas shopping

bwthor20 said:
Do they post a changelog anywhere? Curious what changes are in store.
Click to expand...
Click to collapse
http://android-developers.blogspot.com/2016/12/welcoming-android-711-nougat.html?m=1
Sent from my Pixel using Tapatalk

do i need to flash every OTA or just the last one? currently on 7.1.0 (Europe, NDE63U, Nov 2016)
google is not really informative at this point

I'm getting the December OTA as I type this. I have a 32GB Pixel with locked bootloader, from the Google Store.
EDIT: Now I'm getting it on my N5x as well. I haven't seen an OTA roll out this swiftly before.

OTA just popped up... Verizon pixel 128gb

Do those of us on Verizon have to worry about thisessing up unlocked bootloader if it's already unlocked??
Also curious if this patched the bootloader exploit used

has anyone flashed the factory image or side loaded the OTA for a non-VZ device yet?

spunks3 said:
has anyone flashed the factory image or side loaded the OTA for a non-VZ device yet?
Click to expand...
Click to collapse
Flashed factory img, carrier tmobile purch from BB

jay661972 said:
Flashed factory img, carrier tmobile purch from BB
Click to expand...
Click to collapse
very nice, which commands did you use to flash?
I'm currently rooted with TWRP alpha2 and SuperSU SR5. I'd like to update without losing data.
My system is on Sot B so I'm thinking:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_b system.img
fastboot flash vendor vendor.img
and then to get TWRP back:
fastboot boot twrp.img
- TWRP install twrp.zip
Reboot into recovery
- TWRP install supersu.zip
Does the above sound accurate?

spunks3 said:
very nice, which commands did you use to flash?
I'm currently rooted with TWRP alpha2 and SuperSU SR5. I'd like to update without losing data.
My system is on Sot B so I'm thinking:
and then to get TWRP back:
fastboot boot twrp.img
- TWRP install twrp.zip
Reboot into recovery
- TWRP install supersu.zip
Does the above sound accurate?
Click to expand...
Click to collapse
I use the flash-all file, i edit the file first to remove the -w so i can dont have to wipe the data
Cant answer the TWRP, not sure if it works with the new update

aholeinthewor1d said:
Do those of us on Verizon have to worry about thisessing up unlocked bootloader if it's already unlocked??
Also curious if this patched the bootloader exploit used
Click to expand...
Click to collapse
I just sideloaded the OTA onto my VZW Pixel with unlocked bootloader. My bootloader remains unlocked and I flashed twrp and SuperSU SR5. So far everything is working fine.
According to the dePixel8 website (http://theroot.ninja/depixel8.html) "dePixel8 is patched in Android 7.1.1 and newer, do not ask for future support or any kind of support."
So if you take this OTA from the phone (on an unlocked bootloader) you may well be locked out for good (unless someone finds another exploit).

stranula said:
I just sideloaded the OTA onto my VZW Pixel with unlocked bootloader. My bootloader remains unlocked and I flashed twrp and SuperSU SR5. So far everything is working fine.
According to the dePixel8 website (http://theroot.ninja/depixel8.html) "dePixel8 is patched in Android 7.1.1 and newer, do not ask for future support or any kind of support."
So if you take this OTA from the phone (on an unlocked bootloader) you may well be locked out for good (unless someone finds another exploit).
Click to expand...
Click to collapse
Thanks for the reply. I did some more reading and realized it's safe to install the OTA since I'm already unlocked. The update can't relock it. I already installed it via OTA and everything is ok

sorry, big time newb here. How do I flash the update if I have Verizon pixel with bootloader unlocked and with twrp installed? OTA doesn't work and I don't want to lose data....please help

Want stock kernel back

Guys i unlocked the bootloader of NPN 25.137-92 indian retin variant with nov 1 patch. I unlocked the bootloader and rooted the phone with SU, only problem is that cam stops working. Then i installed Elemental X kernel 2.02 as a workround to get the cam working which went ok . But i want to go back to the stock kernel, i dont want to flash whole rom . Is there is a way i get info or download link for the stock kernel. Is it possible that i can just flash the kernel. Will my camera app stops again if i do that?
Please reply

Stifmeister11 said:
Guys i unlocked the bootloader of NPN 25.137-92 indian retin variant with nov 1 patch. I unlocked the bootloader and rooted the phone with SU, only problem is that cam stops working. Then i installed Elemental X kernel 2.02 as a workround to get the cam working which went ok . But i want to go back to the stock kernel, i dont want to flash whole rom . Is there is a way i get info or download link for the stock kernel. Is it possible that i can just flash the kernel. Will my camera app stops again if i do that?
Please reply
Click to expand...
Click to collapse
Flash boot.img from your stock ROM using fastboot, just like you flash stock but this time only flash the file boot.img

Thanks for the prompt reply

Before trying the Fastboot method, do a backup of everything in case of a bootloop , after flashing the stock kernel, do a backup with Flashify

Broloff said:
Before trying the Fastboot method, do a backup of everything in case of a bootloop , after flashing the stock kernel, do a backup with Flashify
Click to expand...
Click to collapse
Or by temp-booting TWRP from fastboot

Bro another noob question can i flash the stock rom with twrp rather than going with fastboot method. I dont own a PC and new to this rooting and flashing stuff. Is there a way?

Stifmeister11 said:
Bro another noob question can i flash the stock rom with twrp rather than going with fastboot method. I dont own a PC and new to this rooting and flashing stuff. Is there a way?
Click to expand...
Click to collapse
The fastboot ROM can't be flashed with TWRP, we have a separate TWRP flashable stock ROM builds that are used specifically with TWRP and other custom recoveries (if available).
So to make it clear, you can't flash the fastboot ROM via TWRP, you need to download stock ROM from the below thread.
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Keep in mind to flash only the firmware that matches your device or the last update version you were on and never downgrade to a lower version than your device had when you stepped into the world of custom ROMs, root and etc otherwise you'll end up bricking your device.

Oh wow you just solved my problem i was really worried but this will do it... Yes i go through the instructions and flash the correct one... Thanks again