Database Develop

Issues with android security patch level

Hello everyone.
I`ve got rooted Nexus 6 with Franco kernel. From time to time it shows system security updates, which I install`s. But I notices on my android security patch level stops on January 2016 and still want to install February updates. Everytime N6 tries to install February updates. Does anybody know whats going on? Maybe it`s because I locked with security password on my twrp? After rebooting twrp show`s and I really dont know are updates installed well. I quess not. Can someone help?
And another question, does this android security updates will remove my root?

Shantarien said:
And another question, does this android security updates will remove my root?
Click to expand...
Click to collapse
Security updates will not work; unless the device is completely stock.

You should look at installing the OTA from this page - instructions are provided. If you want to retain the kernel,TWRP & and root you'll have to re-flash them when you're finished.
https://developers.google.com/android/nexus/ota
If you're unencrypted (I'm not - I prefer the security to an extra 10 minutes of battery life) do some reading first - I'm not sure how the OTA works with an unencrypted device. Maybe other members can advise both of us on this point.

Thx for answer`s.
Correct me if I wrong, but I`ve got stock rom, but with Franco kernel, and root, but it`s still stock, right? Does this could be a reason? All my data are encrypted, so maybe this could be a reason ( however after every update reboot I decrypt`s my data), I`ll switch off encrypting my N6 and try again update it.
----------EDIT------------
Guess, NLBeev was right. I can`t make an OTA update when my N6 is rooted, only manually method. I really afraid of this manually updates, because of losing something from my phone, or even brick it.

fear is something that xda can not help you with. itll happen through out life, in many situations. the only thing that you can do is deal with it and move on.

I manually update mine every update and have yet to have an issue.

I f you're encrypted (good!) then my earlier concern is irrelevant. Sideload the newest OTA at the link I gave you. I've done it now several times with two Nexus 5s and a Nexus 6. It's quick and simple and doesn't touch your data.
But I still always take a TWRP backup first and copy it to my laptop. Can't be too careful...

Once again thanks for help! I`ll try install them manually, as fast as I make backup by twrp.
Ach, I forgot, last question, which update should I download? I`ve got January system security updates, so should I download every single one by one? Or just last one (July 6.0.1 (MOB30O))?
Regards!

By "manually' do you mean extracting the separate components (system, radio, boot...)? I strongly recommend the OTA sideload method. Fast and simple, with no data loss.
You need only do it once. Download the MOB30O OTA and sideload it. Then if you want you can flash TWRP and root.

November update

https://developers.google.com/android/ota
I've update via adb.
Swiping via Soli seems much improved for me when using the music player.

What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.

ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
I followed the below steps. This is assuming you are already rooted on October patch level and want to maintain root.
1) Downloaded the factory images for the Nov update (https://developers.google.com/android/images) to the PC.
2) Extracted the zip file (make sure to extract the zip file inside the first one. That zip contains the .img file which we will need in step 4 ).
3) Edited the flash_all.bat file to remove '-w' parameter so that the data is not wiped.
4) Copied the 'boot.img' to the phone and used magisk manager to patch the boot file (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching).
Copied the patched 'magisk_patched.img' from the phone to the PC.
NOTE: I also disabled all magisk modules before the next steps. This is just to ensure that custom module don't mess up the update (have seen this with the Oneplus 7 PRO android 10 update when i had that device)
5) Reboot phone into bootloder and connect to PC
6) Flashed the update by running the flash_all.bat file (make sure to remove the '-w' parameter before flashing so that DATA is not wiped). I did run into issue where the vendor.img failed at flashing but a change of USB cable fixed that (I have seen this issue before. some cables just don't work in fastboot/adb).
7) Once the flashing completes the phone reboots and does some update after booting up.
8) Again reboot into bootloader. Flash the boot with the 'magisk_patched.img' that was copied in step 4.
Code:
fastboot flash boot magisk_patched.img
I always flash it on both the a & b partitions by using below command.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
9) Reboot the phone. At this point you have ROOT with Magisk and your custom kernel would be gone since stock/patched boot.img would have replaced it. You can re-flash your kernel (make sure the kernel has been updated for the November security update). Also at this point you can enable any modules that you may have disabled before the update.

