yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] moichman:
yay! profit!

i downloaded a fresh copy of the factory image and copied init_boot.img to platform tools. since there was a slight difference from what was supposed to be in the tb checker results, i am going to detail it all.

i did the first step 1 and 2, and noticed something odd when i ran tb checker. after the xposed check, all references regarding magisk failed. also, the magisk random package name was enpty, even though the magisk app was installed. that cinched what the problem was, in my mind. i went ahead and deleted magisk as you suggested.

i did part 2 step 1 and flashed init_boot.img, as you suggested. i then installed the magisk app and pushed the init_boot.img to the pixel, and patched it. after pulling the patched image and flashing it as you suggested in part 2 step 2 and rebooted it now says the device is rooted and apps recognize it.

thank you, @Homeboy76 and @simplepinoi177 for taking the time to analyze and respond, and offering succinct advice!
[Google Pixel 7 Pro] Homeboy76:
Magisk Beta Update

Magisk Beta v26.2

[MagiskBoot] Support extracting boot image from payload.bin

[MagiskBoot] Support cpio files containing character files

[MagiskBoot] Support listing cpio content

[MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation

[Daemon] Make daemon socket a fixed path in MAGISKTMP

[resetprop] Support printing property context

[resetprop] Support only printing persistent properties from storage

[resetprop] Properly support setting persistent properties bypassing property_service

[MagiskSU] Support -g and -G options

[MagiskSU] Support switching mount namespace to PID with -t

[MagiskPolicy] Fix patching extended permissions

[MagiskPolicy] Support more syntax for extended permissions

[MagiskPolicy] Support printing out the loaded sepolicy rules

[App] Support patching boot image from ROM zips

[App] Properly preserve boot.img when patching Samsung firmware with init_boot.img

Magisk Canary Update

Magisk (e47e869f) (26201).

Sync with public release

Diffs to v26.2

N/A

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 7 Pro] supermansaga:
took the plunge to update. So far so good. Thanks
[Google Pixel 7 Pro] linuxares:
ohh neat
[Google Pixel 7 Pro] gpvecchi:
Sync with public release means that stable and canary are actually the same?
[Google Pixel 7 Pro] justDave:
Beta and canary for now, I believe.
[Google Pixel 7 Pro] Homeboy76:
I don't think so.
[Google Pixel 7 Pro] moichman:
i have sort of a follow up question to my previous, but it's not directly related.

i had an essential phone, before the pixel 7 pro. when i did an ota update, i would restore the image in magisk, do the ota update, and do an install to the inactive slot (after ota).

i assume, now, that with init_boot.img that it's not the same process, and that i have to extract and patch the image each time. correct?
[Google Pixel 7 Pro] Homeboy76:
I'm not sure the OTA Upgrade Guides, instructions to "install to the inactive slot (after ota)." are working.
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, by my general observation, more and more people have had success using this method as of late. That post of mine was 7 months ago, so it's been a while. I can't comment further than that since I never use that method. Thus, your mileage may vary.
[Google Pixel 7 Pro] moichman:
so install to inactive slot (after ota) may or may not work?

i was using pixelflasher and doing the ota and rerooting worked well. however, when i had that issue with losing root, i wasn't sure if it was pixelflasher that was responsible, or i was (by inadvertently clicking something incorrectly), or if it was just one of those things. doing it manually wasn't ever that much effort, so until it's better defined i can't go wrong by restoring the stock init_boot.img, installing the ota (or factory image with keep data), and then rooting it from scratch.

thanks for the input.
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

Magisk (de00f1d5) (26202)

[General] Fix device information detection script

Diffs to v26.2

[General] Fix device information detection script

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 7 Pro] jlokos:
I need some help; I cleaned flashed the August firmware on my wife's 7 pro and rooted using Magisk 26.1 and displax's safetynet-fix-v2.4.0-Mod_2.0.zip. When I run Yasnac's safetynet checker, CTS profile fails. Zygisk is checked as is enforce denylist and google play services and and google play store are on the denylist. In google playstore it also says the device isn't certified even though I registered the device. Any thoughts on how I might resolve this? It was all pass in July.
[Google Pixel 7 Pro] Lughnasadh:
Use Displax's 2.4.0-1.3 zip. Need that one as of now on Pixel 7s.
[Google Pixel 7 Pro] jlokos:
Thanks very much. I'll give that a shot when I get home.

