Develop Bugs

Update from PI3 to official Nougat.

I've seen some posts about updates to official Nougat failing, so I decided to upload the update.zip to get to Nougat. I'd like to note that I didn't update using the update.zip method, so let me know if anyone runs into any issues. Hopefully this helps you guys out.
1) Make sure you are on official NON-ROOTED PI3. Also, make sure you enable any disabled packages.
2) Create a folder on your SD card named fota.
3) Download this zip and rename it to update.zip, then put it in the fota folder you created.
4) Turn off the phone and boot into recovery-volume up+home+power at the same time.
5) Wait a minute for the dead android to go away and recovery finally boots, then select update from SD card. Select the update.zip.
Here is the Odin files for PI3 for those that need it. G930VVRU4API3

Testing now
---------- Post added at 11:51 PM ---------- Previous post was at 11:17 PM ----------
Still not working. Didn't get the log though, but there was a mounting error and then I believe I saw something status 7. Not sure what else is wrong.

Are you on PI3?

CVertigo1 said:
Are you on PI3?
Click to expand...
Click to collapse
I am.

Download "Phone Info *Samsung*" from the PlayStore. Open it up and upload a screenshot of the firmware page.

CVertigo1 said:
Download "Phone Info *Samsung*" from the PlayStore. Open it up and upload a screenshot of the firmware page.
Click to expand...
Click to collapse
Thank you for your help.

Everything appears to be in order. Is your SD card encrypted? I recall that being an issue with the beta builds.

CVertigo1 said:
Everything appears to be in order. Is your SD card encrypted? I recall that being an issue with the beta builds.
Click to expand...
Click to collapse
It is not

The best advice I have is to Odin all four PI3 files, but not Home_CSC. It will give you the cleanest install and take everything else out of the equation. I'd backup everything with Smart Switch first, then restore it all after updating.

CVertigo1 said:
I've seen some posts about updates to official Nougat failing, so I decided to upload the update.zip to get to Nougat. I'd like to note that I didn't update using the update.zip method, so let me know if anyone runs into any issues. Hopefully this helps you guys out.
1) Make sure you are on official NON-ROOTED PI3. Also, make sure you enable any disabled packages.
2) Create a folder on your SD card named fota.
3) Download this zip and rename it to update.zip, then put it in the fota folder you created.
4) Turn off the phone and boot into recovery-volume up+home+power at the same time.
5) Wait a minute for the dead android to go away and recovery finally boots, then select update from SD card. Select the update.zip.
Click to expand...
Click to collapse
What if you are on PKC? You think it will still work?

Crsdr37 said:
What if you are on PKC? You think it will still work?
Click to expand...
Click to collapse
Im on pkc also

Probably not, but you are welcome to try. If it doesn't work, then flash back to PI3 and update from there.

Also if you use package disabler pro like most of us. Ensure you go back into there and enable all bloatware you can re-disable after the update goes through

Crsdr37 said:
Also if you use package disabler pro like most of us. Ensure you go back into there and enable all bloatware you can re-disable after the update goes through
Click to expand...
Click to collapse
I already put this in the steps, but I guarantee a lot of people will forget to follow it lol.

I got mine updated. Here's what I did.
I reluctantly used the Verizon software repair tool to "repair" the OS. It took quite a while but did reload everything. After that I just took the OTA and it seemed to work fine. I would imagine that Odin would have worked too.

I'm on a VZ Galaxy S7, PI3 firmware on Boom Mobile (VZ MVNO). Tried OTA update, Samsung Smart Switch and Verizon Software Upgrade. All 3 are showing that my firmware is up-to-date on version 6.0.1 PI3. Have they just not rolled it out to everyone?
Is my only option to use the procedure on here?

mogulman01 said:
I'm on a VZ Galaxy S7, PI3 firmware on Boom Mobile (VZ MVNO). Tried OTA update, Samsung Smart Switch and Verizon Software Upgrade. All 3 are showing that my firmware is up-to-date on version 6.0.1 PI3. Have they just not rolled it out to everyone?
Is my only option to use the procedure on here?
Click to expand...
Click to collapse
Updated using the process from OP, worked fine.

I was on PI3 firmware and I kept checking without getting the new software from yesterday. Just now I connect my phone to the PC and open up Smart Switch, it tells me the new update is available.