I got november update now from ota..

Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
meek2100 said:
Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
Click to expand...
Click to collapse
Actually I just found the answer here: https://support.google.com/pixelphone/thread/18553639?hl=en
Pixel 4 (XL):
US (ATT & Verizon): QD1A.190821.014.C2
US (TMobile, Sprint, Google Fi) & UK carriers: QD1A.190821.014
All other carriers (AU/JP/CA/TW/US): QD1A.190821.007.A3

ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
The post above (post #3) that says to use the factory image isn't wrong, but it isn't the easiest method either.
You can side-load the OTA image. You can do this on a phone with a locked or unlocked bootloader and you don't need to modify any files to prevent it from wiping the phone. It's just like the OTA update and will not wipe the phone.
You can find the files and directions directly from Google. https://developers.google.com/android/ota
Once the update is done, you will need to reroot the phone using the standard modified boot image method and then reflash your custom kernel (after making sure it has been updated to the latest OTA version). Just be aware that while the actual flashing time is much shorter than taking the OTA normally, it may have to optimize all of the apps during the initial boot. Unfortunately it doesn't give you any indication this is going on (unlike during a normal OTA update) and therefore people tend to get impatient and reboot during the initial boot. Don't do this. Just be patient and let the phone do it's thing. My phone took about 20 minutes to boot initially after side-loading the Nov update because I have a decent number of apps that it had to optimize.

Oops, nevermind. fixed

How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.

Spookymyo said:
How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.
Click to expand...
Click to collapse
Instructions here
https://developers.google.com/android/ota

Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?

xxaarraa said:
Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?
Click to expand...
Click to collapse
Pure speculation on my part, but I wonder if Google didn't tweak the auto-white balance due to the complaints about how the phone handled white balance in pictures with a predominantly red color.

Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Sent from my Pixel 4 using Tapatalk

BubbaGumprc said:
Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Click to expand...
Click to collapse
I had the same issue, the check update function did not work on my P4. It was working great on my P3.

Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.

sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed

sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine

Does this undo the tweak to get Google pay to work with magisk? Or will we have to re do it?

ahsank128 said:
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed
Click to expand...
Click to collapse
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
thehartk said:
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine
Click to expand...
Click to collapse
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.

sn0warmy said:
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Look here: https://support.google.com/pixelphone/thread/18742521?hl=en

sn0warmy said:
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Yes flash the .007.A3 if you were on the .007 before. I went through the same problems with the .014 too but .007.A3 fixed it.

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.

Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.

Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.

falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.

i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.

I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*

[UPDATE/KEEP ROOT GUIDE] SEP 2020 (RP1A.200720.009) "FLAME" Magisk/Stock Boot Images

[UPDATE/KEEP ROOT GUIDE] SEP 2020 (RP1A.200720.009) "FLAME" Magisk/Stock Boot Images
PLEASE READ ALL ADDITIONAL NOTES IN THE FIRST 2 POSTS!!!
THIS IS A MAJOR UPDATE TO A NEW VERSION OF ANDROID AND CONSEQUENTLY COMES WITH A MUCH HIGHER RISK OF BOOTLOOPING IF YOU'RE NOT CAREFUL.
PLEASE DROP A QUICK THANKS IF YOU STILL FIND THESE GUIDES HELPFUL! :good:
(I PERSONALLY AM WAITING TO UPDATE TO ANDROID R (WAITING ON GRAVITYBOX) SO I WON'T BE ABLE TO HELP AS MUCH - PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT! )​
***IF YOU ARE STILL ON AUGUST / ANDROID 10 BUILD AND WANT TO UPGRADE TO CURRENT OCTOBER 2020 BUILD: I HIGHLY RECOMMEND FOLLOWING THIS SEPTEMBER UPDATE GUIDE FIRST (TO FIRST ENSURE YOU PROPERLY UPGRADE TO ANDROID 11, ELIMINATE ANY POTENTIAL ISSUES WITH BOOTLOOPING, MAKE SURE ALL MODULES ARE UP TO DATE AND COMPATIBLE, ETC). ONCE YOU ARE SUCCESSFULLY UPGRADED TO SEPTEMBER BUILD ANDROID 11, LET IT SETTLE AND PLAY AROUND FOR A WHILE BEFORE YOU FOLLOW THE OCTOBER UPDATE GUIDE.***
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4 XL "CORAL"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.200720.009, Sep 2020"!
Magisk Canary v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675562381
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675562110
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675562111
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.

READ THIS ENTIRE POST BEFORE PROCEEDING!
ADDITIONAL PRELIMINARY STEPS COMPARED TO PREVIOUS MONTHS - DO NOT SKIP!!!!:
A. Make sure all of your Magisk / EdXposed modules are updated for compatibility with R. For example:
* Magisk Module: Riru (Riru - Core) v21.3
* Magisk Module / EdXposed version: EdXposed v.0.5.0.6-android_r (4561) [this is a Canary build]
B. Recommend disabling any Magisk and/or Xposed modules that have not been tested with Android R.
C. Install latest Magisk Manager build: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.2/MagiskManager-v8.0.2.apk
D. Regular reboot the phone to make sure updates are applied before proceeding with the rest of the update process.
---------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "10.0.0 (QQ3A.200805.001, Aug 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-qq3a.200805.001-factory-dtbo.img: https://www.androidfilehost.com/?fid=8889791610682911608
flame-qq3a.200805.001-factory-boot.img: https://www.androidfilehost.com/?fid=8889791610682911606
September 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rp1a.200720.009-6dde3195.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot flame-qq3a.200805.001-factory-boot.img
3. fastboot flash dtbo flame-qq3a.200805.001-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload flame-ota-rp1a.200720.009-6dde3195.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot flame-rp1a.200720.009-magisk_patched-21.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
---------------------------​
ADDITIONAL NOTES FROM @sidhaarthm, WHO TESTED FOR ME - THERE'S SOME GOOD INFO HERE TO HELP PREP YOU BEFORE UPDATING YOUR PHONE (NOTE, THIS WAS DONE BEFORE MAGISK MANAGER 8.0.x BECAME STABLE, AND WAS FOR PIXEL 4 XL):
Okay, so I just successfully completed the steps and I'm booted into Android 11 without issues.
Here are my observations, notes and findings:
Pre-requisites:
- I installed the Canary Build of Magisk apk - it basically overwrote the existing installation of Magisk and worked straight away. I remained on the 'stable' update channel.
- I uninstalled all the Accent and Colour Mods from Tulsadiver as he is yet to update the mods for R11 (although he's confirmed its' possible and will publish it soon).
- I also deleted the AK3 Helper module from Magisk that gets flashed with Kirisakura Kernel since I was about to to flash the stock kernel anyway.
- I left the GPay SQlite Fix, Systemless Hosts, Busybox, V4A and AML Modules in Magisk enabled and as is.
Upgrade Notes:
- Followed your instructions to the T and the upgrade process was a breeze.
- I did extract the boot file from the factory ROM and patched it in Canary Magisk myself on my P4XL, but I chickened out at the last minute and flashed the boot file you had provided anyway. Reason being the flashed boot IMG I generated was 33,292 KB vs the one you had provided (and the ones I saw posted in other threads) were all 33,332 KB. So there was definitely some differences there and I just didn't want to risk it at that point.
- The phone got a bit hot during the upgrade process - around 40C+ but I suppose that's alright. Its' cooled down now and running okay.
- I did not flash any Kernel yet since I am waiting for the next official Kirisakura Kernel release for R11.
Findings:
- My P4XL booted first time, no bootloops etc - finalised the upgrade in a couple of minutes and everything thereafter seems smooth as butter.
- GPay works perfect without any tinkering (that's a big plus!)
- Device is rooted and all Root apps (AdAway, TiB etc), all work as normal. Camera, WiFi, Bluetooth, everything works, no issues whatsoever.
- Face Unlock works as normal and so do all the apps that use the biometric API to unlock (banking apps etc).
- SafetyNet fails on ctsProfile (evalType Hardware) but it was the same before upgrading to R11, so not surprised.
- Viper FX doesn't work post upgrading to R11 - that's expected and people have already reported the same 'failed at patching system' error on the main thread. Hopefully we get an upgrade at some point. Really gutted about this one as I love V4A!
Click to expand...
Click to collapse
Big thanks to @sidhaarthm for being an awesome and detailed tester!
-------------------​
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Coming from an earlier build than August 2020?
Download the September 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
Since this is a major jump to a new version of Android, I don't want to recommend this yet until someone tests it. If anybody tries this way successfully, please let me know so we can update this part. Thanks!

Link to October 2020 update guide: https://forum.xda-developers.com/pixel-4/how-to/update-root-guide-oct-2020-rp1a-201005-t4175957
P.S.: Yes, I know this is very late to post last month's update, but life has been super busy for me, my wife, and the "new" member of our family <3 <3 <3. Plus, the Pixel 4 is not my phone but my wife's phone, and on top of that I haven't updated either of us to Android 11 yet. I really wanted to make sure I wasn't leading everyone who follows my guides into bootloop / bricking hell, so along with the help of a great tester and an abundance of caution, I only released the September guide for the Pixel 4 XL. Then I just never got around to doing the same for the Pixel 4. Whoops, my bad. Anyway, there's some great news brewing on the GravityBox scene, and hopefully I'll be updating our phones in the near future and I can get back on top of these guides without worrying that there may be any issues that I can't help out with, not having performed the upgrades myself.
Anyway, enjoy! And please let us know if you have any issues.

i5lee8bit said:
Link to October 2020 update guide: https://forum.xda-developers.com/pixel-4/how-to/update-root-guide-oct-2020-rp1a-201005-t4175957
P.S.: Yes, I know this is very late to post last month's update, but life has been super busy for me, my wife, and the "new" member of our family <3 <3 <3. Plus, the Pixel 4 is not my phone but my wife's phone, and on top of that I haven't updated either of us to Android 11 yet. I really wanted to make sure I wasn't leading everyone who follows my guides into bootloop / bricking hell, so along with the help of a great tester and an abundance of caution, I only released the September guide for the Pixel 4 XL. Then I just never got around to doing the same for the Pixel 4. Whoops, my bad. Anyway, there's some great news brewing on the GravityBox scene, and hopefully I'll be updating our phones in the near future and I can get back on top of these guides without worrying that there may be any issues that I can't help out with, not having performed the upgrades myself.
Anyway, enjoy! And please let us know if you have any issues.
Click to expand...
Click to collapse
thanks mate ive been waiting for this!! i did not feel like accidentally bricking or doing factory clean/. i followed the guide exactly and i updated all magisk modules to latest versions available and downloaded latest xposed canary yahfa. everything working buttery smooth with no hic cups at all. thank you for continuing to make thes guides :good::good::good:
also happy to report the magiskprophide module seems to be working for me and i pass safetynet! i will also take your advice and wait a bit before ota ing to october build. thanks again mate!

strange issue after updating...
i5lee8bit said:
Link to October 2020 update guide: https://forum.xda-developers.com/pixel-4/how-to/update-root-guide-oct-2020-rp1a-201005-t4175957
P.S.: Yes, I know this is very late to post last month's update, but life has been super busy for me, my wife, and the "new" member of our family <3 <3 <3. Plus, the Pixel 4 is not my phone but my wife's phone, and on top of that I haven't updated either of us to Android 11 yet. I really wanted to make sure I wasn't leading everyone who follows my guides into bootloop / bricking hell, so along with the help of a great tester and an abundance of caution, I only released the September guide for the Pixel 4 XL. Then I just never got around to doing the same for the Pixel 4. Whoops, my bad. Anyway, there's some great news brewing on the GravityBox scene, and hopefully I'll be updating our phones in the near future and I can get back on top of these guides without worrying that there may be any issues that I can't help out with, not having performed the upgrades myself.
Anyway, enjoy! And please let us know if you have any issues.
Click to expand...
Click to collapse
Thanks again! I do have a strange issue after updating that hasn't happened before and I can't seem to track down. Updated per instructions, same as I do pretty much every month, however this time (I use the 3 button home buttons) my home and task button don't work. They flash to indicated that I have pressed them, but no luck. Also noticed that dark theme is not holding after reboot... No issues popped up during install. Tried process a second time, again no issue, same deal. Also tried booting into safe mode and the issue is in safe mode as well...anything else to try before wipe and reset? I don't believe its related to this process, just hoping someone has any ideas or experienced this after the latest update...I just can't seem to find anyone having the same issue...

JakeKane08 said:
Thanks again! I do have a strange issue after updating that hasn't happened before and I can't seem to track down. Updated per instructions, same as I do pretty much every month,
1) however this time (I use the 3 button home buttons) my home and task button don't work. They flash to indicated that I have pressed them, but no luck.
2)Also noticed that dark theme is not holding after reboot...
3) No issues popped up during install. Tried process a second time, again no issue, same deal. Also tried booting into safe mode and the issue is in safe mode as well...anything else to try before wipe and reset? I don't believe its related to this process, just hoping someone has any ideas or experienced this after the latest update...I just can't seem to find anyone having the same issue...
Click to expand...
Click to collapse
1) We still haven't updated to Android 11, so unfortunately I'm not sure if I can be of much help. Actually, I hate gesture navigation and plan to use 3-button myself, so hopefully this doesn't happen to us, lol. I would start with something simple and quick - try to toggle 3-button navigation off (system, settings, navigation option or wherever it is), then back on. Maybe try rebooting in between? Then of course see if there are any modules (Magisk or Xposed) that may be messing with the setting. I would think GravityBox, but it isn't compatible with Android 11 yet... If you have EdXposed, try disabling the module to disable Xposed and see if it still happens. If that still doesn't work, perhaps try booting into Magisk core-only mode, or just flash the stock boot and dtbo images (for the current month you're on) for testing to see if it works, then flash the magisk-patched boot image again afterwards to re-root. Maybe booting non-rooted / all modules disabled will easily tell you if the problem is an uncooperative module.
2) Actually, I've had this issue since as long as I can remember in owning the device (well, on my P4XL, and also happens on my wife's P4). We both have the setting for auto dark mode (morning / evening auto setting). We're still both on Android 10 and it does the same thing. If it's on dark mode and the phone is rebooted, it boots back into light mode. We would have to toggle it back manually. However, I do believe it does automatically switch to dark theme on the next scheduled time/day. Yeah, it's been like that for literally as long as I can remember, unfortunately. Kinda annoying but meh, whatever.
I'm also not sure what happens if you follow the guide twice, only because you would already be on the current month, then flashing the previous month's boot/dtbo images, and OTA'ing to what you're already on. I doubt it would permanently break anything though, but maybe try flashing your current build's dtbo image just to be safe? Not sure if the OTA directly updates the dtbo partition. For example:
Round 1: You follow my guide for September update. You are currently on August build. You are flashing the stock August boot / dtbo images to revert recovery to stock for your current patch level, then flashing the September OTA. You are now on all September images. You then flash the Magisk patched September boot image to re-root.
Round 2: You follow the guide again. You are already on September build, yet you're flashing the August boot / dtbo images to revert recovery to stock - but for a month back. See what I'm saying? But at least you said you got no errors. I would assume the 2nd round of following the guide didn't hurt anything, but this is also why I say maybe try flashing the stock dtbo image for the current month you're on.
Good luck! Let me know how it turns out. Still waiting to update, and having working 3 button navigation is a MUST for both my wife and I! Not trying to have an Apple Pixel here.

