Recent content by Brian706

Yes. Just make sure you are patching the boot.img for the version you will be using. If you upgrade to the November patch, make sure you patch the November boot.img and flash that after updating.

I have not done it but according to the instructions, you can restore the stock boot.img via magisk. Alternatively, you can always download the factory image from and extract the boot.img from there. I would think you already have a copy of the stock boot.img on your device and/or PC. Didn't...

Ah, yeah. Custom ROMs will be a whole other beast! I prefer keeping stock these days but rooting for AdAway and Titanium. But surely you will be able to flash updates of custom ROMs a lot easier than this.

Thanks for this by the way. I will try taking the official ota next time. I just assumed it wasn't possible as taking ota when rooted has always been a no-no and seemed counterintuitive. So I always just sideload the ota after flashing the stock boot.img. After thinking about it though, it makes...

It won't really change anything as far as I know. You'll still want to update using the same methods. You won't be able to take an ota update with TWRP installed as TWRP resides in the boot partition. You will still need to return to the stock boot.img before updating and then add TWRP and root.

You can still use an ota image after previously using a factory image. If you updated this time by flashing the full factory images that's fine. You will still be able to sideload the ota image next time.

I can't confirm 100% but as far as I know it should. Doesn't viper have an option to back up your settings just to be safe? The thing about using the ota image is that it's not like flashing a factory image. It's just like taking an ota update. It shouldn't affect your apps or app data.

Here's what I do when I update. 1.) fastboot flash the stock boot.img for your build. 2.) Download the factory image and the ota image for the version you are updating to. 3.) Extract the boot.img from the factory image package and patch via magisk. Then copy the patched boot.img to your PC...

Haha, yeah, might just be the way it's displaying on my phone. They don't look that different. A couple things to maybe try. Maybe try repatching the boot.img. perhaps something went wrong in the patching method? Also, you double-checked that you downloaded the factory image/boot.img that...

slaydog That's where I downloaded mine from (the link you posted). This is what it looks like. Sorry, not on PC at the moment but downloaded on my phone to see the file structure.

Are you guys using the platform tools that you download directly from the factory images page? I only ask because previously I was using a smaller package (just adb/fastboot) even though it was the latest version and I had issues flashing the factory images. After I downloaded the platform tools...

Ahhhhh, so happy right now! Donation incoming. Thanks topjohnwu

I still don't understand why people interested in unlocking the bootloader and/or rooting buy the Verizon version. Just get the unlocked. You know Verizon is gonna lock you out at every step. Not intending to sound rude. I'm genuinely curious. Is it because you get a carrier subsidized...

Just curious if anyone tried to fastboot boot the modified boot.img instead of fastboot flash. I was thinking about the original Pixel XL and how this was the case, though I'm unsure about with magisk. I've never used it, I used SuperSU. But with chainfire retiring, might be time to check out...

I don't believe it will. A factory reset just wipes user data, it doesn't touch the system partition. Only way to undo changes to the system is to restore a backup of the system via TWRP or flash factory images. You can flash the factory images without wiping data though. Edit the...