I use Systemless Hosts for AdAway as well, and have never needed to disable it when updating. The module does not change anything in /system; instead, it "hijacks" where the kernel looks for the hosts file and redirects it to the custom hosts file managed by the ad blocker.
What do you mean "patch the update before"? These instructions are correct; Android system downloads and unpacks the OTA, then installs it to the inactive slot; when the system reboots, it switches to the updated slot.
Thank you for the reply. Now I understand what you mean, but something went wrong, in the last step, which is flashing of magisk, I have selected the canary version which was saved, and then, after flashing the phone stuck for while with Google logo. When I rebooted i see it shows that the device is corrupted.
There have been many cases where users have gotten the corruption problem. Sometimes flashing an old boot.img (for example, from May) will fix it. If trying to flash the full firmware zip (with -w removed so it doesn't wipe your phone) doesn't help, you can always try Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
Thanks for the suggestion. I'm going to start flashing from Flash Tool and If I select June build, disabled Lock, then Flash
Make sure you are following the instructions in the guide. Do not try to substitute your own ideas. The only way Magisk can be "flashed" is via a custom recovery such as TWRP, which to my knowledge has not been ported to Android 12 or the Pixel 6.
Confirmed fixed with today's release of Stable 25.1 and Canary 25101. No problems updating via direct install.Looks like the issue may have been fixed with these commits...
Don't skip backup even if original does not exist · topjohnwu/[email protected]
Close #5945, fix #5944github.com
Don't backup ramdisk created by Magisk · topjohnwu/[email protected]
Fix topjohnwu#5938, fix topjohnwu#5944
v2.3.1
Latest
kdrag0n released this 3 hours ago
· 3 commits to master since this release
v2.3.1
f79e5cc
Changes
Highlights
- Fixed fingerprint on OxygenOS/ColorOS 12 (@osm0sis)
- Support for Magisk 24+ module updates (@benjibobs)
- Restored support for Android 7
Other changes
This version only supports Zygisk (Magisk 24 and newer).
- Spoofed OnePlus OEM unlock status for futureproofing (@osm0sis)
- Minor code improvements
Donate
If you found this helpful, please consider supporting development with a recurring donation for rewards such as early access to updates, exclusive behind-the-scenes development news, and priority support. Alternatively, you can also buy me a coffee. All support is appreciated
Contributors
osm0sis and benjibobs
Assets
3
19 people reacted
- safetynet-fix-v2.3.1.zip
93 KB3 hours ago- Source code (zip)
3 hours ago- Source code (tar.gz)
3 hours ago
12
4
10
0Join discussion
github.com
I would also like to know if this is a problem that others are having, otherwise rooting my phone is pointless; the only reason I bother is for V4A.
Do you have any Magisk mods that may need disabling and updating to be compatible with the Junes security patch? You can flash the patched image and then boot into safe mode and then reboot and that will disable all your mods. If you can boot up after this with the patched boot image you likely have a mod that needs updating.
I had usnf, acp, aml, v4a, systemless hosts (although I wasn't using adaway). All were disabled, and I can no longer see any of them through magisk, because it is not installed properly (no root).
When you flashed the patched boot image in fastboot, are you using the latest Platform Tools?
Yes, I just downloaded the latest set before beginning the process today.
Does it work for Android 13 too?Read my post here
Post in thread 'Android 12 (Viper4Android)' https://forum.xda-developers.com/t/android-12-viper4android.4307163/post-87114613
Thank you.
I root my phone so I can back it up in order to restore stuff after sideloads go wrong like they just did. Some data doesn't get backed up otherwise.,
I believe some Wallet functions are limited in the US, such as being able to upload your driver's license. But, for payment, mine seems to work fine.My bad. The articles I have seen the past couple of days stated that Google pay was being replaced by Google wallet every where except the US and I think Singapore. I presumed that the US was not getting wallet. I stand corrected.
Root process is the same for A13 as it is on A12.
adb devicesadb reboot bootloaderfastboot flashing unlockfastboot flash boot <drag and drop master root.img here>adb reboot sideloadadb sideload ota.zipfastboot boot <drag and drop master root.img here>fastboot flash bootloader <drag and drop new bootloader.img here>fastboot flash radio <drag and drop radio.img here>fastboot update --skip-reboot image-codename-buildnumber.zipfastboot boot <drag and drop master root.img here>flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot --slot=all <image-device-buildnumber.zip>fastboot boot <drag and drop master root.img here>Part of it is due to device differences - non A/B devices can't use seamless updates, so re-rooting is only possible by either patching the boot image directly, or by flashing Magisk in a custom recovery.
Notice the date of that post, 16 months ago. Magisk Canary 23017 re-incorporated the ability to install to inactive slots.