Update: I flashed the 1.3 zip and everything passed. Thanks again for the heads up!
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

Magisk (96e559fb) (26203)

[General] Update BusyBox to 1.36.1

[General] Fix compiling toolchain that produces broken arm32 executables

Diffs to v26.2

[General] Fix device information detection script

[General] Update BusyBox to 1.36.1

[General] Fix compiling toolchain that produces broken arm32 executables

magisk-files/notes.md at canary · topjohnwu/magisk-files · GitHub

Download

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 7 Pro] Golf c:
Boy it feels like rooting is getting less popular? I Never understood how 1 person or 2, can carry the heavy load of ROOT! Started rooting early on , and like all things in my life, I go all in, loose interest, and move on. Still rooting stock for mostly Aesthetics. And those Advertisements destroy my soul . Roms, I lost all interest.
[Google Pixel 7 Pro] Homeboy76:
Magisk

Beta/Stable

Update

Magisk Beta/Stable v26.3

[General] Fix device information detection script

[General] Update BusyBox to 1.36.1

[General] Update toolchain that produces broken arm32 executables

[App] Fix root service unable to bind on OnePlus devices

Magisk Canary Update

Magisk (d4e552d0) (26301).

Upstream to latest release

Diffs to v26.3

N/A

Download Magisk Canary

Tap app-release.apk

Tap the three dot menu across from

Code

Blame

Tap Download
[Google Pixel 7 Pro] jolly_roger_hook:
Can any pixel 7 pro. Bottleader be unlocked or is it only ones straight from factoryike ones from fi or Google directly?
[Google Pixel 7 Pro] Pixel86:
My main motivator to root is to enable the Wireguard kernel space function. So worth it to me.
[Google Pixel 7 Pro] Homeboy76:
The Google Pixel 7 Pro phones purchased directly from Google/Fi are bootloader unlocked. The Google Pixel 7 Pro phones from purchased from U.S. carriers (ATT, T-Mobile, and Verizon) are normally are sold with the bootloader locked. These carriers, normally, do not ever unlock the bootloader.
[Google Pixel 7 Pro] supermansaga:
What does this function do exacrky
[Google Pixel 7 Pro] moichman:
if i may ask what may be a stupid question. in the instructions on the first page, i certainly appreciate the detailed instructions and covering the varied situations and outcomes. i am comfortable with, and have done on my old phone, running the flash-all.

my question is this: if one is simply doing a monthly update on an already rooted phone, is there a reason to go through the process of extracting the flash-all and editing, etc? is it better than flashing the stock image, doing the OTA through settings, then flashing the patched init_boot.img back...or will this miss something that using flash-all won't?

similar questions apply to upgrading to 14, when it's released. can i flash the stock image, do the upgrade, then flash the patched init_boot.img, or is it better to flash-all, etc?

thanks!
[Google Pixel 7 Pro] Homeboy76:
If you just use the flash-all.bat file without editing it, it will wipe your phone.

If you take the automatic OTA it will unroot your phone and you have to flash Magisk to the inactive slot or flash the new patched init_boot. img that you extracted from the latest factory image.

There are some post that state the latest Magisk Alpha/Canary can extract the init_boot.img from the OTA.zip file. At this point in time I am not familiar with that process.

I'm hoping @shoey63 who has extracted the init_boot.img from the OTA.zip will share the process he used to do it.
[Google Pixel 7 Pro] shoey63:
Well I know for a fact that extracting and patching the boot.img from an update archive works on the Pixel 6, and I'm assuming it will do the same for other devices, maybe even automatically patching init_boot.img where required. (untested)

Anyway, the process is :

Open Magisk

Tap Install

Tap Select and patch a file

Navigate to the OTA.zip, or any archive containing payload.bin or an archive that contains boot/init_boot.img.

Tap it then tap the check mark (✓)

Tap Lets go

Update using your preferred method and then flash the patched image via fast boot.
[Google Pixel 7 Pro] Misterxtc:
I use payload-dumper-go to extract ota files and rom zips. Just drag and drop the zip you want to extract on the payload dumper.exe and it extracts all the files in the ota or whatever you are extracting from. I just tried it on the August ota for the P7P.
[Google Pixel 7 Pro] Homeboy76:
So, there is an init_boot.img in the Google Pixel 7 Pro OTA.zip file. Thanks for extracting and sharing the Google OTA.
[Google Pixel 7 Pro] Misterxtc:
I figured I would share the link to the extractor instead if the init_boot.img because of the different build numbers and a update coming soon. The extractor works great on Win11. Thanks @AnierinB for sharing the link to the extractor in his rom thread.
[Google Pixel 7 Pro] Homeboy76:
I have one more question: Did you disable/remove all the

