After November's system update, I followed the guide rooted my Pixel 5 and pass SafetyNet. But I can not receive OTA update, here is my original post.
Yesterday, I found a Magisk module - Universal SafetyNet Fix, here is the post. First, I modified the build.prop from Pixel 3 back to default Pixel 5 by MagiskHide Props Config. Then I install Universal SafetyNet Fix 1.1 module. After the restart, "Check SafetyNet" Success.
I checked system update, it's back! I uninstall Magisk (restore image), then start the system update. Before restart, back to Magisk install. But there is no option for "install to inactive slot". I googled what's happened here. So I have to "Direct Install". After restart, as I guess, Magisk and root both fine, but the system update still let me restart to apply. So this time I restart directly without uninstalling Magisk. This time, the system update to December, Magisk still installed but root is not available. I check system update again and update to the latest January patch.
Then followed the regular steps, I patch the latest Stock Boot image, then flashflash the patched image to my phone. Module and root back again.
Related
Hi, I have been using Magisk for last one month. Everything worked fine. All my root apps worked like a charm. Today I tried to install an OTA update. For which I tried to restore stock boot image with Magisk. After Magisk showed, 'restore successful' message, I tried to install the OTA (April), but I couldn't, it kept on showing installation error.
I then tried to reboot my device but it got stuck in bootloop.
Using MiFlash Tool, I flashed back the stock ROM which restored everything including the bootloader but retained my data (user apps and settings, Magisk and other root apps were also retained.) I then updated my stock ROM with the OTA.
Then with ADB, I unlocked the bootloader and flashed the patched boot image file of April.
After booting up first time after the patch, Initially the Magisk and root checker, both showed me root access, but after a reboot, the root access was gone. The root checker now says - Root access is not properly installed on this device.
Magisk homescreen says, Magisk is Latest Version v16.0 but Magisk is not installed. On clicking the install button, it only shows two options - Download Zip only and Patch boot image file.
What should I do to get back my root access?
You have to reflash Magisk manually after every OTA update.
Hi, i'm trying to update my Mi A2 on stock rom but it gives always an installation error. There's any other way to update ? Maybe anually?
Hope someone help
U can install stock rom via fastboot or remove root and update.
For fastboot update u need to download whole stock rom (10.0.9 may update) and install manually but after that you need to flash patched boot images of may update for root access
I had problems too but since the last Magisk update (couple weeks ago), the latest OTA went just fine.
Thus :
1. Try again after updating the Magisk app and module : update Magisk (direct install), reboot, uninstall magisk (restore image), update Android, DO NOT REBOOT, install magisk on the other slot and reboot.
2. Or, uninstall Magisk, reboot and install the update (you will have to reinstall Magisk like you did the first time)
There was an update to magisk and after installing it I lost root. I used magisk manager to download it and install it. I still have magisk manager. Is this common when updating?
When I try to flash the patched boot image, I am just stuck on the google "G" boot screen forever.
choder said:
There was an update to magisk and after installing it I lost root. I used magisk manager to download it and install it. I still have magisk manager. Is this common when updating?
When I try to flash the patched boot image, I am just stuck on the google "G" boot screen forever.
Click to expand...
Click to collapse
Normally, right after updating magisk manager you open it back up and there is an indication that magisk needs to now be updated as well. You click it and choose "direct install".
I have been using Magisk for two years on my device (Moto G5S Plus). Some time ago I did an upgrade of the Magisk Manager app, unfortunately not knowing I should have unhidden it first. From that moment when I started the app, it would immediately stop. Today I finally had the time to dive into the problem. I uninstalled the Magisk app, and from TWRP uninstalled Magisk.
And now I am trying to install Magisk v22.0. I have downloaded and installed the latest Magisk app. When I start it, it shows my device has a boot ramdisk.
I downloaded the stock boot.img to my device, selected Install from the Magisk card, keep options as they are (keep AVB 2.0/dm-verity: off, keep enforced encryption: on).
At the Method step I selected the downloaded boot.img. When I tap "Go" (or whatever it would say with an English UI), nothing happend. I waited several minutes without anything happening.
The UI is responsive. I can go back and do it all over again, with the same result.
Why doesn't the app patch the image?
Is there anything else I can or should do eliminate traces of the old hidden Magisk manager app (besides a full restore, because without Magisk no root, without root no Titanium backup)?
gewe said:
I have been using Magisk for two years on my device (Moto G5S Plus). Some time ago I did an upgrade of the Magisk Manager app, unfortunately not knowing I should have unhidden it first. From that moment when I started the app, it would immediately stop. Today I finally had the time to dive into the problem. I uninstalled the Magisk app, and from TWRP uninstalled Magisk.
And now I am trying to install Magisk v22.0. I have downloaded and installed the latest Magisk app. When I start it, it shows my device has a boot ramdisk.
I downloaded the stock boot.img to my device, selected Install from the Magisk card, keep options as they are (keep AVB 2.0/dm-verity: off, keep enforced encryption: on).
At the Method step I selected the downloaded boot.img. When I tap "Go" (or whatever it would say with an English UI), nothing happend. I waited several minutes without anything happening.
The UI is responsive. I can go back and do it all over again, with the same result.
Why doesn't the app patch the image?
Is there anything else I can or should do eliminate traces of the old hidden Magisk manager app (besides a full restore, because without Magisk no root, without root no Titanium backup)?
Click to expand...
Click to collapse
It doesn't necessary to patch boot image. I had same problem.
Just install magisk 22 with TWRP, reboot...open magisk and install it.
You are ready and rooted.
Thanks for your quick reply. Problem solved!
Dear Team,
When I try to patch the AP file there is an error and it says: "Process error installation failed" , both canary and magisk 24.1 are used in the process
phone info:
android 12, one ui 4.0 (firmware downloaded and flashed 12 hrs ago on my s21 phone)
s21 5g (sm-g991b/ds)
AP filename that iam trying to patch: AP_G991BXXU4BULF_G991BXXU4BULF_SCL23365054_VCL23364085_MCL23373251_SQB47608375_VQB47608374_MQB47608349_REV01_user_low_ship_MULTI_CERT_meta_OS12.tar.md5
see screenshot, please help. thank you.
In my case, when I click the update button while on Canary 23016, Magisk Manager simply evaporates with no error, no log. I'm going to try patching a boot image. I have the January update, Pixel 6 stock.
Kenaz Rune said:
In my case, when I click the update button while on Canary 23016, Magisk Manager simply evaporates with no error, no log. I'm going to try patching a boot image. I have the January update, Pixel 6 stock.
Click to expand...
Click to collapse
So, it turned out to be a bit of a confusing UI "language". I had the 24.1 app installed, but it had an update button next to it. The Magisk library had the typical "install" button rather than "update". I clicked install and was able to proceed normally.
Edit: Spoke too soon. It updated, and I rebooted, but it still showed the Canary. I finally had to delete the app (which was still actually the canary version, but crashed on update) and install the new APK. After reboot.... The proper version is now applied - 24.1.
Whew!