[Guide] Flash Magisk on Android 12

[pershoot]

It's not easy, you basically have to look at the canary channel commits, and they're all named "app-debug"

Magisk 23001

Monitor this and you should be able to keep privy of releases (aside from the app notifying you of such).

History for gradle.properties - topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

 

[pershoot]

Odd issue, Zygisk was showing: No. I had patched before that was enabled. I repatched while it was on, then reflashed, and now showing Yes, as it should.

 

[xstrifey]

Really noob question sorry - first pixel device, I'm used to using Odin on Samsungs.

I have bootloader unlocked

PS C:\adb> fastboot flash boot magisk_patched.img
target reported max download size of 268435456 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.419s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.565s


Anyone know the reason this would be happening?

 

[V0latyle]

Really noob question sorry - first pixel device, I'm used to using Odin on Samsungs.

I have bootloader unlocked

PS C:\adb> fastboot flash boot magisk_patched.img
target reported max download size of 268435456 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.419s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.565s


Anyone know the reason this would be happening?

Did you previously have a custom ROM on the device? It sounds like you should use Android Flash Tool and force flash all partitions.

 

[xstrifey]

Did you previously have a custom ROM on the device? It sounds like you should use Android Flash Tool and force flash all partitions.

thanks for the response.

The phone is 100% stock, running 12.0 (current firmware), only thing I’ve done so far is unlock the boot loader and create the patched boot file.

I’ll reflash the current firmware using the web-ui and force flash all partitions, and report back.

 

[V0latyle]

thanks for the response.

The phone is 100% stock, running 12.0 (current firmware), only thing I’ve done so far is unlock the boot loader and create the patched boot file.

I’ll reflash the current firmware using the web-ui and force flash all partitions, and report back.

Make sure you check "Disable Verity" and "Disable Verification" too.

 

[xstrifey]

Make sure you check "Disable Verity" and "Disable Verification" too.

No success unfortunately

 

[ggkameleon]

Hi ! I have a mistake Yesterday with LSPosed Zygist Riu when flash the last update my Pixel stay only on black screen or power off/restart/shut down. After test to start on safe mod I can't and flash the boot modified backup and data corrupt. Rrrrr. I do a clean install with Android flash tool with disable verity etc.. And root it no mistake.

But this day after install mod again I loose the root after restart !?
How can to root it again correctly please I don't want to make a clean install again.
Thanks

 

[V0latyle]

No success unfortunately

You might have a corrupted device.

One more thing to try though. When in bootloader, use the volume buttons to change to Rescue Mode, then select that. Then, go here: Pixel Repair Tool
Select "Other" for the carrier.

If that doesn't work...your device is probably corrupted.

If you don't mind, explain how you got to the point where you couldn't write to /boot. Did this device work before? What happened between the point where it worked and now?

 

[xstrifey]

You might have a corrupted device.

One more thing to try though. When in bootloader, use the volume buttons to change to Rescue Mode, then select that. Then, go here: Pixel Repair Tool
Select "Other" for the carrier.

If that doesn't work...your device is probably corrupted.

If you don't mind, explain how you got to the point where you couldn't write to /boot. Did this device work before? What happened between the point where it worked and now?

Thanks for the help.

As alternative test I successfully installed graphene OS this morning which went smoothly.

Ill revert back to stock tonight and try the above suggestion. Appreciate the help!

 

[ggkameleon]

Hi ! I loose the root just magisk manager on my pixel after install a mod.
For root again do flash stock boot.img and patch it again with magisk after just flash the modified boot.img or do flash vmbeta disable verity... . Before ? Thanks.

 

[ggkameleon]

Hi ! Please help me I have mistake after flash module and loose Root Magisk. I'm on November update wipe data and root but loose it after install a module !? Don't know which module.
I have flash again Magisk boot modified after flash vmbeta (verity & verification) but boot loop ?
I have flash stock boot img after flash vmbeta (verity & verification) and restart.
But I can't root it ? I don't understand ? Do dirty flash Rom for root it ?

Resolve I can flash Magisk again but without "--slot=all" and all module are uncheck I remove it and install one by one but I think this is the last LSPosed Riru Zygist or Magisk Hide. Don't install MagiskHide I have USN 2.2 and Install stable LSPOSED not the last.

Hi think is MagiskHide make bootloop with last USN & LSPOSED Zygist and not necessary for pass safetynet

 

[V0latyle]