modules

in the Magisk app before you used Magisk to patch the the Google OTA.zip file?

Why?

Several, XDA members experienced boot loops when they flashed a magisk_patched...img file that was patched with a Magisk app that had modules enabled that were not updated for the Google OTA image file.
[Google Pixel 7 Pro] moichman:
i know you asked someone else, but i've read it both ways. using pixel flasher, i have disabled the one module i had and updated, and another time i forgot. what i can't answer is if not doing it is what coincided with my root not taking (earlier post on this forum). that said, i didn't boot loop when i forgot to disable.
[Google Pixel 7 Pro] shoey63:
No, but boot loops are always possible when updating the rom with modules enabled,

typically those that affect system files like AOSP type mods which haven't been updated.

You need to know how to boot into safe mode in that case so that they will all be disabled.

Then re-enable one by one until the culprit is found
[Google Pixel 7 Pro] Homeboy76:
Thanks!

Thanks!
[Google Pixel 7 Pro] Homeboy76:
I appreciate your input.

I know there are modules that can be left enabled that will not cause boot loops. I also know that changes in a updated factory or OTA image can render modules inoperable and cause boot loops. That being said, I believe "an ounce of prevention is worth more than a pound of cure". In other words, disabling modules before patching the init_boot.img is worth way more than the hassle of clearing a boot loop. :)
[Google Pixel 7 Pro] badabing2003:
In my experience I have not seen the outcome of the generated patch change when modules are kept enabled.

Differently said, when creating a patch you can keep the modules enabled or disabled, the patches will be binary identical, so no worries during patch creation.

As @shoey63 said, the boot loop risk is when you boot to the patched system, it is at this point that disabled modules keep you safer.
[Google Pixel 7 Pro] Homeboy76:
Does it really matter when "disabled modules keep you safer"? Yes.

My point is, if you can prevent a

boot loop

from happening by disabling modules before patching the init_boot.img. Why, would you wait until your phone

boot loops

to disable the modules?
[Google Pixel 7 Pro] badabing2003:
I think you missed my point.

I'm absolutely in agreement with you about preventing a bootloop and encouraging to disable suspect modules.

I was merely clarifying the point that the impact of suspect modules has nothing to do with how you create a patch, but rather when using the patch (booting to it).

Your statement might have led people to believe that as long as they disabled the modules while creating a patch, they were safe.

Here's an illustration

Assuming that one has a module that would cause bootloop.

If one performs the following action.

Disable modules

create a patch

enable modules

apply patch, reboot

or the following action

create a patch

apply patch reboot

The outcome is the same, bootloop.

On the other hand. This won't bootloop

create a patch

disable modules

apply patch, reboot

As you can see it has nothing to do with creation of the patch but rather the use of it.

Of course I believe your message is about disabling the modules and keeping them disabled before booting to the patch, and you're right if you disable them before patching, and keep them that way, you're safe.

I just didn't want people to think that they're safe like in the first example.
[Google Pixel 7 Pro] Homeboy76:
You're right I missed your point, I apologize.

I missed it because I do this every time I update and re-root:

<<edited - to show all the steps>>

download the latest factory/OTA image <<edit>>

extract image...zip from factory image <<edit>>

disable modules

reboot <<edit>>

create a patch

flash/sideload factory/OTA image <<edit>>

flash patch <<edit>>

reboot <<edit>>

enable modules

reboot
[Google Pixel 7 Pro] Lotus1922:
Cannot wait to try this, thank you for the work!

Question, I have a small wishlist of features that I loved on my old phone/ previous iterations of Android OS that are apparently missing on Pixel 7 Pro Android 13. I'm hoping there are custom ROM's or other post-root magic that could enable this. Namely:

- Ability to organize app drawer by dragging icons onto each other to create folders that can then be custom named or color themed a la Android Marshmallow

- Press and holding the "back" button in Chrome to display page history and manually pick which page to go back to, instead of having to blindly click backwards to get to where you want.

- Unleashing any extra latent camera features/options

- My last LG had a cool "quick draw" feature where you could double-press the power button to open the camera app and immediately snap a photo. The Pixel opens the camera with double-press, but you still have to manually press the shutter. The voice triggered shutter would also be nice to have again.