I was having this same problem. I couldn't get my phone to take the OTA even after unrooting and I had to end up using Odin and flashing that BL file as well as the other three that you normally flash. give that a go if you're still having problems!

Upgraded directly from PKC (beta) using SamFirm to download and flash new verizon firmware via odin. Worked great. Didn't have to downgrade back to pe1.

full Odin package *N920AUCS4CQA1* help you up to Nougat quickly

Can not wait for the official Nougat version! Here are the latest model which I can get for you.
Not much to say，here's link for QA1, every person can flash that with Odin and then OTA to Nougat by @norbarb 's way.
Simply speaking, upgrade is divided into two steps. First flash my QA1. Then usd adb update to QC5.
Flash QA1 by Odin:
https://mega.nz/#!EFAiXTKC!S0LvpCIedF_ubVgszflUaN3U_O2zwQoeH6ku68gqnDM
QA1-QC5 Adb files from @norbarb
https://docs.google.com/uc?id=0B4sOy1rlqVoYdnROaFU4LXQybjA&export=download

Warning
Whether Odin or Adb will formate data on your phone. Please backup and then do it.

smxwang said:
Can not wait for the official Nougat version! Here are the latest model which I can get for you.
Not much to say，here's link for QA1, every person can flash that with Odin and OTA to Nougat by @norbarb 's way.
Simply speaking, upgrade is divided into three steps. First flash my QA1. Then usd adb update to QB2. Finaly using adb update to QC5.
Flash QA1:
https://mega.nz/#!EFAiXTKC!S0LvpCIedF_ubVgszflUaN3U_O2zwQoeH6ku68gqnDM
QA1-QB2:
https://forum.xda-developers.com/att...-plus-t3563086
QB2- Nougat:
https://forum.xda-developers.com/att...rvers-t3574757
Click to expand...
Click to collapse
Thanks man...great job

Is this ready for "daily driving"?

Iam on PBH4 (agaust security patch)
can i flash QA1 directly?

TeldenW said:
Is this ready for "daily driving"?
Click to expand...
Click to collapse
Working great for me as DD. Battery life is better than 6.x, but I'd expect that it'd be a little better anyway after a full wipe & fresh install.

samsung lo said:
Iam on PBH4 (agaust security patch)
can i flash QA1 directly?
Click to expand...
Click to collapse
I was on the PK1 yesterday, then I ODIN'd to PL1 (using Norbarb's instuctions and wiped my device in the process).
I then realized that since the device was already wiped, I simply ADB directly to QC5 (as it was already 1.5GB in size and should already contain the previous updates).
Battery life is now horrible, although I'm still trying to get used to the new features by turning off / disabling what I don't need. The update is worth it. as the theme makes me "feel" as though I got a new device. The touchwiz additions replace quite a number of third party apps that I'd have downloaded separately otherwise.

jaxf250 said:
Working great for me as DD. Battery life is better than 6.x, but I'd expect that it'd be a little better anyway after a full wipe & fresh install.
Click to expand...
Click to collapse
As you probably did, I'm using a non-rooted AT&T Galaxy Note 5 (N920A}. I'm familiar enough with ODIN to know that I'll probably mess it up the first try... And spend a lot of time figuring out my mistakes.
Did you have any difficulty with the update process?

TeldenW said:
As you probably did, I'm using a non-rooted AT&T Galaxy Note 5 (N920A}. I'm familiar enough with ODIN to know that I'll probably mess it up the first try... And spend a lot of time figuring out my mistakes.
Did you have any difficulty with the update process?
Click to expand...
Click to collapse
The only problem I encountered was the need to perform the large address aware fix to adb so it would sideload the S4CQB2-to-U4EQC5.zip file for me, otherwise it went fine. Just takes time. I went step by step after first backing all my stuff up. I was on an older MM release that had not been patched with any of the last 3 or 4 security patches, so I began with a complete wipe and ODIN of CPK1. Then sideloaded the rest, one at a time and switching USB debug on each time before the next update: CPK1-to-PL1, then PL1-to-CQA1, then CQA1-to-CQB2, then the final S4CQB2-to-U4EQC5. About 90 minutes maybe, a little less? I can't recall, but wasn't a big deal. It took Google longer to load my 180 apps back on at the end LOL. All the tips (like the large address fix) are in the other thread - just read it over before starting. I see we have a new update too to version QC6.... I may flash that or wait another week or two to see if more updates come out. Honestly it is running just great and I have no issues. Snappy. HTH

