yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary

These versions of Magisk Canary are all broken: 25207, 25208, 25209, and 25210.

The last working Magisk Canary 25206 - app-release.apk can be downloaded here.
[Google Pixel 7 Pro] cmh714:
209 was working just fine for me....
[Google Pixel 7 Pro] Homeboy76:
SDK Platform-tools

SDK Platform-tools r34.0.1 has been released.

There is a link in the OP, ~ ~ ~ Part I - INFORMATION ~ ~ ~, 2. Prerequisites, • A Computer with the latest SDK...
[Google Pixel 7 Pro] supermansaga:
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.
[Google Pixel 7 Pro] badabing2003:
Depends on how you're applying.

Direct install works, but patching stock boot and applying that (ie dirty flashing) which you would do with March release (when it comes out), you lose root.

Hopefully by then 25211 will be out, otherwise I advise you to either install the stable version or 25206.
[Google Pixel 7 Pro] gpvecchi:
I'm on the test build and Android 14 DP2, banking apps work but I don't have the certification. I cleaned Play Store and Play Services data...
[Google Pixel 7 Pro] dd805bb:
https://xdaforums.com/t/march-8-202...-also-for-future-major-android-betas.4550933/

Go to here and check it out. Not passing cts is normal for DP 14 and 13 qpr releases. That isn't a magisk issue but DP 14 known issue.
[Google Pixel 7 Pro] Homeboy76:
SDK Platform-tools

Several members of the XDA community have

written posts that SDK Platform-tools r34.0.1 is

broken

. Problem: fastbootd not working

Use SDK Platform-tools r33.0.3: https://xdaforums.com/t/guide-root-...der-pass-safetynet-more.4505353/post-88261723
[Google Pixel 7 Pro] mochamoo:
Am on 25209. Dirty flashed the March update. Patched init_boot image via magisk and fastboot flashed it after flashing the update. All good here. Rooted. Adaway works. I thought I might have to go back to 25206 but 25209 is working fine so I am leaving well enough alone for now.
[Google Pixel 7 Pro] badabing2003:
Thanks,

Suspecting that the issues are device specific, but that's just a guess.

See this discussion.
[Google Pixel 7 Pro] supermansaga:
Yes. It appears 25209 is still good enough. I just followed this old video at

and updated three of my P7Ps to the March stable build. It's more straightforward now that I get more and more comfortable with the process. And the best news is that my grouped apps based on the same subject/topic on the home screen remain intact.
[Google Pixel 7 Pro] Homeboy76:
People comprehend instructions differently, that is why there are several descriptions of how to do a thing on the INTERNET. I'm ok with people choosing a method of instructions that they can comprehend or that works for them. :)
[Google Pixel 7 Pro] mochamoo:
Yeah I prefer downloading the full update file and flashing it via ADB/ fastboot method. No flash tool here. I generally will extract and patch the init_boot.img first so it is ready to go. Maybe I have been lucky but I don't disable modules first either. After the update is fully installed and the device has rebooted - I just drop back down into ADB/ fastboot and flash the patched magisk image. Done. Have been doing it this way for years and don't see a reason to change. I just have to remember to use init_boot now.
[Google Pixel 7 Pro] synesthete:
Yeah I do the same thing. It is so much easier to have the patched img ready to flash right after all of the others.
[Google Pixel 7 Pro] gpvecchi:
Put the patched init_boot in the same folder of fastboot, name it with a simple name, don't use the quotes and the path.
[Google Pixel 7 Pro] simplepinoi177:
like I answered him in the other thread, it's most likely because he's using PowerShell...I just watched a video for re-rooting after a monthly update and the creator used powershell and it included "./" in the syntax, so there's probably that... *it actually was the youtube video a couple posts up!*

That's why I suggested that @anthonnyb98 use CMD instead....less headaches like this...
[Google Pixel 7 Pro] Homeboy76:
That is true. The instructions to open a Command (CMD) prompt are in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 8. Open a Command Prompt/Boot Fastboot Mode/Boot Recovery, • Open a Command Prompt on Computer
[Google Pixel 7 Pro] dd805bb:
KernelSU is also another way to root our phones now, FYI.. They have a manager now and module support. You can run modules like magisk but is buggy. Just another way. Zygisk for KernelSU allows you to install Zygisk modules like safetynet fix and lsposed. Systemless hosts module it is lacking.

GitHub - tiann/KernelSU: A Kernel based root solution for Android

A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.

github.com