i5lee8bit said:
1) We still haven't updated to Android 11, so unfortunately I'm not sure if I can be of much help. Actually, I hate gesture navigation and plan to use 3-button myself, so hopefully this doesn't happen to us, lol. I would start with something simple and quick - try to toggle 3-button navigation off (system, settings, navigation option or wherever it is), then back on. Maybe try rebooting in between? Then of course see if there are any modules (Magisk or Xposed) that may be messing with the setting. I would think GravityBox, but it isn't compatible with Android 11 yet... If you have EdXposed, try disabling the module to disable Xposed and see if it still happens. If that still doesn't work, perhaps try booting into Magisk core-only mode, or just flash the stock boot and dtbo images (for the current month you're on) for testing to see if it works, then flash the magisk-patched boot image again afterwards to re-root. Maybe booting non-rooted / all modules disabled will easily tell you if the problem is an uncooperative module.
2) Actually, I've had this issue since as long as I can remember in owning the device (well, on my P4XL, and also happens on my wife's P4). We both have the setting for auto dark mode (morning / evening auto setting). We're still both on Android 10 and it does the same thing. If it's on dark mode and the phone is rebooted, it boots back into light mode. We would have to toggle it back manually. However, I do believe it does automatically switch to dark theme on the next scheduled time/day. Yeah, it's been like that for literally as long as I can remember, unfortunately. Kinda annoying but meh, whatever.
I'm also not sure what happens if you follow the guide twice, only because you would already be on the current month, then flashing the previous month's boot/dtbo images, and OTA'ing to what you're already on. I doubt it would permanently break anything though, but maybe try flashing your current build's dtbo image just to be safe? Not sure if the OTA directly updates the dtbo partition. For example:
Round 1: You follow my guide for September update. You are currently on August build. You are flashing the stock August boot / dtbo images to revert recovery to stock for your current patch level, then flashing the September OTA. You are now on all September images. You then flash the Magisk patched September boot image to re-root.
Round 2: You follow the guide again. You are already on September build, yet you're flashing the August boot / dtbo images to revert recovery to stock - but for a month back. See what I'm saying? But at least you said you got no errors. I would assume the 2nd round of following the guide didn't hurt anything, but this is also why I say maybe try flashing the stock dtbo image for the current month you're on.
Good luck! Let me know how it turns out. Still waiting to update, and having working 3 button navigation is a MUST for both my wife and I! Not trying to have an Apple Pixel here.
Click to expand...
Click to collapse
Sorry for the late reply and confusing with versions I was actually working with September images the entire time. I hadn't actually flashed back August images. After I installed the September OTA and it didn't work, I applied the entire September image to see if something in the OTA broke. No luck there either. I ended up backing everything up and performing a system wipe/recovery. Happy to report that all is working and actually working much better than before. Device is quite snappy and battery has improved, I find that at the end of the day I have about 10-15% more battery than I had before. I'm sure that this is probably due to less bloat and/or something was definitely not working right on the system.