I will post in Nougat update thread new update to 4CQB2 to 4EQC6 firmware. Please let me know there if you want 4CQA1 to 4EQC6 update also.

jaxf250 said:
The only problem I encountered was the need to perform the large address aware fix to adb so it would sideload the S4CQB2-to-U4EQC5.zip file for me, otherwise it went fine. Just takes time. I went step by step after first backing all my stuff up. I was on an older MM release that had not been patched with any of the last 3 or 4 security patches, so I began with a complete wipe and ODIN of CPK1. Then sideloaded the rest, one at a time and switching USB debug on each time before the next update: CPK1-to-PL1, then PL1-to-CQA1, then CQA1-to-CQB2, then the final S4CQB2-to-U4EQC5. About 90 minutes maybe, a little less? I can't recall, but wasn't a big deal. It took Google longer to load my 180 apps back on at the end LOL. All the tips (like the large address fix) are in the other thread - just read it over before starting. I see we have a new update too to version QC6.... I may flash that or wait another week or two to see if more updates come out. Honestly it is running just great and I have no issues. Snappy. HTH
Click to expand...
Click to collapse
Dude, thanks man. I'm gonna do my research over the next couple days.
Good lookin' out.

norbarb said:
I will post in Nougat update thread new update to 4CQB2 to 4EQC6 firmware.
Click to expand...
Click to collapse
I just got QC5 sideloaded last night. I stayed up restoring my apps and data as close as I had it before on my PK1. This was a time-consuming process.
norbarb said:
Please let me know there if you want 4CQA1 to 4EQC6 update also.
Click to expand...
Click to collapse
You can't now just drop the QC6 on me like that so I have to go through that process all over again.
Hence I'll say "No, thank you" :highfive:

norbarb said:
I will post in Nougat update thread new update to 4CQB2 to 4EQC6 firmware. Please let me know there if you want 4CQA1 to 4EQC6 update also.
Click to expand...
Click to collapse
that's great. No matter what new model is better than elder one.

jaxf250 said:
The only problem I encountered was the need to perform the large address aware fix to adb so it would sideload the S4CQB2-to-U4EQC5.zip file for me, otherwise it went fine. Just takes time. I went step by step after first backing all my stuff up. I was on an older MM release that had not been patched with any of the last 3 or 4 security patches, so I began with a complete wipe and ODIN of CPK1. Then sideloaded the rest, one at a time and switching USB debug on each time before the next update: CPK1-to-PL1, then PL1-to-CQA1, then CQA1-to-CQB2, then the final S4CQB2-to-U4EQC5. About 90 minutes maybe, a little less? I can't recall, but wasn't a big deal. It took Google longer to load my 180 apps back on at the end LOL. All the tips (like the large address fix) are in the other thread - just read it over before starting. I see we have a new update too to version QC6.... I may flash that or wait another week or two to see if more updates come out. Honestly it is running just great and I have no issues. Snappy. HTH
Click to expand...
Click to collapse
Where did you find the QA1-to-QB2 file?

trsanning said:
Where did you find the QA1-to-QB2 file?
Click to expand...
Click to collapse
Here : http://forum.xda-developers.com/showthread.php?p=71184332
Originally from servers
Clicking from Edge of Galaxy

Help
Hello !
Please help, yesterday i try slideload with ADB from U2AOI6 to U2APB2 , i don't know how i did it, but now i have bootloop and messages " dm-verity verification failed "... " update from ADB is disabled " in downloading mode ... Is there any issue to do not loose my data. ..? If not, is the link of S4CQA1 provide here sufficient to make a full flash with odin ?

dakkidd said:
Hello !
Please help, yesterday i try slideload with ADB from U2AOI6 to U2APB2 , i don't know how i did it, but now i have bootloop and messages " dm-verity verification failed "... " update from ADB is disabled " in downloading mode ... Is there any issue to do not loose my data. ..? If not, is the link of S4CQA1 provide here sufficient to make a full flash with odin ?
Click to expand...
Click to collapse
ADB sideload always wipes after it completes
There is an app named Flashify which does not wipe after applying updates but that only works on rooted phones (and you cant root the AT&T Note 5)
Therefore no, there is (currently) no way to prevent sideload wipe