Just another way to root or use both Magisk/KernelSU.
[Google Pixel 7 Pro] State.of.mind:
Is anyone having issues using the latest Platform tools with the March update?
[Google Pixel 7 Pro] Homeboy76:
Yes, SDK Platform-tools r34.0.0 -- ? r34.0.1 -- fastbootd doesn't work.

Use SDK Platform-tools r33.0.3: https://xdaforums.com/t/guide-root-...der-pass-safetynet-more.4505353/post-88261723
[Google Pixel 7 Pro] wrkadung:
I tried it without any issues.
[Google Pixel 7 Pro] gpvecchi:
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.
[Google Pixel 7 Pro] Homeboy76:
You must be a mind reader, I was in the process of adding

Disabling Verity and Verification

to the OP. :)

It has been added to the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 2. Install/Update Factory Image keep data,

wipe data...

However, flashing the stock factory image does not require Disabling Verity and Verification. Therefore, I also edited the Disclaimer. :)
[Google Pixel 7 Pro] simplepinoi177:
Maybe, in the section quoted below, you can add something like; anytime you run flash-all, you will have to edit in --disable-verity --disable-verification or else you will lose it and will need to wipe again to utilize a custom kernel...

Because it might be a bit confusing with the whole "

First Time

" and "When doing Subsequent updates the..." but you don't mention needing to continue to do the disabling of verity & verification each time as well...
[Google Pixel 7 Pro] Homeboy76:
@simplepinoi177

Thanks for the suggestion. :)

...but you don't mention needing to continue to do the disabling of verity & verification each time as well...

I made some changes the OP, Disabling Verity and Verification (see Notes).
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

app-release_69529ac5-25211.apk

Notes:

Tap app-release.apk

Tap 3 dots (...) across from 10.9 MB, Tap Download

...[General] Bump minimum supported Android version to Android 6.0

Google Android 14 Codename is

'Android U' or 'Upside Down Cake'

...[MagiskPolicy] Update rules to support Android U...

...This fixes boot image patching issues on Android U preview...
[Google Pixel 7 Pro] Homeboy76:
:oops: Not

another broken

Magisk Canary

Notes:

Magisk Canary 25207, 25208, 25209 (some devices), 25210 and 25211 are broken.

Magisk 25211: Some, are reporting

Systemless host

is still not working in this thread:

Magisk General Support / Discussion - starting at Post #55137

Use Magisk Canary 25206

Tap

the 3 dot menu across from 5b2934603f

Tap

Go to file

Tap

app-release.apk

Tap

the 3 dot menu across from 10.9 MB

Tap

Download

<<Edit>> Fix for Module loading, System less Host is still broken.

Waiting for Magisk 26001.
[Google Pixel 7 Pro] dd805bb:
It's broken. It's a typo.

/data/adb/module/hosts/system/etc/hosts should be the location of hosts modules. Look in the picture, it has ......"/moduleshosts/" instead of ....."module/hosts/
[Google Pixel 7 Pro] dd805bb:
Reported as bug.

It's been confirmed and fix is being done on GitHub. FYI everyone. Open source rules.
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

app-release_e2545e57-26001.apk

Notes:

Tap app-release.apk

Tap 3 dots (...) across from 10.x MB, Tap Download

Magisk Beta Update

Magisk-v26.0.apk
[Google Pixel 7 Pro] okgnew:
Good news: systemless hosts and magisk hide are working fine on Pixel 7Pro with app-release_e2545e57-26001.apk
[Google Pixel 7 Pro] supermansaga:
Many thanks for the confirmation. Presumably Marriott v10.13.1 doesn't work on this either? I am still using Shamiko whitelist
[Google Pixel 7 Pro] simplepinoi177:
@Homeboy76

I'm sure everybody would join in on my congratulations on becoming a Recognized Contributor! You certainly work diligently enough on this thread and on all your others to deserve the title!
[Google Pixel 7 Pro] okgnew:
What exactly is wrong with Marriott app?

