FYI, I have been using update method install into inactive slot through Magisk for awhile now. At least the past 2 or 3 times and going from stock to beta. No issues at all for me.
"...stock to beta" Are you using these instructions to do that?FYI, I have been using update method install into inactive slot through Magisk for awhile now. At least the past 2 or 3 times and going from stock to beta. No issues at all for me.
I do my monthly updates with PF and I use the steps to install the update to the inactive slot."...stock to beta" Are you using these instructions to do that?
I wonder has anyone else been sucessful installing to the stock OTA inactive slot, manually, on their stock Pixel 7 Pro.
Excellent!I do my monthly updates with PF and I use the steps to install the update to the inactive slot.
I'm getting a 404 on your link. Think because it has a / at the end? Without the slash it's ok.Excellent!
I have a link to PF in this thread.
Once upon a time a member oould install to the inactive slot using these instructions. I want to know has anyone been able to install to the intactive slot on their Pixel 7 Pro phone using the aforementioned instruction.
I fixed the links, thanks.I'm getting a 404 on your link. Think because it has a / at the end? Without the slash it's ok.
I've seen a handful or so of people successfully use this method over the past few months, but I've seen more who have been unsuccessful, for what it's worth.
Oh my bad. I haven't tried using those instructions for a while. Having PF makes the process to easy. I still follow your guides though!Excellent!
I have a link to PF in this thread.
Once upon a time a member could install to the inactive slot using these instructions. I want to know has anyone been able to install to the intactive slot on their Pixel 7 Pro phone using the aforementioned instruction.
Only thing I do differently is I don't untick auto updates and restart it on the update screen.I fixed the links, thanks.
Yeah, that's why that particular set of instructions has astrick throughmore people are unsuccecessful using this method to install to the Inactive Slot.
Ok, thanks for sharing your method.Only thing I do differently is I don't untick auto updates and restart it on the update screen.
Steps I do
I see the update notification
I uninstall Magisk, just restore images
Go to update screen and let it fully update
Once the restart button is there on update screen,
I head over to magisk install to inactive slot,
After that is done go back to update screen and restart it there via bottom restart button.
It worked on stock, then I went to android beta, it worked. That was December I jumped back on beta. Then January update did the same way to update.
You update it in the app without a problem. As for installation, I had an issue last month with PixelFlasher not installing Magisk correctly, - it wouldn't grant SU to any of the apps I needed it to, so I just installed it as any app, downloaded and installed with Package Manager, and it was fineHi. Sorry if this has already been asked but can magisk be updated as usual (Install - Direct install) on Pixel 7?
On Samsung it's easy as that but Pixel has A/B partitions and I'm not sure if updating magisk this way will not break something and leave the phone unbootable. Thanks.
Yes.Hi. Sorry if this has already been asked but can magisk be updated as usual (Install - Direct install) on Pixel 7?
On Samsung it's easy as that but Pixel has A/B partitions and I'm not sure if updating magisk this way will not break something and leave the phone unbootable. Thanks.
You update it in the app without a problem. As for installation, I had an issue last month with PixelFlasher not installing Magisk correctly, - it wouldn't grant SU to any of the apps I needed it to, so I just installed it as any app, downloaded and installed with Package Manager, and it was fine
That was supposed to say that you can update in the app itself not implying that that’s the only way to do it. My bad on the typo.Huh???
The answer to his question is in the OP (Post 1), ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,
6. Set Magisk App Update Channel/Update Magisk,
• Update Magisk
I assume you are talking about updating the Magisk version within the Magisk app (via direct install)? If so, Magisk does have the ability to find and patch the init_boot.img. Support for that was added back in March of last year.Ya'll are confusing the heck out of me. Wouldn't 100% be unsuccessful using that link method? As Magisk wants to patch the boot.img and not init_boot.img the Pixel 7 needs?
No I am referring to taking the OTA, open Magisk and install to Inactive Slot(after OTA). Then reboot, doesn't that fail?I assume you are talking about updating the Magisk version within the Magisk app (via direct install)? If so, Magisk does have the ability to find and patch the init_boot.img. Support for that was added back in March of last year.
![]()
Add init_boot parition · topjohnwu/[email protected]
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.github.com
Ah, ok. There have been a few people (that I have seen) on the Pixel 7 series who have been successful using that method, but most have not. There are 2 Github issues opened related to this issue. The devs couldn't find any problems with the script and no one has provided a log so they can look into it more. Until logs are provided, they can't work on a fix or figure out why some are successful while most are not.No I am referring to taking the OTA, open Magisk and install to Inactive Slot(after OTA). Then reboot, doesn't that fail?
Ok thanks, so I wasn't going crazy lolAh, ok. There have been a few people (that I have seen) on the Pixel 7 series who have been successful using that method, but most have not. There are 2 Github issues opened related to this issue. The devs couldn't find any problems with the script and no one has provided a log so they can look into it more. Until logs are provided, they can't work on a fix or figure out why some are successful while most are not.
![]()
Magisk wants to patch boot part instead of init_boot on devices that ship A13 · Issue #6380 · topjohnwu/Magisk
Device: Pixel 7 Global Android version: 13 (comes with A13 and therefore used init_boot) Magisk version name: latest debug Magisk version code: 25205 On devices that ship with A13 (pixel 7 for now)...github.com
![]()
Magisk won't backup init_boot.img · Issue #6378 · topjohnwu/Magisk
Device: Pixel 7 Android version: 13 Magisk version name: cf9957c Magisk version code: 25205 I'm using the latest version of Magisk on my pixel 7 and everything works fine. However, there is a small...github.com
Depends on how you're applying.That's why I am a bit hesitant to unreroot and reroot to 25206, though I am dying to enable 5g again for China telecom.
You must be a mind reader, I was in the process of adding Disabling Verity and Verification to the OP.I suggest to add the guide to disable verify and verification in the first post, I didn't do this, and now I need another full wipe to install a custom kernel.
fastboot flashing unlock
and press enter.fastboot reboot
at the Command Prompt and press enter.fastboot flashing lock
fastboot reboot
adb wait-for-device shell magisk --remove-modules
fastboot Reboot
flash-all
at the Command Prompt and press enter.flash-all
at the Command Prompt and press enter.fastboot flash init_boot magic_patched....img
at the Prompt and press enter.fastboot reboot
at the Prompt and press enter.fastboot flash init_boot --slot all init_boot.img
adb wait-for-device shell magisk --remove-modules
fastboot devices
to verify communication with phone. It should return your phone's serial number.I know what your problem is, I'm trying to be helpful here, but I find it that you are either unwilling or unable to provide the information you're being asked.OK The sdk files that I downloaded are from AUG 2022 version 33.0.3
adb and fastboot are in Windows C: \Platform-Tools
Here are the directory contents
Ok for some reason I can't post the contents of the dir. so adb fastboot files and magisk_patched-25200_OKTza.img are in the Platform-Tools directory. Is that what your asking?
where
commandsI assume you are talking about updating the Magisk version within the Magisk app (via direct install)? If so, Magisk does have the ability to find and patch the init_boot.img. Support for that was added back in March of last year.Ya'll are confusing the heck out of me. Wouldn't 100% be unsuccessful using that link method? As Magisk wants to patch the boot.img and not init_boot.img the Pixel 7 needs?
I would add to it that doing it to both slots assures that the inactive slot does not have anything non stock on it.Ok, can we agree using this method may be the safest method to Return phone to stock:
Use the Android flash tool: select Wipe => Force Flash Partitions => Lock Bootloader.