Thank you very much Dezborders!
Now it will be my first time to use Odin, pleaz can you give me the link of the more stable marshmallow for you on N920A... ?

dakkidd said:
it will be my first time to use Odin, pleaz can you give me the link of the more stable marshmallow for you on N920A... ?
Click to expand...
Click to collapse
Seriously dude!
See Page 1 Post 1 Link 1 of this thread.

dezborders said:
Seriously dude!
See Page 1 Post 1 Link 1 of this thread.
Click to expand...
Click to collapse
Lool... I have seen, but the idea was that the last update is not necessary the more stable... But ok, i'll do whith...
Thank you very much.
Sorry for my english, it's not my first speech :good:

17.0240. 2004.9 Out

Was checking system updates and found an update.

HermesHidayat said:
Was checking system updates and found an update.
Click to expand...
Click to collapse
Yup, was posted today on telegram group...
(WW)
FOTA (incremental update from 2004.60) ;
Rename to UL-ASUS_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
https://fota2.asus.com/delta_packag...2004.60-17.0240.2004.9-06061254-fota-user.zip
Full rom zip ;
https://dlcdnets.asus.com/pub/ASUS/...S_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
Raw rom ;
https://drive.google.com/file/d/1T0P8CDJLjPypRAS2HDpdUn8Z-M5tfzKc/view?usp=drivesdk
Stock boot img ;
stock2004.9
Root boot img ;
root2004.9
Place rom in root of storage and reboot. Once detected click to update. Reboot again to finish.
For those with root already and wishing to keep root, simply put the rom in root of storage, reboot and click to update when prompted. BUT, DON'T reboot yet when it finishes updating. Click 'later', go to magisk manager and choose 'install magisk'. When given the options for installing, select 'after OTA' (or words like that). Once magisk is installed again, select reboot. Root will be maintained. Saving the hassle of flashing the root img via fastboot.
-----------------------------------------
For those of you who are not yet rooted but would like to be using the boot img above, see below for guidance. NOTE: if something goes wrong, I am not responsible in any way!! Also, by unlocking bootloader (which is required for root), you will void your warranty.
Also note: you must update to latest 2004.9 rom from above links before starting this process. Should you wish to do this process another time with another update, you MUST ALWAYS match the root boot img for the same rom version you are using.
1. First you need to unlock the bootloader. Download and install the apk from link, then follow instructions. NOTE: doing this wipe the device. Do not power off the device or stop the process once started. I think the device will reboot a couple of times during the process, but ican't remember sorry... Just leave it to do its thing and once finished, proceed to step 2.
Get the bootloader unlock tool, which says in the description that it's compatible with android 10, from here. You'll find it under tools/utilities.
2. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC/laptop to C drive
3. Download the root2004.9 boot img from above and move/save it to (C:\Program Files (x86)\Minimal ADB and Fastboot folder)
4. Switch the phone into fastboot mode (from device being in off/powered down, hold volume up then press and hold power button). Fastboot is the first screen you see with a scrollable menu giving some other options, don't select any options... just stay in that mode. Connect the phone to pc/laptop using the SIDE port of the phone. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
5. (optional, but recommended) Once your phone is connected in fastboot mode and you have your cmd window open, type 'fastboot devices' in the cmd window. If your device is recognised then a key/serial will be displayed. Providing this is shown, proceed to step 6.
6. Next you are going to flash the root boot img (which, if you followed the instructions, should be in the Minimal ADB folder). In the cmd window type 'fastboot flash boot magisk_patched2004.9.img'. Once completed without errors, your device will now have a rooted boot img flashed. Yey!!
7. Now you can go ahead and unplug your device and boot it up. I did this months ago when I first got the phone, so you'll have to forgive me.... I can't remember if magisk manager is installed during the above process or if you have to install it manually after. If, when you have booted to system, there is no 'magisk manager' in your app drawer, you'll need to install yourself from here scroll about half way down the page and you'll see the downloads section. Go for the latest stable (currently 7.5.1).
8. Download a root checker app from playstore to verify you have root and you're done. If you need to resort back to original boot img, download it from above and follow the same process, but instead type 'fastboot flash boot boot2004.9.img'.