It's working fine for me on rooted Pixel 7 Pro once I added it to Magisk's DenyList (and wiped Marriott app's data).
[Google Pixel 7 Pro] supermansaga:
Are you saying you didn't use Shamiko module white list? Please see my more relevant discussion at https://xdaforums.com/t/hotel-app-marriott-detects-magisk-and-root.4566357/. My understanding is once you use the white list feature, you don't have to add Marriott to the Denylist. This is not to mention I did add it anyways: com.marriot.mrt. I tried again just now and it still wouldn't work. It would force close and say it detected magisk, even the latest 26001. Version 10.12.0 if not 10.13.0 should be safe from such detection.

Shamiko white list is great, because all my banking apps are working great without being added on the deny list, not to mention my Google Wallet app.
[Google Pixel 7 Pro] okgnew:
I'm not using Shamiko.

I just use safetynet-fix-v2.4.0-MOD_1.2.zip module and added Marriott to Magisk's Denylist.

And it's working fine. In fact all my banking/payment apps are working fine.
[Google Pixel 7 Pro] Slim2none4u:
Indeed my Pixel 7 Pro with just safetynet fix and all bank apps work along with wallet with no need for other mod. Seems the best way to go imo.
[Google Pixel 7 Pro] supermansaga:
You also enforce the Denylist too, right? I guess it was another app that pushed me to use Shamiko. Say Company Portal and SEP Mobile. Not that the latter two work these days. Thx
[Google Pixel 7 Pro] Slim2none4u:
It's I enjoyed in deny list.
[Google Pixel 7 Pro] Homeboy76:
Yes: OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 5. Root/Reroot with Magisk and Pass SafetyNet., •

Pass Safety Net with SafetyNet Fix

, 3. Settings for Magisk,

• Enable Denylist
[Google Pixel 7 Pro] supermansaga:
I did just that enforcement, but my Marriott v10.13.1 still gets detected. I have now disabled Shamiko too. If the Denylist is that great, why would people then use HuskyDG's Magisk Delta Magisk Hides? Not that it works for me.
[Google Pixel 7 Pro] Homeboy76:
If the Marriott app is passing Safety net on one phone Google Pixel 7 Pro phone https://xdaforums.com/t/guide-root-...der-pass-safetynet-more.4505353/post-88382243 and not passing SafetyNet on another Google Pixel 7 Pro phone with the

exact same settings

. I think, the problem has to be the phone.
[Google Pixel 7 Pro] supermansaga:
I am afraid it's not just the safety net issue. It's unclear whether okgnew or slim2none4u were on 10.13.1 or earlier version. If you have time to refer to the reddit post at https://xdaforums.com/t/hotel-app-marriott-detects-magisk-and-root.4566357/, the app is trying to detect a lot of other things too. Back then, it was not even P7P focused.
[Google Pixel 7 Pro] Homeboy76:
@okgnew @Slim2none4u:

Would you, please, share the version of the Marriott app and Magisk app are you using that passes

SafetyNet for the Marriott card

.
[Google Pixel 7 Pro] Homeboy76:
It seems the problem you are having with the Marriott card cannot be fixed with the instructions for

passing SafetyNet

in this thread or these threads:

Security message when running an app

Hotel app Marriott detects Magisk and root

If you are asking

what method the Marriott card is using to detect root and what apps trigger the Marriott card root detection method.

I do not have an answer for that question.
[Google Pixel 7 Pro] cmh714:
Yes it stopped working here too. Was working the first week of March as I was at a Marriott. It broke on 13 QPR2 and is still broken on QPR3.
[Google Pixel 7 Pro] supermansaga:
Many thanks for the confirmation. I also just tried the latest Shamiko 0.7 and it still didn't work either. Not sure if anyone over there is aware of it. I found it hard to report issue on Github

Many thanks for looking into it. Everything else passes the safetynet check either with Denylist or Shamiko. Well, I guess except Company Portal and SEP Mobile and Microsoft related derived over there.
[Google Pixel 7 Pro] cmh714:
I never use Shamiko....it just worked with Magisk hide previously.
[Google Pixel 7 Pro] Homeboy76:
<<Edit>>

@cmh714

"Yes it stopped working here too." When it first stopped working "here too":

- Were you using Google's stock firmware for the your Google Pixel 7 Pro?

- What version of Magisk were you using,

- What version of the Marriot app were you using!

Questions about DP Betas should be posted on this thread: General April 6, 2023 QPR3 Beta 2.1 T3B2.230316.005 - Pixel 7 Pro [Cheetah] - [thread also for future Android QPR Betas]
[Google Pixel 7 Pro] Homeboy76:
If you are using Google's stock firmware and @topjohnwu's Magisk (Beta/Canary/Stable) Shamiko is not needed.
[Google Pixel 7 Pro] cmh714:
For me, its not some huge deal.....that is why I have not commented in the thread....I was just replying to the other comment. But yes, seems to me its a QPR issue.
[Google Pixel 7 Pro] cmh714:
Never used Shamiko on the QPR's either.....and it all has worked until recently.
[Google Pixel 7 Pro] okgnew:
See attached screenshots.
[Google Pixel 7 Pro] Homeboy76:
Thank you. The fact that your Marriott app [10.13.1 (399)] is passing Safety net is confirmation the OP Instructions for passing SafetyNet work for the Google Pixel 7 Pro that has Google's

stock

firmware on it and is rooted with topjohnwu's Magisk. :)
[Google Pixel 7 Pro] supermansaga:
The OP instructions passed safetynet check for everything else. I have to wonder whether 10.13.1 left some traces on my P7P after its first detection and thus regardless of my clearing app data and reinstall, it just refuses to work again. Maybe it's like the Magisk.db file where it has to be deleted to trigger super user permission ask again? And normal uninstall won't delete it? Thx
[Google Pixel 7 Pro] Homeboy76:
Are you using Google's stock firmware for the Pixel 7 Pro?
[Google Pixel 7 Pro] Homeboy76:
https://xdaforums.com/t/guide-root-...der-pass-safetynet-more.4505353/post-88387529

Thank you. :)
[Google Pixel 7 Pro] supermansaga:
I have to. Not smart enough to try anything else
[Google Pixel 7 Pro] Homeboy76:
What version of Magisk do you have installed?

