Database Users

[Updata]WW-4.21.40.223(andriod M)

ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V4.21.40.223 for WW SKU only* (andriod M)
Improvement Item:
1)Improve Wi-Fi/Bluetooth stability
2)Update Security patch
3)Improve system stability
4)Support India SOS call (India only)
Full Rom Download Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-4.21.40.223-user.zip

Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks

fredlamour said:
Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks
Click to expand...
Click to collapse
It is, but not if your bootloader is unlocked.

Rodepo said:
It is, but not if your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks.
bootloader unlocked so no way.
I am thinking about jumping into a lineage rom.

VoLte support?? in this new update....

I felt like this was happening today! came in and here it is. Updating right now.
Thanks

any update for this update of asus zenfone 2

optimumgiant said:
any update for this update of asus zenfone 2
Click to expand...
Click to collapse
Hello. This forum is for galaxy 8.07. We don't know about zendroid 2 or whatever you ask.
Just joking. This IS for zenfone 2.
I'm currently using the update. Screen flickering has stopped for the time being.

i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance

crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
it seems you are first. Give it a try and find it out for yourself and let us know!

crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
My way is unroot and uninstall Xposed first, than sideload the whole rom with stock recovery.
I had failed to OTA many times because I modified some system files (forgot to restore them), so now I just reflash rom to save the trouble.

Wifi auto-connect problem seems fixed and the phone has more available ram after "power and boost".
It's worth to update imo.
Battery life seems the same

All sensors working with this version in my brazilian zenfone 2 z00a.

Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.

I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit

audit13 said:
After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
I had unlocked the BL before so i updated and directly tried regaining root and xposed but failed (softbrick at asus loading screen), I confirm that applying the whole ota from sideload sort of relocks the bootloader and you must do it again, now it is booting and rebuilding the dalvik cache.

audit13 said:
I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
In conclusion you did only flashed stock recovery and, from that, you flashed the whole zip in the first post, right?
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

timbernot said:
Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.
Click to expand...
Click to collapse
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642

timbernot said:
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Click to expand...
Click to collapse
can you please share your adblock app with us.
thanks

crownpiyush said:
can you please share your adblock app with us.
thanks
Click to expand...
Click to collapse
its a add-on downloaded and installed from ` tools ` in firefox browser settings :good:
ps, i had trouble using adblockplus add-on from firefox ,when viewing XDA pages ..they turned out blank , XDA i think prevented the use of such adblock , so now i use the less blocking add-on in firefox called `uBlock`
its good enough

Unexpected Android system update, booted into TWRP

Hello,
Today I received a Motorola Android system update. I did not expect this to happen, because my device has an unlocked bootloader and is rooted, and I have TWRP installed. I never received a system update before in the 1,5 years that I have it.
After the update was downloaded, it started installing by verifying the update and then initiated a reboot. The reboot however ended up in TWRP.
What should I do now? Just reboot? Will that cancel the update or break anything?
Is there any way that I can manually complete the installation of the update?

if you are rooted with twrp installed, just copy update file from /cache to your internal storage. Then unroot your device (discard any changes in /system partition via flashing stock system.img), flash stock recovery and apply update from recovery.
I suppose, file you have being downloaded is just security update.
Please pm me, if this file large than 500MB ;

The update file is named Blur_Version.24.61.52.lux_reteu.reteu.en.EU.zip. It is 69,5 MB (69514015 bytes).
This is the first time I receive a system update (I unlocked the bootloader and rooted my phone right at the start). Strange thing is that the contents of the file all have a timestamp of 14 februari 2014 17:43. I can't believe I received a three year old update. The Moto X Play did not even exist three years ago.

I installed the update. It was 24.201.5.en.EU, containing the security patches of october 2016. So your assumption was right. Still strange that this is the first update I received in 1,5 year.

gewe said:
I installed the update. It was 24.201.5.en.EU, containing the security patches of october 2016. So your assumption was right. Still strange that this is the first update I received in 1,5 year.
Click to expand...
Click to collapse
Hello there, could you let me know how you installed the update (step-by-step if possible), I am having the same problem while updating as my moto x play tries to reboot during the install and I get the TWRP interface. Thanks

gamoraw said:
Hello there, could you let me know how you installed the update (step-by-step if possible), I am having the same problem while updating as my moto x play tries to reboot during the install and I get the TWRP interface. Thanks
Click to expand...
Click to collapse
I followed the instructions I found here, with the following changes:
skip flashing bootloader.img and logo.bin (unlocked bootloader);
skip flashing recovery.img (you want to keep TWRP);
skip erase userdata (keep your data).
Some people advise against not erasing useradata, but I never had a problem skipping that step.