reg66 said:
Yup, was posted today on telegram group...
(WW)
FOTA (incremental update from 2004.60) ;
Rename to UL-ASUS_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
https://fota2.asus.com/delta_packag...2004.60-17.0240.2004.9-06061254-fota-user.zip
Full rom zip ;
https://dlcdnets.asus.com/pub/ASUS/...S_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
Stock boot img ;
stock2004.9
Root boot img ;
root2004.9
Place rom in root of storage and reboot. Once detected click to update. Reboot again to finish.
For those with root already and wishing to keep root, simply put the rom in root of storage, reboot and click to update when prompted. BUT, DON'T reboot yet when it finishes updating. Click 'later', go to magisk manager and choose 'install magisk'. When given the options for installing, select 'after OTA' (or words like that). Once magisk is installed again, select reboot. Root will be maintained. Saving the hassle of flashing the root img via fastboot.
Click to expand...
Click to collapse
bro,im not saying youre disturbing or whatsoever,you should make a detailed thread.unlike me im kinda dumb,i dont understand this Root boot img and so on. and making your own thread will allow more people will see your thread as i doubt many people will come to this thread to read...

Can anyone check to confirm whether heating is still on an issue on the new version?

HermesHidayat said:
bro,im not saying youre disturbing or whatsoever,you should make a detailed thread.unlike me im kinda dumb,i dont understand this Root boot img and so on. and making your own thread will allow more people will see your thread as i doubt many people will come to this thread to read...
Click to expand...
Click to collapse
Nah, should be fine here. People will still see the update in your title and click to view content. And for those that want root who are not already rooted I'll add some instructions in a while or tomorrow about how to use the boot img's (on my phone right now, it's easier if I do it on pc). Links and details are only the second post on the page so people will still see the info they need. So yeah, if it's OK with you I'll just leave the content here rather than starting another thread with the same title
---------- Post added at 03:36 AM ---------- Previous post was at 03:35 AM ----------
TikiThePug said:
Can anyone check to confirm whether heating is still on an issue on the new version?
Click to expand...
Click to collapse
I'd like to shed some light on this for you but I'm not a heavy gamer (I assume that's when the device gets hot mainly) and have never had any heating issues with any of the builds

TikiThePug said:
Can anyone check to confirm whether heating is still on an issue on the new version?
Click to expand...
Click to collapse
i dont play games anymore on my phone but the only time it hit 74 degrees was when i left my phone in my car under the sun...
reg66 said:
Nah, should be fine here. People will still see the update in your title and click to view content. And for those that want root who are not already rooted I'll add some instructions in a while or tomorrow about how to use the boot img's (on my phone right now, it's easier if I do it on pc). Links and details are only the second post on the page so people will still see the info they need. So yeah, if it's OK with you I'll just leave the content here rather than starting another thread with the same title
Click to expand...
Click to collapse
of course its fine.i was worried people wouldnt be able to see it.

Issue with Android 10 update on tencent with WW fingerprint
@reg66 tried moving post 2 ROM into root of storage .bit the update is still failing . New update is detected and after reboot, while it initialising install it's failing at the very start
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !

VeeJay1 said:
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !
Click to expand...
Click to collapse
Hmm, you should be able to update from latest A9 (1910.64) to A10. I'm guessing that the updater app only downloads the small incremental updates. These will fail unless you update 1 by 1, going up one version each time.
If you wanna jump straight to latest update (currently this one) download the FULL rom zip from post 2 of this thread. Put that in root of storage and reboot. Should hopefully not fail now and you'll be on latest.

Issue with Android 10 update on tencent with WW fingerprint
@reg66 tried moving post 2 ROM into root of storage, but the update is still failing . New update is detected and after reboot, while it's initialising install it's failing at the very start
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !

Yes, moved to 2004.9
Did the incremental update and now my tencent rog2 on ww2004.9. thanks for the pointers.They really helped.

reg66 said:
I'd like to shed some light on this for you but I'm not a heavy gamer (I assume that's when the device gets hot mainly) and have never had any heating issues with any of the builds
Click to expand...
Click to collapse
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.

well, video recording while connected to usb mic still doesn't work with the asus camera app

VeeJay1 said:
Did the incremental update and now my tencent rog2 on ww2004.9. thanks for the pointers.They really helped.
Click to expand...
Click to collapse
So the incremental worked direct from 1910.64 to latest? Or you had to go through each incremental?
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
TikiThePug said:
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.
Click to expand...
Click to collapse
Man that sucks. I've had zero heating issues even with leaving X mode on permanently @120Hz

Had to do this with each incremental update!
reg66 said:
So the incremental worked direct from 1910.64 to latest? Or you had to go through each incremental?
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Man that sucks. I've had zero heating issues even with leaving X mode on permanently @120Hz
Click to expand...
Click to collapse

TikiThePug said:
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.
Click to expand...
Click to collapse
I've also suffered from battery and performance issues in A10. A9 was just fabulous, A10 was a step back.
I'm also a heavy gamer and just updated so I'll be sure to let you know what's going on.
P.S I did manage to improve performance and some battery life by installing the only real custom kernel we have, but which is a great one - kirisakura + Naptime with doze on Google play services.

VeeJay1 said:
Had to do this with each incremental update!
Click to expand...
Click to collapse
Ahh ok, bummer!! At least it's sorted now

Hi all, I have problem with the last update, always that's stop at 9% with message error update

dracoolia said:
Hi all, I have problem with the last update, always that's stop at 9% with message error update
Click to expand...
Click to collapse
I had the same problem with the incremental update. Just use the full ROM linked in the op.

Thanks for the Rooted Image.

Hi just chasing the raw rom if anyone has it please!

[UNOFFICIAL][MAGISK MODULE] Active Edge Mod for Edge Sense Plus - continuation for patch levels 2021-01-05 and later

EDIT: It's too annoying to maintain and edit 6 separate threads. The installer works across all devices, so please visit this post for the latest version: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/
Thanks!

NOTE: Download link in the OP will install mod for the current patch level down to January 2021. It will detect your current patch level and install the correct file. For earlier system builds from 2020 and prior, please use the official discontinued module on the Magisk Manager repo. I did not clone the entire Active Edge Mod repository; my unofficial repository only hosts January 2021 and later builds.
Changes:
I know, I know... I said I was done with releasing my Unofficial Active Edge Mod installer, yet here's another month's update. I might keep doing it for those that update immediately and want it a bit sooner, so long as it's fortunate enough to happen on a day when I'm able to do it relatively quickly. Since I'm building these anyway and sending them over to the dev, for now, to upload to the official Magisk repo, for now I don't mind also updating it here a bit sooner. Anyway, more on this below and some of the headache involved moving forward...
04-05-2021: Soooo... the script I wrote to churn these out as quickly as possible as Google releases the updates, relied on system image dumps on GitRip... unfortunately the domain was seized by the FBI (lol) and so it looks like the old dumper is no longer updating his Android dumps repo on GitRip. Fortunately, mikalovtch pointed me over to a new source that hosts such system dumps, and I was able to get these done relatively quickly afterwards. OP is updated with the 04-05-2021 installer now!
03-02-2021: Meant to post an update a week or two ago. Noticed the magisk module on the official Magisk repo now says [RE-CONTINUED], so there really isn't much need for me to continue updating this anymore! As a final gift, I ran my batch builder script and built the modded apk's for all variants for the 2021-03-05 patch level, and download link for the module installer is in the OP.
02-02-2021: February 2021 mod is now uploaded. Updated installer is in the link in the OP.
02-01-2021: Modified and uploaded modded SystemUIGoogle.apk files for 3 / 3 XL / 3a / 3a XL to GitHub repository. Updated Magisk installer slightly to accommodate this, and removed a few unnecessary lines. Won't make any difference if you already installed the first release.

Works! Thanks for keeping this alive!
(I'm on Jan. 2021)

newkydawg said:
Works! Thanks for keeping this alive!
(I'm on Jan. 2021)
Click to expand...
Click to collapse
Thanks for the feedback! Like I said, I don't own these devices so it's good to know that it's working properly.
Btw, fyi the current installer will install the correct mod for either patch level (Jan or Feb). I'll update one of the posts to reflect this. Like the old official installer, it will detect your current patch level and install the correct needed file. The major differences between this and the official mod installer (in terms of the installation process) is that I pulled out support for some of the devices (older Pixels and HTC), and it won't install for anything before 01-2021. I mean, I guess I could clone the official mod's files repo, which would also allow installs for older patch levels, but I didn't see the point seeing as how the official installer will still work fine for them as well as those other devices (afaik - don't think they've had system updates in a while).

Just tried your updated script for the March update but it keeps failing. I noticed on the Pixel 3 forum that there was a glitch that you addressed but I just tried again and it still fails. I've attached a screenshot.

newkydawg said:
Just tried your updated script for the March update but it keeps failing. I noticed on the Pixel 3 forum that there was a glitch that you addressed but I just tried again and it still fails. I've attached a screenshot.
Click to expand...
Click to collapse
Hmm, somehow the MD5 filename had the .apk stripped off before getting pushed to github, so the installer couldn't find the MD5 to compare with. Updated the github repo with the proper name; should flash now! No need to redownload, just try flashing again.

Yay! I have my squeeze for flashlight back! And just like you said "No need to redownload, just try flashing again." Thanks so much!

hello, I am getting a similar error as newkydawg with no remote md5.
I'm running the May security patch on pixel 2 xl.

raisins said:
hello, I am getting a similar error as newkydawg with no remote md5.
I'm running the May security patch on pixel 2 xl.
Click to expand...
Click to collapse
Unfortunately the last official security update for Pixel 2 XL was from December 2020. Also my unofficial mod only started supporting firmwares beginning in January 2021.
Either you're on an older (May 2020, not 2021) firmware than the latest, in which case just use the official module in the Magisk repo. Or if you're indeed on May 2021 security patch, I can only assume you're on a custom ROM which unfortunately isn't supported.

i5lee8bit said:
Unfortunately the last official security update for Pixel 2 XL was from December 2020. Also my unofficial mod only started supporting firmwares beginning in January 2021.
Either you're on an older (May 2020, not 2021) firmware than the latest, in which case just use the official module in the Magisk repo. Or if you're indeed on May 2021 security patch, I can only assume you're on a custom ROM which unfortunately isn't supported.
Click to expand...
Click to collapse
Oh yeah - i am on a Pixel Experience custom ROM. Dang I really liked the long squeeze.. oh well. Thanks for the info

Posting this here because I can't find a thread for the recontinued module. There hasn't been an update to that module for the June '21 firmware. Does that mean there were no changes to SystemUI and we can use the previous module?

CSX321 said:
Posting this here because I can't find a thread for the recontinued module. There hasn't been an update to that module for the June '21 firmware. Does that mean there were no changes to SystemUI and we can use the previous module?
Click to expand...
Click to collapse
There were changes to the SystemUI so I wouldn't use the previous module.

CSX321 said:
Posting this here because I can't find a thread for the recontinued module. There hasn't been an update to that module for the June '21 firmware. Does that mean there were no changes to SystemUI and we can use the previous module?
Click to expand...
Click to collapse
Looks like Mikhail hasn't updated the official repository yet. I'll shoot him a reminder. I sent the files a few days ago. He must be busy lately.
Meanwhile, here's another unofficial update (even though the official version will have identical modded files). Gonna only edit the Pixel 4 XL thread from now on. It's too much of a PITA to edit every single post for each variant. The installer is the same for all devices anyway. Here's a link to the thread, and download link will be there too: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/

Thanks for updating!

August active edge update soft bricked my Pixel 3.
I can dirty flash OTA to get back but obviously root is gone and if I try to install magisk again the same thing happens. How can I remove the bad update without formatting the phone? The previous method only worked on android 10.
I do not recommend anyone flash the recent august update.

Rumsfield said:
August active edge update soft bricked my Pixel 3.
I can dirty flash OTA to get back but obviously root is gone and if I try to install magisk again the same thing happens. How can I remove the bad update without formatting the phone? The previous method only worked on android 10.
I do not recommend anyone flash the recent august update.
Click to expand...
Click to collapse
Yep, the same thing happened to me. I had to manually flash the stock boot image to both slots and reboot. Then use the long-press in power menu Restart option to reboot to safe mode, but as soon as it starts to reboot, hold the volume down button so that it goes to the bootloader. Then you can flash the Magisk patched image, and reboot, and when it reboots this time it will be rooted but still be in safe mode, so the bad Active Edge module will be disabled. It was a pain, but at least I got back to a working state without a factory reset.
Edit...I had to flash stock boot to both slots because I had corrupted the previously inactive one in my attempts to recover from this situation. If you haven't messed with the inactive slot, you shouldn't need to flash stock to it.

Soft bricked here too. Did exactly what @CSX321 did to get back to normal.

CSX321 said:
Yep, the same thing happened to me. I had to manually flash the stock boot image to both slots and reboot. Then use the long-press in power menu Restart option to reboot to safe mode, but as soon as it starts to reboot, hold the volume down button so that it goes to the bootloader. Then you can flash the Magisk patched image, and reboot, and when it reboots this time it will be rooted but still be in safe mode, so the bad Active Edge module will be disabled. It was a pain, but at least I got back to a working state without a factory reset.
Edit...I had to flash stock boot to both slots because I had corrupted the previously inactive one in my attempts to recover from this situation. If you haven't messed with the inactive slot, you shouldn't need to flash stock to it.
Click to expand...
Click to collapse
What is the process for flashing to a slot? Is this done with adb?

Rumsfield said:
What is the process for flashing to a slot? Is this done with adb?
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
or the same with boot_b
You can use:
fastboot getvar current-slot
to find which slot to flash.

CSX321 said:
fastboot flash boot_a boot.img
or the same with boot_b
You can use:
fastboot getvar current-slot
to find which slot to flash.
Click to expand...
Click to collapse
Thanks I'll give it a shot.

Question RE : SD1A.210817.037

My device is running .036 and about a week ago the system update said there was a download. I am assuming is .037 because that is the only thing it could be...
I try to download it and it fails and it says to try again and it fails, repeat ad nauseum...
Is this ( .037 ) supposed to download ?
Ah snap, is my phone's update software broken ?
I assume this android bug will only go away with a factory reset...
Hmm...
Because fixes are cumulative, should I just wait a little bit and download December's update. I am assuming there will be a software update in December besides the security stuff.
Vote now.
Factory Reset -or- wait

You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip

miravision said:
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
Click to expand...
Click to collapse
Ug, ya I know, too many questions... lets try again...
Question: Is the .037 supposed to download ?

Yes

I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.

miravision said:
Yes
Click to expand...
Click to collapse
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?

NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Cool ! I like that idea. Will the newer update push in front of the glitched update ?

old_fart said:
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
Click to expand...
Click to collapse
The OTA will not wipe, no flags needed. Only the full image will wipe, unless you use the flag.
I doubt your update system is broke, I suspect you just got a bad download. Next download will be fine I think. So sideload or wait for December.

NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Monthly updates usually occur on the 1st Monday of each month, which would be the 6th for December. Just curious, where did you hear this rumor that they were deviating from this process?

old_fart said:
My device is running .036 and about a week ago the system update said there was a download. I am assuming is
Click to expand...
Click to collapse
To be clear, are you rooted, or at least running a custom kernel? If yes to either one, you shouldn't attempt to take any automatic downloads. At worst they just won't update, such as you found out, or at worst it could break something, although still not catastrophic except maybe losing some data.
So, if you are rooted or at least using a custom kernel, you should turn off automatic updates in the Developer Options. And if you're not rooted and not using a custom kernel, then go with what everyone else said. Now if December's OTA failed to update your phone correctly and you're not rooted or using a custom kernel, then I would consider first just flashing the full factory image (whatever the most up to date at the time will be) while removing the -w (wipe) command from the flashall.bat.
Also, to complicate this reply even further, whether you're rooted or not, have you /or disabled verity and verification? If so, when you use the flashall.bat, you're going to want to put the disable verity and verification commands in place of the -w wipe command - otherwise you would *have* to wipe any time you go from either enabled to disabled, or from disabled to enabled.
Sorry for any confusion my reply may cause.

Do I need to root my phone before manually updating using the OTA file?

speedyx2000 said:
Do I need to root my phone before manually updating using the OTA file?
Click to expand...
Click to collapse
No

Lughnasadh said:
No
Click to expand...
Click to collapse
Thank you for your quick answer!

I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers

virtyx said:
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
Click to expand...
Click to collapse
It was America only apparently. Everyone else will get it in December as normal

From Orange France is 036, from Google store is 037

Fingerprint improvement patch was U.S. and Japan only, if you really want it sideload it, it works perfectly fine