Same
Before. It happens the instant I extract the file from the image archive. I couldn't even extract it to a cloud drive.
Weird. I have all my phone software stuff in a Phone folder that I have added to Defender exceptions. In Windows 10, it's Settings > Update and Security > Windows Security > Virus and threat protection > Virus and threat protection settings > Exclusions
forum.xda-developers.com
You have to patch init_boot on the Pixel 7, so I wonder if that applies to the beta as well?i would hold off for the moment and monitor....there are reports of issues patching the boot image
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
I don't believe the Pixel 6 series has an init_boot.img. But patching the Pixel 7 boot image and flashing it on the Pixel 6 works to root the Pixel 6 when on QPR2 Beta 1.
That's odd. Magisk patches ramdisk, which on the Pixel 7 was moved into init_boot.img. Boot.img just contains the kernel. So, unless Magisk adds ramdisk back in somehow...that shouldn't work
Magisk can add a generic ramdisk to a boot image lacking one, e.g. Pixel 7.That's odd. Magisk patches ramdisk, which on the Pixel 7 was moved into init_boot.img. Boot.img just contains the kernel. So, unless Magisk adds ramdisk back in somehow...that shouldn't work
Well now that makes sense.Magisk can add a generic ramdisk to a boot image lacking one, e.g. Pixel 7.
It depends. The only absolute "right" way is to start with a clean copy of the boot image from whatever build you updated to, patch that, and flash it.
Good to know - I've always used the original C to C cable without issues. Guess it depends on the pc (my is fairly recent)
I had the same exact problem, on delta and using PixelFlasher. After some trial and error I figured out how to get it back to where it was. It's actually really simple. Just uninstall any instance of the Magisk app you have installed, including any hidden magisk app you may have forgotten to unhide (uninstall them just like any other app by long pressing on the app and dragging it to the top where it says uninstall). Once you have all instances of the Magisk app uninstalled, just use PixelFlasher like you normally do. Download the March update, process and patch it, flash it and let PixelFlasher do it's thing. Thats it, you're back to where you were before you lost root except now you're on the March release. All your modules will still be there and enabled (just remember to keep data when flashing). Let me know how it goes.For me update on latest march update is not going to sucess with Root unfortunately
Till now I was using Magisk Delta and used Pixelflasher - worked everytime like a charm.
Now after march update I lost root and am not able to regain it. I patched boot image with Delta Magisk but when booting (live or flash), root is not present.
When selecting Canary Build from Magisk, Pixelflasher is telling
WARNING! Problematic Magisk Manager Version: 981ccabb:25210 is installed. Advised not to use this version.
Anyone facing similar issues and is able to help to regain Root?
Edit:
There seems to be an issue between latest Magisk and March update...
I had to downgrade from 25210 to 25206 which works now flawlessly as usual.
It really does seem like there are more issues than normal this month. The changelog is posted around here somewhere but I can't remember where I seen it. I highly recommend using PixelFlasher to update your device, it's a very well put together program that Badabing2003 created. I can't say enough good things about it, really well done. It literally takes me 224 seconds every month to update, except this month do to an error on my part. Give it a go, if you have any questions or run into any issues PM me and I'll help you out.
Excellent, I will check it out. I remember seeing a comment about the latest version (34.0.x?) having a bug, and to use 33.x.x instead - is this still the case? Many thanks!
There's no issues with PixelFlasher, it's Platform Tools that is having issues. I guess the latest version 34.0.0 has issues so they're telling everyone to revert back to 33.0.3 If you have 34.0.0 you'll have to find a place to download 33.0.3 from. Once you get that straightened out then you can use PixelFlasher if you want. Just don't use the latest Platform Tools or you'll end up in a bootloop (at least that's what I hear).
Are you using the correct factory image for your device? It should have "raven" in the file name.
Yeah, I definitely know what I'm doing. Installing 33.0.3 has completely resolved the problem. Thank you for help, you're the MVP.
This is the first time I've ever run into issues updating the monthly on my P6P, Part my fault because I forgot to unhide Magisk (although I didn't think this would cause issues as it hasn't in the past) but somehow I lost root. Not all that big of a deal as I uninstalled Magisk and patched the new update and that fixed the issue but for some strange unknown reason I'm now showing Magisk Delta (which is what I installed), but I'm also showing the icon for the hidden Magisk app which I uninstalled prior to re-rooting. I'm guessing that one of the files must have been left behind. Strangely, everything is working perfectly, Passes root check and integrity, all my modules are there and working as well. Seeing everything is working as it should and I'm not having any issues I'm just going to leave it as is. I think if I try to uninstall the old Magisk app it might take a file with it that shouldn't be uninstalled and I don't feel like doing a full wipe if I don't need to. Anyone else have an issue similar to this please let me know.
WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!
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 <image-device-buildnumber.zip>fastboot boot <drag and drop master root.img here>MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
