david

That's my guess (unless you have something else installed that also modifies /system). Android won't allow an OTA if /system has been changed, because it is an incremental update and it can't be sure of the result unless the /system that the incremental update was created from is identical to the one it is applying the update to.

Yes, I believe so. Here are some options to use adaway in a systemless way, or using an equivalent ad blocking module in Magisk: https://forum.xda-developers.com/mi-a1/help/systemless-adaway-magisk-t3733839

@rtuz2th, you could try capturing the download URL (https://www.thecustomdroid.com/how-to-capture-ota-update-url-android/) and then download the OTA with a web browser and install it from the SD card. I have no idea if that will get around the "reason 20" error, but it is something to try. I'm guessing you'd want to follow the same steps with regard to Magisk Manager before and after, and not reboot until Magisk is re-enabled.

I understand completely. I had the same experience. Very frustrating. I don't think there is a truly *good* app anywhere to be found. Did you change anything in /system?

I updated mine to 80.0.3987.132, and I still see "Add to dictionary" and "Delete" in the list box.

The best way I found is to do a batch restore (of only regular apps, not system apps) and then after it fails on one, start it again, but filter out the ones it has already restored (there is an option to filter out those that are already installed), in addition to the most recent app it failed on. For the apps it fails on, I add those to a "label" and then check "inverse" to exclude those in that label. That greatly reduces the amount of time each pass takes. But yes, if they would have simply given an option to skip the app it is currently restoring, and give you a list of those at

Mine shows the same two items in Chrome and Gmail. For some reason mine are not invisible in Chrome. I have Chrome version: 80.0.3987.99 I was wondering the same thing.

Still broken on mine.

The location of the backup can be found in the link provided in the subnote of my post here: https://community.fxtec.com/topic/2537-magisk-install-step-by-step-root/?do=findComment&comment=46413 When you tell Magisk Manager to patch a boot image, it makes a backup copy of it for later use. The date at the end of that is what we are referring to as the version. You can find the boot image for 20200106 online in the link provided by @Ilrilan here: https://community.fxtec.com/topic/2537-magisk-install-step-by-step-root/?do=findComment&comment=39635

One thing to add... For those who are going back to older images, I *believe*, in theory, you could run into problems with not clearing the /data partition. If some system apps have changed their data structures between the various versions, then going back could lead to an incompatibility. I don't know if we can say that jumping forward through all the OTAs to where you were before you flashed the factory images will get you back in sync, because it might be possible for those system apps to get into a weird state when provided with incompatible data structures in the /data partition f

That means it didn't create the patched boot image originally, or you possibly uninstalled it temporarily (without having an new OTA to point it at), and that got it confused. And if you have an SD card and have it set to be used as combined storage with the internal storage, Magisk doesn't work properly (have to move magisk manager back to the internal storage). I thought it wouldn't work at all, but maybe it could work, but be confused and fail with this procedure. My guess is that you have 2 main options and 1 more time consuming option: 1) You can get the boot image file for

Glad to hear it. Yeah, some people have reported that if you install Magisk Manager on a phone with the SD card set to be shared with internal storage, it will put the app on the SD card and it won't work. Others have reported some issues with using USB 3 cables/ports vs USB 2 cables/ports (with one type working for some and another type working for others). And others have found issues depending on the fastboot version used. Seems like you hit all 3 of those (or just reduced your risks by changing all 3 out at the same time). So did you get it all working in the past 7 hours? :-)

Yeah, you would be stuck, unless someone has that image. A bunch of us updated with the 20200304 update, so we can't easily get the 20200306 image. You will know right away if the process of temporarily disabling root and getting the Ota and re-enabling root works, on the first Ota. Then it should be a matter of doing that for each one.

Yes, I heard the same. And hospital personnel have to work even if sick. Horrible decisions for doctors to have to make, not just once, but continuously.

Stock back to 2019 factory images? Did you go through all the OTA's again? Good that you got it working.

You can try holding in the power for an extended time to see if it will get you out of some odd state.

See this: https://community.fxtec.com/topic/2537-magisk-install-step-by-step-root/?do=findComment&comment=46379 And this: https://community.fxtec.com/topic/2537-magisk-install-step-by-step-root/?do=findComment&comment=46403

I am not aware of any full builds (other than that factory image), just partial updates.

Booo!!!! (not you, the issue)

I had mostly old apps too, but I was forced to upgrade WhatsApp on the old phone and I did upgrade Viber to try to get notifications to work (which they did not). I don't know why some of the other apps were of the newer variety. They might have been more recently installed. When you have hundreds of apps and the restore program hangs when it hits one, it is a pain in the @ss to do a batch restore. It took me hours to restore my apps to the Pro1 from my old phone. Of course, part of that was that I didn't get smart until near the end of the process and started filtering out restoring the

Short answer is that it is a new modular way to package and deploy apps. You might hear it referred to as app bundles too. Longer answer: https://medium.com/google-developer-experts/exploring-the-android-app-bundle-ca16846fa3d7 For whatever reason, Titanium Backup doesn't seem to be actively supported, at least not in a meaningful way, or else they would have added support for this new format quite a while ago. You might be able to re-install the app from the Play Store and then restore the data from Titanium Backup, even if Titanium Backup can't restore the app itself.

So you think the one currently going through certification is a full update instead of incremental?

^^^This. And stock android Q + Magisk. Some of us will just have to hope we reach our expiration date before the rooted Pro1s we are holding in our crippled, old hands do.

In reading the comments from that ticket, I like the idea of limiting (non-banking apps) so that they can tell if they (the apps) have been modified, not that something else in the system has been modified. That seems like a good compromise for all involved. Without that, and as aggressive as apps are getting about detecting system changes, AOSP and LOS could be hit hard by this. Make the calls to the apis that detect system changes be certified and only allow banking/money related apps to be certified. Let apps like snapchat and Netflix check to see if their apps have been modified, b

Boooo!!!! I'll refrain from including a list of expletives.