Help with new update and Magisk

Hey guys
so initially i rooted partition B using magisk now i got the new update of 75mb. I switched to partition A where it was still on august security patch and i made update of 1gb followed by 75mb update.
So i switched back to partition B and it was unrooted but the update did not install on this partition and told me to make update of 75mb again but i tired to update and it gave me an error but safetynet was not passed ctsproilfe:false
can someone help me? i tried to flash boot.img of stock but same result.

faddys123 said:
Hey guys
so initially i rooted partition B using magisk now i got the new update of 75mb. I switched to partition A where it was still on august security patch and i made update of 1gb followed by 75mb update.
So i switched back to partition B and it was unrooted but the update did not install on this partition and told me to make update of 75mb again but i tired to update and it gave me an error but safetynet was not passed ctsproilfe:false
can someone help me? i tried to flash boot.img of stock but same result.
Click to expand...
Click to collapse
I ended up having to flash the previous Oct (7.10.14) fastboot ROM using MiFlash, rebooted back into the stock ROM and then took the single 1GB OTA update which has the Oct 30 kernel and build number. Booted into TWRP and reflashed Magisk 14.4 and Safetynet passed.
BTW, did you try booting into partition A and check whether the Oct 30 kernel and build OTA (75MB) update was installed? Just thinking this might be the case since you took 2 OTA updates.

cmk7128 said:
I ended up having to flash the previous Oct (7.10.14) fastboot ROM using MiFlash, rebooted back into the stock ROM and then took the single 1GB OTA update which has the Oct 30 kernel and build number. Booted into TWRP and reflashed Magisk 14.4 and Safetynet passed.
BTW, did you try booting into partition A and check whether the Oct 30 kernel and build OTA (75MB) update was installed? Just thinking this might be the case since you took 2 OTA updates.
Click to expand...
Click to collapse
using miflash did you do this without the data being wiped?

faddys123 said:
using miflash did you do this without the data being wiped?
Click to expand...
Click to collapse
I selected the "save user data" option before flashing in MiFlash but somehow all my data was erased when the phone rebooted. Not sure why that happened.

cmk7128 said:
I selected the "save user data" option before flashing in MiFlash but somehow all my data was erased when the phone rebooted. Not sure why that happened.
Click to expand...
Click to collapse
if i just download the stock rom extract boot.img and system.img and flash manually via fastboot it should return to stock? with my app data etc still intact then i can run the update and then flash magisk for root?

faddys123 said:
if i just download the stock rom extract boot.img and system.img and flash manually via fastboot it should return to stock? with my app data etc still intact then i can run the update and then flash magisk for root?
Click to expand...
Click to collapse
Not sure, but worth a try. What about booting from partition A?

cmk7128 said:
Not sure, but worth a try. What about booting from partition A?
Click to expand...
Click to collapse
i booted into A and it is updated with build 30 oct not rooted, but if i root this using new magisk 14.4 for future updates i won't be able to update and partition b is still on update from 14 oct

faddys123 said:
i booted into A and it is updated with build 30 oct not rooted, but if i root this using new magisk 14.4 for future updates i won't be able to update and partition b is still on update from 14 oct
Click to expand...
Click to collapse
If I am not mistaken, you can boot into partition B (which is unrooted) for future OTA updates. Being on 7.10.14 updates would just mean the OTA files will be bigger in size compared to the OTA file for updates from 30 Oct?

Yesterday, I run into problems updating my phone to 30 oct version too. At the end I stuck into bootloops. This is how I solved it:
- boot into fastbootmode
- flash 14 oct Image with MiFlash (option: save user data)
- reboot
- download and install update 30 oct
- reboot into fastbootmode
- fastboot oem unlock
- fastboot boot recovery.img
- flash Magisk 14.4
- reboot Phone

cmk7128 said:
If I am not mistaken, you can boot into partition B (which is unrooted) for future OTA updates. Being on 7.10.14 updates would just mean the OTA files will be bigger in size compared to the OTA file for updates from 30 Oct?
Click to expand...
Click to collapse
well partition B was the one originally rooted, but i could not install the new update, so switched partition to A and did the update but booting into partition b still has build of 14th oct whereas partition A (unrooted) is on 30th oct build. so both partitions are not getting updated together

Foolproof way for OTA-update with Magisk installed

Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?