Are any of these possible to tweak by rooting with a custom ROM?

Many thanks again in advance!
[Google Pixel 7 Pro] Homeboy76:
This forum has a list of most of the Custom ROMS for your Google Pixel 7 Pro: Google Pixel 7 Pro

Tap Development to see the Custom ROMS.

Tap the ROM link and read the OP (post #1). The OP list the features of the ROM, Instructions to install the ROM, etc.
[Google Pixel 7 Pro] Subl1m1nal1:
So during this process of attempting the dual boot, steps:

(NEW) Make Both Slots Bootable:

Manually

, Flash the OTA Image to Both Slots - One

bootable and rooted

, the other slot

bootable without root

.

in this section, my device now seems to always have ramdisk "yes" even after fully flashing both slot a and slot b and i'm getting the "your device is corrupt it can't be trusted and may not work properly message"

It won't properly boot in slot a and boots in slot b. however still same error etc.

Any guidance/help would be huge.
[Google Pixel 7 Pro] Homeboy76:
The

Ramdisk yes

message is ok.

Is slot b rooted?

If yes, adb sideload the same Google OTA zip that you sideloaded again

while on slot b

.
[Google Pixel 7 Pro] Subl1m1nal1:
I was so concerned the "corrupted" was due to something I ****ed up with magisk still showing ramdisk "yes" and not due to the unlocked bootloader. I'll freshly image both slots and lock the bootloader to confirm everything is good, but if magisk is still "yes" on ramdisk even without root is that bad?
[Google Pixel 7 Pro] Homeboy76:
First, if you want to do this: (NEW) Make Both Slots Bootable: 3.

Manually

, Flash the OTA Image to Both Slots - One

bootable and rooted

, the other slot

bootable without root

.

You cannot relock the bootloader afterwards. Why? Your phone has to be 100% stock. If you lock the bootloader and your phone is not 100% stock you could brick it.

After, doing 3. Manually, Flash the OTA Image to Both Slots - One

bootable and rooted

, the other slot bootable without root. One of the slots on phone is rooted which means your phone is

not

100% stock.

Second, "if magisk is still "yes" on ramdisk even without root is that bad?" No
[Google Pixel 7 Pro] supermansaga:
Sorry. I am slow. If this bifurcated treatment means the phone is still not 100% stock, what can we do with the unrooted slot? Presumably, Google One VPN still won't work on this unrooted slot? Or Intune Company Portal 5.0.5981 could still give us headache? Trying to understand what can someone achieve with such bifurcated treatment. I am almost on the brink of relocking my bootloader, because Intune simply won't work as discussed at https://xdaforums.com/t/tutorial-ro...-update-q3-2023.4402273/page-20#post-88996973
[Google Pixel 7 Pro] Lughnasadh:
The "Your device is corrupt. It can't be trusted and may not work properly." message is not part of the unlocked bootloader message. It is the RED eio corrupt message.

The system is just noticing the expected and calculated hash on the boot partition doesn't match. The bootloader is looking for an updated OS. Flashing an old boot image and then a new/current boot image often gets rid of it. The bootloader notices an updated boot image and switches back to restart mode instead of eio mode.

I have not seen anyone report any ill effects from having this message. You can likely leave it as is if you want, do the old/new boot image maneuver or wait until the next update which "should" get rid of the message as well.
[Google Pixel 7 Pro] Homeboy76:
Nice catch, you're right ""Your device is corrupt. It can't be trusted and may not work properly." message is not part of the unlocked bootloader message. It is the RED eio corrupt message. "

@Subl1m1nal1
[Google Pixel 7 Pro] Homeboy76:
One, the

phone

is not 100% stock because one slot is rooted.

Two, by switching to the

unrooted slot

you should pass safetynet with all app that do not check for unlocked bootloaders.
[Google Pixel 7 Pro] Subl1m1nal1:
Is there a way while flashing root to not lose user data?
[Google Pixel 7 Pro] Lughnasadh:
As long as your bootloader is already unlocked, you won't lose data when rooting. If your bootloader isn't unlocked, then to root you will have to unlock it, which in turn requires a data wipe.
[Google Pixel 7 Pro] supermansaga:
Thanks. In that case, then maybe Google One VPN still won't work. Given the trend, I have decided to re-lock my bootloader and go stock. I am now able to use Google One VPN and Intune 5.0.5981 for company resources. Just lose the ability to GPS Setter, which is not maintained anymore, and Call Recording. I guess one can't have the cake and eat it too.
[Google Pixel 7 Pro] supermansaga:
Thanks. I just re-lock and yes there is a wipe, but thanks to the simple backup, most of all my play store app's positions and folders are maintained. So I think I am more comfortable of doing a wipe these days.
[Google Pixel 7 Pro] gpvecchi:
Google VPN works with rooted phones and safetynet fix. You just can't use Xposed.
[Google Pixel 7 Pro] supermansaga:
Thanks for the insight. Then I guess there isn't much point for me to keep rooted, because call recording and gps setter are all Xposed based. Unless there are Magisk modules directly comparable and free.

Also, after I relock, my play system update is back to 2/1/2023. Weird
[Google Pixel 7 Pro] gpvecchi:
I use Google Dialer Mod to enable call recorder on stock dialer, no need for Xposed.
[Google Pixel 7 Pro] badabing2003:
Google Dialer Mod does not work for all, it didn't for me.

BCR, basic call recording works very well, it's a Magisk module.

The are few other material modules that do the job too.
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
Greetings, does BCR work with A14 beta 5.3? Sorry for the out of topic query.
[Google Pixel 7 Pro] badabing2003:
I'm still on A13, and it works on A13, you'd have to check their forums / Github
[Google Pixel 7 Pro] xdrc45:
I don't want to hijack @Homeboy76 thread but It's obvious that Google VPN is not working for some and is working for others. I don't know if it's a regional thing or a server side issue or what the problem is that's causing it to not work for some. I see a lot of speculation as to what the root cause of the problem is, but there isn't definitive answer. For me, it has worked for months now and I have a P7P bootloader unlocked, with dm verity and verification disabled, rooted with magisk 26.3, universal safetynet fix v2.4.0-MOD_1.3, a custom kernel, and I also have LSPOSED installed and active and Google 1 VPN is working without any issues.
[Google Pixel 7 Pro] Homeboy76:
Google's September 2023 factory and OTA are up!
[Google Pixel 7 Pro] scorpio76r:
I may not take this update. I will just wait till October 4th to update to android 14 stable.
[Google Pixel 7 Pro] andrew2432:
Ok I feel dumb...

Adb reboot fastboot

Fastboot flashing unlock

FAILED remote: unrecognized command flashing unlock

Fastboot: error: command failed
[Google Pixel 7 Pro] Lughnasadh:
ad reboot fastboot puts you in fastbootd and you want to be in fastboot. So use adb reboot bootloader instead.
[Google Pixel 7 Pro] andrew2432:
Thank you, I used buttons and sort of figured that out but that clears it up for sure.

Now I'm looking at the rooted/unrooted slots. before I unlocked my bootloader I patched both factory init_boot and OTA init_boot with magisk. Can I use these or should I patch them again with my new device? Does it matter? I had no modules when patching, I didn't have root, just the manager app. Then...how do I know if I'm rooted or not? Just reboot until I am? Sideloading the OTA flashes the new bootloader and removes root correct? So I can test root really fast with the module I'm interested in and then disable it...sideload OTA twice, reboot and flash patched image once yes?

Sorry to be annoying lol
[Google Pixel 7 Pro] Homeboy76:
@andrew2432,

I'm assuming you have unlocked the bootloader on your Google Pixel 7 Pro, it has the the September 2023 Factory or OTA image installed on it, you have

Platform-tools r. 33.0.3

installed on your computer, and you patched the init_boot.img from the September 2023 Factory or OTA images using that phone. If all my assumptions are correct, you can use the magisk_ patched...img to root your.

To root your phone:

a. boot

fastboot mode

on your phone

b. Connect your phone to your computer

c. Open a command prompt on your computer in the platform-tools folder and type:

fastboot flash init_boot magisk_patched....img (full name of the init_boot.img).

d. When it finishes type: fastboot reboot
[Google Pixel 7 Pro] andrew2432:
Thanks for the response homeboy and every guide I've ever read by you lol

I'm playing with panther just to make things difficult lol. I am currently rooted. Because I have some apps that won't work rooted I was really looking at the root/unrooted boot. I really want to get that working. I already have Sept OTA zip patched with magisk saved on my comp. I guess unlocked bootloader will trigger some things idk about yet, but I was assuming I could root one side and leave one side unrooted for the bits root messes with