Fixing bootloop?

so my bramble spazzed and did a soft reboot and then the system ui wouldn't load (I was able to use the phone, but not the status bar, navbar). i disabled the lockscreen security and removed my magisk modules. then i tried flashing the stock firmware (december) *after erasing the -w*, then i tried sideloading the december ota via recovery, then i tried to do the same withe november versions and then again the december, you get the idea. nothing doing, the best i get is it'll get to "pixel is loading" for a split second then go to bootloader. anyone have any suggestions for me?
sorry, asking on the P5 forum because the phones are so similar the P5 forum is more active.

mistermojorizin said:
so my bramble spazzed and did a soft reboot and then the system ui wouldn't load (I was able to use the phone, but not the status bar, navbar). i disabled the lockscreen security and removed my magisk modules. then i tried flashing the stock firmware (december) *after erasing the -w*, then i tried sideloading the december ota via recovery, then i tried to do the same withe november versions and then again the december, you get the idea. nothing doing, the best i get is it'll get to "pixel is loading" for a split second then go to bootloader. anyone have any suggestions for me?
sorry, asking on the P5 forum because the phones are so similar the P5 forum is more active.
Click to expand...
Click to collapse
Are you booting on the right slot ?

jaythenut said:
Are you booting on the right slot ?
Click to expand...
Click to collapse
Thanks, yes I was. I ended up dirty flashing the stock firmware from December and from November and sideloading otas from both months over and over till it was working again. Took all day but I saved my data. I was flashing the all carrier December image as they was the one I was on, not flashing verizon one did the trick. Something to keep in mind for next time.