Tiemichael said:
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Click to expand...
Click to collapse
Hey!
Following the official Magisk procedure works, at least for me.
You just have to be careful to restore backup image before starting the OTA download and installing to second slot (After OTA) before rebooting.
Reading this thread:
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
I found there’s a lot of confusion (I was confused also and made a few mistakes), but my conclusions are:
- That method is to be used just ONCE in order to gain root, and not every month.
- Always try to use your own patched image if you have the opportunity
- You have to use “fastboot BOOT” and not “fastboot FLASH” when first rooting, otherwise you won’t be able to restore boot image and OTA will fail
- Follow official procedure as a cooking recipe
If you don’t want to root using a patched boot image, you can also use latest TWRP (As of now latest is recovery-3.2.1-2-oreo.img)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
And boot to TWRP image in order to install Magisk ZIP (did this yesterday and also worked), but the update via OTA method should be the same.
Best regards.

Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me

Keeping phone to stock and not rooting for only one OTA in more than a month? I think its not worth it!!
I always root my phone and when OTA arrives i just flash twrp version of it and root it again ?

Siebenmik said:
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Click to expand...
Click to collapse
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?

I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..

_mysiak_ said:
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
Click to expand...
Click to collapse
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?

Tiemichael said:
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Click to expand...
Click to collapse
Yes, exactly. I didn't have any issue with OTA installation yet.

Tiemichael said:
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
Click to expand...
Click to collapse
I forgot saying that using restore image in magisk didn't work. Even though I didn't flash the patched boot.

https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where to enable secured startup?

Skeuomorphic said:
Where to enable secured startup?
Click to expand...
Click to collapse
create a pattern from security setting and it will prompt to enable secure startup.. just press yes..

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Finally a different answer, I have secure boot disabled maybe this is the reason ending into bootloop for past 3 montly security updates. Will try this for May update.

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....

Tiemichael said:
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Click to expand...
Click to collapse
Settings->Security & Location->Screen lock->Pattern

This what was working for me just now:
Detailed steps performed 20.4.2018:
Backup Titanium
Backup Magisk Modules
Switch on Secured Booting (e.g. Pin) => not same a normal pin!
Open Magisk
Uninstall Magisk​
Restore Images​
Start OTA update
Downlowd​
Step1​
Step2​
Go Back to Magisk
Install to 2nd slot​
Reboot​
It was working ... very easy!

I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.

I didn't update my phone for a very long time, then I decided to finally go for the latest MIUI on my Mi Max and basically I flashed full new ROM via fastboot & MiPhone.
You can see detailed description here: https://forum.xda-developers.com/showpost.php?p=78050983&postcount=41
I think it should work with other Xiaomi phones too but please correct me if I'm wrong
The only difference is that I had SuperSu before, but maybe with Magisk it's the same to do - also correct me if i'm wrong

quetzalcoatl2435 said:
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
Click to expand...
Click to collapse
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
H.A.L. 9000 said:
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse

freekarol said:
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Click to expand...
Click to collapse
Yeah, but you need a PC for this. If I need access to a PC every time there's an OTA update, might as well download and flash a full ROM. ?
Official Magisk OTA guide works anytime anywhere, no PC needed.

October 2019 Security update for Mi A2 is now available

85 MB

did it update for you?

laviniu_c said:
did it update for you?
Click to expand...
Click to collapse
Yes. No problems. I don't see significant improvements ou bugs.

k congratz! no idea why mine bricked but apparently i'm not alone. https://forum.xda-developers.com/mi-a2/help/october-2019-security-update-mi-a2-t3985917
did you download via wifi or mobile data?

Teksat said:
85 MB
Click to expand...
Click to collapse
Ah! two posts on the same update. Yikes

laviniu_c said:
k congratz! no idea why mine bricked but apparently i'm not alone. https://forum.xda-developers.com/mi-a2/help/october-2019-security-update-mi-a2-t3985917
did you download via wifi or mobile data?
Click to expand...
Click to collapse
WiFi

I had the same problem where my phone bricked, i fixed it by just connecting the device to my laptop using the usb cable.Just restart it once to twice and it worked.
Now when it boots up it says that the update has failed, but when i again update the phone, it shuts down the phone at next login, but when i restart the device again the device was updated to october verson

Teksat said:
WiFi
Click to expand...
Click to collapse
i did mine over mobile data maybe that's why. anyway, will wait a couple of days till they sort out this mess, for now im back to 10.0.14 and i can make sure my backups have everything i need.

Teksat said:
85 MB
Click to expand...
Click to collapse
Could you see if Cam2Api is enabled in the October patch with the stock rom?

