You need to extract the init_boot.img not the boot.img.Hello
I have a fail on the magisk_patched.img flash :
FAILED (remote: partition (init_boot) not found)
I take the last platform tool (r33.0.3), usb drivers on Android studio, flashing factory firmware as it said on tuto (november one).
So, what am i forgetting please?
That was done.
fastboot flash init_boot_b magisk_patched-25200_T9evv.img
tryThat was done.
testing this :fastboot flash init_boot_b magisk_patched-25200_T9evv.img
And that's pass!!
fastboot flash init_boot magisk_patched-25200_T9evv.img
That's what i try since yesterday, and i don't know why, but i can't change slot with adb or PixelFlasher. I can't flash factory image on the second slot too. That why i try the init_boot_b command.tryCode:fastboot flash init_boot magisk_patched-25200_T9evv.img
Your device is in bootloader mode?That's what i try since yesterday, and i don't know why, but i can't change slot with adb or PixelFlasher. I can't flash factory image on the second slot too. That why i try the init_boot_b command.
With init_boot_b command, it the first time it passed.
fastboot getvar current-slot
fastboot --set-active=other
fastboot reboot bootloader
fastboot getvar current-slot
Your device is in bootloader mode?
What do you get when you issue this command"
Code:fastboot getvar current-slot
What happens when you do
Code:fastboot --set-active=other fastboot reboot bootloader fastboot getvar current-slot
Actually he did, cross posting is always messy.
Hence why I wanted to know why he can't change slots, it does not make sense.
Thank you for posting your solution.My wish is rooting, and i was blocked. With my edit, i find the solution but i think it's not a normal command.
I just write my command to help others members in the same situation
Sorry for my bad english!
Your carrier is Verizon so use the Verizon factory/ota image if it is available. If it is not available use the Global factory/ota image.Hey Guys I've got a question? I'll be getting my 7pro tomorrow from Google I'm hoping it will have the Global version on it. I have a OnePlus 10 pro now that's enough of that. I'm on Verizon I'll be unlocking the bootloader before I put my sim in also. My question is I noticed in the op under Google Pixel Updates there was one for the Global and also one for Verizon. Now I know wants I put my sim in Verizon will fill my phone up what all kinds of crap. OK so do I want to stay with the Global ver. or go with Verizon? O thanks for your help also. This phone will be a new experiences for me. I've been with OnePlus for a long time.
I understand you are putting your phone on the Verizon network, but did you purchase your phone from Verizon? Or did you purchase it from Google, Amazon, Swappa, or any other third-party site -- anything outside of any carriers? Because if you did purchase it through Verizon (or any carrier), it won't matter whether you put the sim before or after unlocking the bootloader, most likely you will not be able to unlock the bootloader because the OEM unlock toggle will be greyed out and unable to switch -- without the switch you would not be able to unlock the bootloader successfully...Hey Guys I've got a question? I'll be getting my 7pro tomorrow from Google I'm hoping it will have the Global version on it. I have a OnePlus 10 pro now that's enough of that. I'm on Verizon I'll be unlocking the bootloader before I put my sim in also. My question is I noticed in the op under Google Pixel Updates there was one for the Global and also one for Verizon. Now I know wants I put my sim in Verizon will fill my phone up what all kinds of crap. OK so do I want to stay with the Global ver. or go with Verizon? O thanks for your help also. This phone will be a new experiences for me. I've been with OnePlus for a long time.
If you are on Verizon's cell line, it would be best to use their factory/ota image as it has certain "tweaks" for the Pixel 7 Pro & their network; if not, using the Global factory/ota image works just as well -- even if you did load Verizon's factory/ota image on a device that isn't on their line, the images are comparable and either would be safe to use; it's just as matter of having one that would have said "tweaks" applied for Verizon's line or not...Your carrier is Verizon so use the Verizon factory/ota image if it is available. If it is not available use the Global factory/ota image.
Please read the post before you reply:I understand you are putting your phone on the Verizon network, but did you purchase your phone from Verizon? Or did you purchase it from Google, Amazon, Swappa, or any other third-party site -- anything outside of any carriers? Because if you did purchase it through Verizon (or any carrier), it won't matter whether you put the sim before or after unlocking the bootloader, most likely you will not be able to unlock the bootloader because the OEM unlock toggle will be greyed out and unable to switch -- without the switch you would not be able to unlock the bootloader successfully...
If you are on Verizon's cell line, it would be best to use their factory/ota image as it has certain "tweaks" for the Pixel 7 Pro & their network; if not, using the Global factory/ota image works just as well -- even if you did load Verizon's factory/ota image on a device that isn't on their line, the images are comparable and either would be safe to use; it's just as matter of having one that would have said "tweaks" applied for Verizon's line or not...
Some other people feel the same way.I have a Google phone on Verizon and I have never put the Verizon update on it. I'm afraid that it will come with all their crapware.
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.