Have you ever hid the Magisk app?

What Magisk Modules do you have installed?
[Google Pixel 7 Pro] supermansaga:
I had upgraded to Magisk 26001 after someone here said it's safe to upgrade. Yes I have hid it. I only have the usual ones installed. What's left out of this screenshot is only Clash for Magisk which was not turned on.
[Google Pixel 7 Pro] Homeboy76:
Please be patient, I know I am asking a lot of questions. Why? Your answers to these questions will determine my suggestion to pass Safety net for all your apps.

Do you have a Pixel 6 Pro or Pixel 7 Pro?

You have a Pixel 6 Pro module enabled.

When you say you hid Magisk that should mean the Magisk app has another name. Right?
[Google Pixel 7 Pro] supermansaga:
I have a pixel 7 pro, but that p6 module from senior member foobar66 here still works on pixel 7 pro for usage in China to enable local carrier 4g service for this phone that is not sold in China, not to mention Google is totally banned here.

Yes. Magisk is hidden with "setting" name. All other banking apps work fine with either the default Denylist enforced or Shamiko v0.7 whitelist approach. Many thanks for your dedication to my problem.
[Google Pixel 7 Pro] Homeboy76:
@supermansaga,​

I wonder if having Shamiko and the Deny list on is affecting the Marriot app.

Uninstall the Marriot app

Turn these Magisk modules off

Shamiko

Volte properties for Pixel 6 Pro

Zygisk LSPosed

Magisk Settings

These settings should be on

I know Magisk is hidden

The channel should be set to the Magisk (Beta/Canary/Stable) you are using.

Check Updates

Zygisk

Enforce DenyList

(Optional) Scroll down to Superuser and enable

Enable Biometric Authentication

.

Reboot

Reinstall the Marriot app

Then

Tap

Configure DenyList

=> Tap 3 Dot Menu => Check ✓

Show system apps

=> Check ✓ Google Play Store, Google Pay, Google Wallet, Marriott app, etc.

Get Device Certified Clear Google Play Store, Google Play Services, Google Pay, Google Wallet, etc. [/B]

Turn Airplane mode on

Open Settings

Tap Apps & notifications

Tap see all...

Tap three dot menu

Tap Show system

Scroll down to Google Play Store

Tap Storage & Cache

Tap Clear storage

Note:

Repeat the 3 steps above

for Google Play Services, Google Pay, Google Wallet, Marriott app, etc.

reboot

Turn Airplane mode off

Check Device Certification, It may take 24 hours for Device Certification

Open Google Play Store app

Tap Menu - Circle top right

Tap Settings

Tap About

Check Play protect certification.

If this works you'll enable/turn on the

Volte properties for Pixel 6 Pro

module and see if it breaks anything.

Is the Zygisk LSPosed module needed for the Volte module to work?
[Google Pixel 7 Pro] supermansaga:
Thanks. The Zygisk LSPosed module is not needed for the Volte module to work. Assuming this should work, I am afraid there are other XPosed modules apps that I have to keep using and therefore I would have to keep the Zygisk LSPosed module on. I am aware of Applist Detector app saying those Xposed Modules could be an issue because they can't seem to be hidden, such as GPS Setter, WeXposed, Hide My Applist. The Magisk App also has z.wh.wlwqb.haq detected.
[Google Pixel 7 Pro] Homeboy76:
Just Curious