Boot images v.10.0.15.0 PDIMIXM
Stock and patched (Magisk 20.0) /boot partition images zipped and attached.
Note that most safe sequence for those with Magisk IMHO is:
0. Become "developer" and disable automatic updates (IMHO THIS IS IMPORTANT, even if you have not rooted phone).
.....
Check for an OTA available, and if yes, immediately pause it (going to Options -> System -> Advanced -> System Updates [not sure for terms because previous is backward-translation from localized menu]).
1. MagiskManager -> UINSTALL -> RESTORE IMAGES
2. Reboot (to have "clean" state) (IMHO THIS IS IMPORTANT, reboot before OTA even if you have not rooted phone);
3. Start OTA download and then installation (going to Options -> System -> Advanced -> System Updates);
reboot;
4. Download from here (or somewhere else or pull yourself via ADB/TWRP to PC) stock /boot partition image, and copy it to /Downloads;
5. Prepare for rooting and receiving next OTAs (IMHO THIS IS IMPORTANT):
<MagiskManager -> Install Magisk -> Select and Patch a File> (i.e. boot image), -
(copy of stock boot image is zipped by MagiskManager in /data partition root for step (1) with next OTA)
6. copy patched boot image from /Downloads back to PC (or download it from here or somewhere)
(MagiskManager makes file "magisk_patched.img", I usually rename it patched_boot..img)
7. "fastboot boot patched_boot.img" - this is done to check that everything has succeeded in previous steps
(IMHO THIS IS much SAFER than "fastboot flash patched_boot.img")
8. If booting succeeded, restore root : MagiskManager -> Install Magisk -> Direct Installation

issue with October update
I tried to update my mobile of google october security patch but after installing and rebooting it says couldn't update your mobile.

Aerobatic said:
Stock and patched (Magisk 20.0) /boot partition images zipped and attached.
Note that most safe sequence for those with Magisk IMHO is:
0. Become "developer" and disable automatic updates (IMHO THIS IS IMPORTANT, even if you have not rooted phone).
.....
Check for an OTA available, and if yes, immediately pause it (going to Options -> System -> Advanced -> System Updates [not sure for terms because previous is backward-translation from localized menu]).
1. MagiskManager -> Delete Magisk -> Restore Partitions
2. Reboot (to have "clean" state) (IMHO THIS IS IMPORTANT, reboot before OTA even if you have not rooted phone);
3. Start OTA download and then installation (going to Options -> System -> Advanced -> System Updates);
reboot;
4. Download from here (or somewhere else or pull yourself via ADB/TWRP to PC) stock /boot partition image, and copy it to /Downloads;
5. Prepare for rooting and receiving next OTAs (IMHO THIS IS IMPORTANT):
<MagiskManager -> Install Magisk -> Select and Patch boot image>
(copy of stock boot image is zipped by MagiskManager in /data partition root for step (1) with next OTA)
6. copy patched boot image from /Downloads back to PC (or download it from here or somewhere)
7. "fastboot boot patched_boot.img" - this is done to check that everything has succeeded in previous steps
(IMHO THIS IS much SAFER than "fastboot flash patched_boot.img")
8. If booting succeeded, restore root : MagiskManager -> Install Magisk -> Direct Installation
Click to expand...
Click to collapse
I have disabled dm-verity and forced encryption (using this). Will this update method work for me? (especially at step 2 after restoring partition - will the phone be able to boot up with original boot image and encryption disabled?)

Just updated
Updated just now via WiFi, at this moment i dont see any improvement, will update if i found one.

Updated via mobile data (lte). No problem updating. First try and booting fine. No other improvement though. Just standard security patch update imo.

Battery life has been greatly improved

TWRP data decryption isn't working with October 2019 update.
The version i got from TWRP official site didn't even boot.

So far so good
Mines encountered the same problem, I think its because the net i was on was very slow so it boot looped and restart with the message couldn't install update. I waited until I reach home yesterday to do the update and to my surprise it did and the device is running great. I notice battery improvements, still testing this one though, AT a Glance in home settings is now working and a few other stuff.

Adaptive brightness is STILL unfixed!
Cannot go lower than 19% when adaptive brightness on.
I have experience the phone slow down when installing app. Is it normal?

jrcbm13 said:
Cannot go lower than 19% when adaptive brightness on.
I have experience the phone slow down when installing app. Is it normal?
Click to expand...
Click to collapse
mine is slowing down when updating apps too and I'm still on September update. I have this phone since January and its performance has been VERY underwhelming. Kinda disappointed

Update phone on battery -> bootloop. Phone in charger till starts up. Message that phone hasn't updated.
Update phone with charger in, in one time updates well...