How To Guide April 2, 2024 AP1A.240405.002 Global - Root Pixel 6 Pro [Raven]

[roirraW "edor" ehT]

Just wanted to say, used Android flash tool (kept verity enabled / kept data / kept bootloader unlocked) rebooted, let phone finish android update, rebooted to fastboot (platform tools 30.0.2) and flashed patched boot.img (slot all) supplied here (big thank you to @Lycidias ) all went smooooth! Easy peasy, light and breazy Rooted Magsik 24.3 stable with new custom kernel. Thanks @Freak07 kirisakura kernel 3.0.0.

I'm surprised (but glad) it works fine with the old Platform Tools (v33.0.1 is the latest, but is also a few months old).

 

[jcp2]

I'm surprised (bug glad) it works fine with the old Platform Tools (v33.0.1 is the latest, but is also a few months old).

Oops. Typo fixed. platform-tools - link for windows (downloads v33.0.2.zip v33.0.2

 

[Lughnasadh]

Oops. Typo fixed. platform-tools - link for windows (downloads v33.0.2.zip v33.0.2

*33.0.1

 

[jcp2]

*33.0.1

I clicked on the windows download link, and it came up to save the file as 33.0.2 Maybe I'm just lucky Try it direct link . hover over the hyperlink and you can see the address.

 

[Lughnasadh]

I clicked on the windows download link, and it came up to save the file as 33.0.2 Maybe I'm just lucky Try it direct link

So it does, but the revision section has it as 33.0.1. Hmm...

 

[Forsh]

I'm signed up to the 12.1 QPR beta and currently on the May release. I still don't have the prompt to update to June. Do I need to opt out of the beta to get it or just wait a bit longer for my turn to update? I'd like to update and go back to stable releases without wiping.

 

[Lughnasadh]

I'm signed up to the 12.1 QPR beta and currently on the May release. I still don't have the prompt to update to June. Do I need to opt out of the beta to get it or just wait a bit longer for my turn to update? I'd like to update and go back to stable releases without wiping.

You don't need to opt out to get it. You should get it in time. With the June Stable QPR3 release, the QPR Beta program for Android 12 has ended. You will automatically be unenrolled in the coming weeks or you can unenroll manually. Thus, once on the June build you will be on the Stable releases.

 

[roirraW "edor" ehT]

I clicked on the windows download link, and it came up to save the file as 33.0.2 Maybe I'm just lucky Try it direct link . hover over the hyperlink and you can see the address.

Interesting, thanks for letting us know. Indeed, they haven't updated their changelog yet.

I now also have Aignes Website-Watcher set correctly to look out for a new version of the zip file, even without an updated changelog.

 

[roirraW "edor" ehT]

Platform Tools is updated to v33.0.2 everyone! No updated changelog yet, and 33.0.1 worked for me (and others) for the June update. And thanks to @jcp2 for the discovery.

• You'll need this if you're going to unlock the bootloader on your Pixel 6 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?
  • You can alternately use the tools from the SDK Manager, but most of us will want to stick to the basic tools-only without the complications of the full development manager.
• For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you "adb reboot-bootloader", to be able to use ADB and Fastboot.

 

[vibrantliker]

wondering if anyone would know why with this update, after rooting, I can't tap to read the notifications in my pull down window? Never happened before.

 

[roirraW "edor" ehT]

wondering if anyone would know why with this update, after rooting, I can't tap to read the notifications in my pull down window? Never happened before.

No idea. Working here. Try disabling all Magisk Modules and see if it still happens.

 

[shiftr182]

wondering if anyone would know why with this update, after rooting, I can't tap to read the notifications in my pull down window? Never happened before.

Same issue here

 

[shiftr182]

Same issue here

It was font magisk module Updated the zip and it works now

 

[Lughnasadh]

Just a PSA for those on Android 13 Beta 2.1:

Starting with Canary 24314, updating to a new Magisk version via direct install results in a bootloop. This behavior has continued with the latest Beta 25/Canary 25001. Patching the boot image, however, allows the phone to boot as expected.

An issue was opened but unfortunately closed as "not planned". So for those on Android 13 Beta 2.1 (and beyond most likely), when updating Magisk you'll want to avoid the direct install method and patch and flash the boot image instead to avoid a bootloop until they decide to resolve this issue.

Patching an already patched img result in a bootloop · Issue #5938 · topjohnwu/Magisk

When patching a stock image and booting it's working fine, When patching an already patched image the device bootloop. Here's what I tested Working: patching a stock file manualy, then booting with...

github.com

 

[roirraW "edor" ehT]

wondering if anyone would know why with this update, after rooting, I can't tap to read the notifications in my pull down window? Never happened before.

See @shiftr182's post for the solution.

It was font magisk module Updated the zip and it works now

 

[LLStarks]

Just a PSA for those on Android 13 Beta 2.1:

Starting with Canary 24314, updating to a new Magisk version via direct install results in a bootloop. This behavior has continued with the latest Beta 25/Canary 25001. Patching the boot image, however, allows the phone to boot as expected.

An issue was opened but unfortunately closed as "not planned". So for those on Android 13 Beta 2.1 (and beyond most likely), when updating Magisk you'll want to avoid the direct install method and patch and flash the boot image instead to avoid a bootloop until they decide to resolve this issue.

Patching an already patched img result in a bootloop · Issue #5938 · topjohnwu/Magisk

When patching a stock image and booting it's working fine, When patching an already patched image the device bootloop. Here's what I tested Working: patching a stock file manualy, then booting with...

github.com

That's what that bull**** was? Had to deal with that a few times and eventually figured it out.

Looks like the other issue was closed for a more official one.

`magiskboot` cannot repack boot.img without ramdisk TWICE · Issue #5944 · topjohnwu/Magisk

Device: Pixel 6P Android version: 13 Beta 2.1 Magisk version name: debug Magisk version code: 25001

github.com

 

[Lughnasadh]

That's what that bull**** was? Had to deal with that a few times and eventually figured it out.

Looks like the other issue was closed for a more official one.

`magiskboot` cannot repack boot.img without ramdisk TWICE · Issue #5944 · topjohnwu/Magisk

Device: Pixel 6P Android version: 13 Beta 2.1 Magisk version name: debug Magisk version code: 25001

github.com

Yep. Even though she closed that initial issue as "not planned", her and Canyie seem to be working on it, so that's good news. At least she won't close her own issue without fixing it first, you would think.

 

[vibrantliker]

It was font magisk module Updated the zip and it works now

figured it out, it was 2 of Tulsadiver's mods (font and no battery icon)

 

[Lughnasadh]

Just a PSA for those on Android 13 Beta 2.1:

Starting with Canary 24314, updating to a new Magisk version via direct install results in a bootloop. This behavior has continued with the latest Beta 25/Canary 25001. Patching the boot image, however, allows the phone to boot as expected.

An issue was opened but unfortunately closed as "not planned". So for those on Android 13 Beta 2.1 (and beyond most likely), when updating Magisk you'll want to avoid the direct install method and patch and flash the boot image instead to avoid a bootloop until they decide to resolve this issue.

Patching an already patched img result in a bootloop · Issue #5938 · topjohnwu/Magisk

When patching a stock image and booting it's working fine, When patching an already patched image the device bootloop. Here's what I tested Working: patching a stock file manualy, then booting with...

github.com

Looks like the issue may have been fixed with these commits...

Don't skip backup even if original does not exist · topjohnwu/Magisk@7bf9c74

Close #5945, fix #5944

github.com

Don't backup ramdisk created by Magisk · topjohnwu/Magisk@89ff3c6

Fix topjohnwu#5938, fix topjohnwu#5944

github.com

 

[Nekromantik]

are people sticking with 24.2 Magisk instead of updating while still on stock A12 firmware?
or is Magisk 25 fine and does not need you to disable verity and vbmeta?