What is detecting Magisks z.wh.wlwqb.haq, and the other modules after Magisk is hidden and SafetyNet is installed?
[Google Pixel 7 Pro] supermansaga:
GitHub - Dr-TSNG/ApplistDetector: A library to detect suspicious apps like Magisk

A library to detect suspicious apps like Magisk. Contribute to Dr-TSNG/ApplistDetector development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] simplepinoi177:
Do yo need to use the latest Marriot version?

If all root hiding methods worked on previous versions, can you not use an older version and not update -- as a workaround until you figure out how to successfully hide root on the newest version and/or Zygisk DenyList/Shamiko/Delta/whatever other root-hiding method updates to be successful on Marriot?

I do recall 3 or 4 months ago seeing how Marriot app was one of them apps that was
[Google Pixel 7 Pro] cmh714:
10.12 IS worrking fine on QPR3.....Salamat for the suggestion to downgrade!
[Google Pixel 7 Pro] supermansaga:
It would be good to know the exact changes in each Marriott version from 10.12.0 to 10.13.1, but nothing can be gained from the simple release notes. I am also using 10.12.0 for now.
[Google Pixel 7 Pro] Homeboy76:
Magisk Beta Update

Magisk-v26.1.apk

Magisk Canary Update

app-release_d0c93842-26101.apk

Notes:

Tap app-release.apk

Tap 3 dots (...) across from 10.x MB, Tap Download

Magisk Stable Update

Magisk-v26.1.apk
[Google Pixel 7 Pro] inpowers:
HI Guys have just read through this guide hoping to find an answer with no luck so here goes.

I have not updated my Pixel 7p since October as my phone has never asked for an update even though auto updater in on. Always shows your system is up to date. Do i need to update firmware for each month from november to April? OR just do an April update?

And what would be the best method to carry this out Android Flash tool or the Pixelflasher.

Thanks
[Google Pixel 7 Pro] lovesitgallery@gmail.com:
How to fix pro camera?
[Google Pixel 7 Pro] badabing2003:
Just the latest would do it.
[Google Pixel 7 Pro] inpowers:
Ok Thanks

Which method do you recommend Android flash tool or Pixelflasher?

Thanks again
[Google Pixel 7 Pro] JJT211:
You should update your instrcutions with the correct command for flashing boot image

fastboot flash init_boot magisk_patched-25200_Wt9vl.img
[Google Pixel 7 Pro] Homeboy76:
https://xdaforums.com/t/kernel-clea...k-vib-batterysvr-oct-24.4509793/post-87697599
[Google Pixel 7 Pro] T.A.R.D.I.S.:
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?
[Google Pixel 7 Pro] Slim2none4u:
You need to extract the init_boot.img not the boot.img.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
That was done.

testing this : fastboot flash init_boot_b magisk_patched-25200_T9evv.img

And that's pass!!
[Google Pixel 7 Pro] simplepinoi177:
try

fastboot flash init_boot magisk_patched-25200_T9evv.img
[Google Pixel 7 Pro] T.A.R.D.I.S.:
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.
[Google Pixel 7 Pro] badabing2003:
Your device is in bootloader mode?

What do you get when you issue this command"

fastboot getvar current-slot

What happens when you do

fastboot --set-active=other
fastboot reboot bootloader
fastboot getvar current-slot
[Google Pixel 7 Pro] Homeboy76:
:oops: Oops, T.A.R.D.I.S. is not asking a question. :rolleyes:
[Google Pixel 7 Pro] badabing2003:
Actually he did, cross posting is always messy.

He also said

Hence why I wanted to know why he can't change slots, it does not make sense.
[Google Pixel 7 Pro] T.A.R.D.I.S.:
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!
[Google Pixel 7 Pro] badabing2003:
Thank you for posting your solution.

I'm still curious in learning why / how you were blocked, as that should not have happened.
[Google Pixel 7 Pro] renzgy:
Hello, i tried this step patching init_bot.img through magisk app but during patch in magisk its give me error patching failed. Im updated in November build which is 13.0.0 (TD1A.221105.001, Nov 2022).

anyone here who root the device with pixel 7 pro which November update?

UPDATE: @Homeboy76 It's working with magisk canary because of these steps I managed to changed my SKU of my Japan version using the instructions of @HarryShan in converting device.
[Google Pixel 7 Pro] foamerman:
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.

​
[Google Pixel 7 Pro] Homeboy76:
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.