Hi ! Please help me I have mistake after flash module and loose Root Magisk. I'm on November update wipe data and root but loose it after install a module !? Don't know which module.
I have flash again Magisk boot modified after flash vmbeta (verity & verification) but boot loop ?
I have flash stock boot img after flash vmbeta (verity & verification) and restart.
But I can't root it ? I don't understand ? Do dirty flash Rom for root it ?

Resolve I can flash Magisk again but without "--slot=all" and all module are uncheck I remove it and install one by one but I think this is the last LSPosed Riru Zygist or Magisk Hide. Don't install MagiskHide I have USN 2.2 and Install stable LSPOSED not the last.

Hi think is MagiskHide make bootloop with last USN & LSPOSED Zygist and not necessary for pass safetynet

If you have questions about a Magisk module, please post in the Magisk General Support Discussion thread or contact the developer of the module.

 

[ggkameleon]

If you have questions about a Magisk module, please post in the Magisk General Support Discussion thread or contact the developer of the module.

Good evening.
Yes I would do it like that next time.

It's just that I wanted to explain the situation well and especially to know if it was necessary to flash the "vbmeta.img & verity & verification" to return to the original Boot.img and same for Re-Root and flash the "modified Boot.img".
But you answered my question and thank you. it's not necessary ! only for an update.
Have a good day thanks again

 

[V0latyle]

Good evening.
Yes I would do it like that next time.

It's just that I wanted to explain the situation well and especially to know if it was necessary to flash the "vbmeta.img & verity & verification" to return to the original Boot.img and same for Re-Root and flash the "modified Boot.img".
But you answered my question and thank you. it's not necessary ! only for an update.
Have a good day thanks again

Restoring the boot image does not require that you do anything with vbmeta. In fact I would recommend that you don't.

 

[xstrifey]

All resolved now. Updated the platform tools folder and followed same process and worked this time.

Now just to remove replace google apps with micro-g and enjoy!

 

[V0latyle]

Universal SafetyNet Fix 2.2.0 is out on public release for those of you who want to use the new Zygisk.

 

[Krsmqn]

Most recent Canary update is giving me this issue where no matter what I do, when I reboot, it goes right back to the same screen, asking me to download additional stuff. Is anyone else having this issue?

On another note, I am passing safety net with 2.2.0.

 

[Homeboy76]

Most recent Canary update is giving me this issue where no matter what I do, when I reboot, it goes right back to the same screen, asking me to download additional stuff. Is anyone else having this issue?

On another note, I am passing safety net with 2.2.0.

I had this problem before, the Magisk version was 23001 and the App version was 23014.

What I was told to do by @andybones (Staff Member) was to uninstall Magisk App: Open Settings => Apps => See all... => Scroll down to Magisk => Tap it => Tap Uninstall (Magisk will not be uninstalled, only the Magisk 23014 app) => Reboot => install Magisk ( app-debug_23001.apk) => reboot.

Notes:

1. I add the _230xx to Magisk app-debug.apk after I download them. Why? I have a habit of keeping the old and new app-debug.apk in the same folder, the added portion helps me distinguish between the two.
2. Make sure you have Magisk Alpha/Canary.apk 23013 stored on your phone prior to uninstalling Magisk App 23014.
3. Install Magisk 23013.apk after you uninstall the Magisk App.
4. You will not lose root.

After, the reboot when you open Magisk, there will be an Update next to App.

It should be for Magisk 23014, if you want to update to that version: Tap the Update button and tap Direct install.

See what @andybones, wrote Scroll down read posts #370, 379 and 380 and thank him.

 

[Krsmqn]

I had this problem before, the Magisk version was 23001 and the App version was 23014.

What I was told to do by @andybones (Staff Member) was to uninstall Magisk App: Open Settings => Apps => See all... => Scroll down to Magisk => Tap it => Tap Uninstall (Magisk will not be uninstalled, only the Magisk 23014 app) => Reboot => install Magisk ( app-debug_23001.apk) => reboot.

Notes:

1. I add the _230xx to Magisk app-debug.apk after I download them. Why? I have a habit of keeping the old and new app-debug.apk in the same folder, the added portion helps me distinguish between the two.
2. Make sure you have Magisk Alpha/Canary.apk 23013 stored on your phone prior to uninstalling Magisk App 23014.
3. Install Magisk 23013.apk after you uninstall the Magisk App.
4. You will not lose root.

After, the reboot when you open Magisk, there will be an Update next to App.

It should be for Magisk 23014, if you want to update to that version: Tap the Update button and tap Direct install.

See what @andybones, wrote Scroll down read posts #370, 379 and 380 and thank him.

Thank You for the reply, however, after following your instructions, I was left with the same results.