yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Homeboy76:
@andrew2432,

You can root one slot and leave the other unrooted on your Google pixel 7 phone by following the instructions in the OP, post #1,

~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,

4. (NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.

Notes:

a. Download the OTA image for the Pixel 7 (panther).

b. sideload the Pixel 7 (panther) OTA.
[Google Pixel 7 Pro] supermansaga:
If I am already on September with bootloader locked, and I want to experiment with this 2 slots approach, I guess that means I need to unlock and wipe my phone one more time, but then after all the dusts settle, do I essentially have to install apps 2 times for each slot? Or are they sharing the same apps, incl Intune Company Portal and work profile? If sharing the same apps, would I be able to really use company portal without any problem when boot from unroot? If no problem, I guess I would like to have the cake and eat it too, even if it means I need to reboot each and every time to tap the other slot.
[Google Pixel 7 Pro] Homeboy76:
AFAIK, the slots are " sharing the same apps".

I'm assuming that would "Incl Intune Company Portal and work profile".

You can not " boot from unroot" or "reboot each and every time to tap the other slot". Presently, you need a

computer

with

Platform-tools

to switch slots.
[Google Pixel 7 Pro] supermansaga:
Thanks. Using platform tools won't be that bad, right? Happy to explore it, if there is a proven walkthrough. I can try to "pause work apps" whenever I want to switch the slots. Thanks
[Google Pixel 7 Pro] Homeboy76:
<<Edit>>

See post #664 and 666.
[Google Pixel 7 Pro] Lughnasadh:
Just as a reminder, the "2 slot approach" is not really meant to allow you to switch to your unrooted slot and then have apps work properly because that slot is unrooted. The problem here is that in most instances with an unlocked bootloader you won't be able to pass Play Integrity API checks without doing more, such as rooting and then using Displax's USNF mod or Chiteroman's Play Integrity Fix mod. Thus, even on a slot that is unrooted, you will still fail the Play Integrity API checks because your bootloader is unlocked and "most" apps in question (e.g. apps that check the security of your device such as checking if you are rooted) need to pass this in order to work properly. There are, however, some apps that check if you are rooted, but don't check if you are passing Play Integrity or if your bootloader is unlocked. In these limited circumstances the "2 slot approach" would be helpful.

Also, with the "2 slot approach", you would be able to switch from the rooted slot to the unrooted slot without a computer, but not vice versa. To switch from the unrooted slot back to the rooted slot you would need a computer.

But in general, It's more of a fail safe in case something goes wrong with one slot you know the other slot is bootable because this method makes both slots bootable.

And both slots share /data partition, so you will have the same apps and app data on both slots.
[Google Pixel 7 Pro] gpvecchi:
Is it possible to switch slot within the phone? I mean, without connecting it to a pc.
[Google Pixel 7 Pro] Lughnasadh:
If you are on a rooted slot you can switch using the app below. As stated above, if you are on an unrooted slot you need to use a PC since this app requires root.

https://xdaforums.com/t/dev-boot-control.4598515/
[Google Pixel 7 Pro] Homeboy76:
I totally forgot about the app Boot Control, thanks for the the reminder.
[Google Pixel 7 Pro] Homeboy76:
Thanks for the detailed explanation, you are appreciated.
[Google Pixel 7 Pro] supermansaga:
many thanks. One more dumb question. How can I quickly check if both of my current 2 slots are even bootable? Obviously one is already bootable. But I have no idea about the other. I forgot if I had flash both the last time.
[Google Pixel 7 Pro] Lughnasadh:
You can use the app I mentioned above. Or if you sideloaded the OTA onto your current slot then just sideload it again and both slots will be bootable.
[Google Pixel 7 Pro] REM_8:
My Pixel 7 pro passed safety net fine until today.. when it failed. I didn't change anything.. I use Magisk 26.3 with Zygisk and Universal safteynet fix and magiskhide , everything worked smoothly until today. could it be the updated google play services or something that fails the test? did it happen to anyone else? btw Shamiko as an alternative to deny list didn't help..
[Google Pixel 7 Pro] otonieru:
Use play integrity fix instead of safetynetfix.
[Google Pixel 7 Pro] REM_8:
Hi @otonieru thanks for the replay, unfortunately, that did not help .. is it a known issue with the pixel 7 pro? or just me?
[Google Pixel 7 Pro] REM_8:
btw using play integrity fix v8.6 didn't work as well
[Google Pixel 7 Pro] otonieru:
How about turning off your MagiskHide ?, it's not necessary to use it just to hide root. I only use Play Integrity Fix & Shamiko on my P7P,

and as i also use lsposed, i install HMA and iamnotadeveloper module as well

my YASNAC pass both integrity & cts
[Google Pixel 7 Pro] REM_8:
Thanks so much for sharing your way of hiding root! :) I followed your advice and still, it didn't work :( I have no idea what caused it... yesterday it worked fine.. anyhow I'll wait for updates on the safetynet spoofing modules and try again...
[Google Pixel 7 Pro] otonieru:
Did you clear your play services data yet ?

sometimes, it as simple as that
[Google Pixel 7 Pro] REM_8:
Yeah I did turn on airplane mode and clear data from google play store/ services / wallet and all that.. and rebooted the device but no change...
[Google Pixel 7 Pro] rester555:
I have had this issue before with magisk and another version. The only way that solved it for me was a total wipe.
[Google Pixel 7 Pro] REM_8:
Thanks for the tip, that would be the last option.. I don't want to do that currently..
[Google Pixel 7 Pro] REM_8:
will uninstalling the official Magisk and installing Magisk Alpha could help solve the safety net problem?

what would you guys recommend? (other than wipe) because it seems nothing works for me...
[Google Pixel 7 Pro] Homeboy76:
I don't think so, most safety net problems on the Pixel 7 Pro are resolved with Displax's v2.4.0-MOD_1.3.
[Google Pixel 7 Pro] REM_8:
so I have managed to pass the basic integrity

I did try play integrity fix with shamiko this doesn't work anymore, and tried integrity+universal that didn't work. so currently the CTS seems to be the only problem .

From what I understand in the past magisk-hide-props-config was supposed to fix CTS , but it is not supported. would anyone recommend installing magiskhidepropsconfig?

Any ideas on how to pass CTS ?

Thanks in advance to anyone who can help :)
[Google Pixel 7 Pro] chaos193:
I managed to get all my banking apps to work for me, even the latest version of company intune portal including teams and outlook. Here's how I got it working for me at least.

Started from scratch and removed all magisk modules, then uninstalled the magisk stable.

Installed the latest magisk alpha apk using the normal method. Patch my init.boot using pixelflasher and reflashed the latest factory image to obtain root, which is the October android 14 update.

Hide magisk alpha under a different name, Installed Play Integrity fix 8.7 module and shamiko for magisk alpha 0.7.3 (183) module. Reboot.

After all these steps, all work apps and most of my banking apps open as usual, with no force close or root detected.

I got the remaining two of my banking apps not working after all that, which were RHB mobile banking and TnG eWallet.

Then I installed LSPosed, download hidemyapplist. Enable in LSPOSED, Reboot. Open the app, go to template manage, create a blacklist template and add all my root apps to the list. (Adaway, applist detector, classic power menu, disable FLAG_SECURE, hide my applist, magisk alpha, TwiFucker). Then go back and go to App manage and select the apps you want to hide root from. (In my case RHB mobile banking and TnG eWallet).

Reboot and all my apps now work properly.

Additional notes; for some reason which I can't pinpoint, Installing AOSPMods or Pixelify modules breaks the previous two apps even after I hide them in HMA so I'm not using them at the moment. I think the best way to do is to start installing and see which module breaks the app and don't use them for the time being. Hope this helps.
[Google Pixel 7 Pro] Homeboy76:
I'm passing CTS with Displax's v2.4.0-MOD_1.3.

Try disabling/removing all your mods but Displax's v2.4.0-MOD_1.3. Then check CTS, if it passes install your other mods: enable/install

a module

check CTS until you find the module that is causing CTS to fail.
[Google Pixel 7 Pro] REM_8:
Well.... We have a winner!!!! its @chaos193 !!! thanks so very much for sharing all the steps! :)

I followed your advice and passed all safety checks including CTS !!

The play integrity fix V9 failed all checks and only V8.7 works...

Thank you @Homeboy76 for helping as well, unfortunately, Displax's v2.4.0-MOD_1.3 doesn't work on my device for some reason... even when removing AOSP and all modules...
[Google Pixel 7 Pro] V0latyle:
You need to stop depending on SafetyNet checks. Check your Play Integrity responses instead. See this thread:

[INFO] Play Integrity API - replacement for SafetyNet

THIS IS NOT A SUPPORT THREAD. For questions and support regarding how to fix your Play Integrity verdicts, see the Play Integrity Fix thread. ⚠️BEFORE YOU ASK A QUESTION, READ THIS POST AND THE FAQ!⚠️ ****Update 12/11/23**** Google has been...

xdaforums.com
[Google Pixel 7 Pro] supermansaga:
May I come back here and ask if folks who have been rooting have issues upgrading to October A14 release? The other thread has a couple reporting they got stuck at the monocolored Google logo if they root. Stable is fine. Thanks

Please see Post https://xdaforums.com/t/october-4-2...7-pro-cheetah-safetynet.4502805/post-89088032
[Google Pixel 7 Pro] justDave:
This was my report https://xdaforums.com/t/pixelflashe...-support-thread.4505287/page-55#post-89083541.

No issues at all. I still have root and banking apps etc still work like they did with Android 13.

I just made sure all apps, Magisk and LSposed modules were up to date before I updated. I don't bother unhiding or disabling Magisk and haven't been bitten yet.
[Google Pixel 7 Pro] andrew2432:
I got basic but not the deep stuff on my pixel 7 not pro, panther model

Using @chaos193 method
[Google Pixel 7 Pro] Homeboy76:
That is all you are going to get, Google patched the strong_integrity bug.
[Google Pixel 7 Pro] supermansaga:
Thanks. I also used pixel flasher 5.8.0.3 and flashed my folks' p7p and achieved success, though at one point, the G logo seemed stuck
[Google Pixel 7 Pro] Hitman478™:
I'm on pixel panther too, unable to pass integrity check, A14, what have you done exactly?
[Google Pixel 7 Pro] andrew2432:
I'm still on 13. All I did was uninstall what I had, install steps in chaos post and got that result
[Google Pixel 7 Pro] Hitman478™:
Indeed, i had everything works on A13, problems are now on A14 o_O
[Google Pixel 7 Pro] Morgrain:
My P8 Pro also fails simple integrity check on A14, installed the module, did all the hiding with Zygisk via Magisk, deleted the app data in Gapps, nothing worked.

It seems that we need a new update for the module.
[Google Pixel 7 Pro] Lughnasadh:
Which version of the module did you install? Displax's mod 1.3 should be working. Chiteroman's 9.2 works as well, I think.
[Google Pixel 7 Pro] Jesus David Otero:
Hello, does someone have rooted pixel 7 pro with android 14?

I can't install, whe I execute the fastboot boot boot.img comand, my device restart and magisk manager says that magisk isn't installed, some HELP?
[Google Pixel 7 Pro] Josh:
You must execute init boot but look for a threads on xda where you can see detailed information for root.
[Google Pixel 7 Pro] badabing2003:
Last I checked,

fastboot boot did not work on newer devices

you need to fastboot flash init_boot init_boot.img
[Google Pixel 7 Pro] NCVol:
Have you considered using Pixel Flasher? It worked great for me. Just make sure you use platform tools version 33.0.3 instead of the most recent one.
[Google Pixel 7 Pro] badabing2003:
Unless he's on a Mac in which case he should use 34.0.4
[Google Pixel 7 Pro] NCVol:
Good point. Thanks for clarifying.
[Google Pixel 7 Pro] Homeboy76:
If you are, manually, flashing the factory image, extract the init_boot.img, patch it with the Magisk app, and flash it with this command:fastboot flash init_boot magisk_patched...img to root.
[Google Pixel 7 Pro] Homeboy76:
@Jesus David Otero

Detailed information "for root" is in the OP of this thread:

~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~ ...,

6. Root/Reroot with Magisk and Pass SafetyNet.,

•

Patching the init_boot.img

- to root/reroot.,

2. Patch the

init_boot.img

file

•

Factory Image - Extract and Patch the init_boot.img

file

•

OTA Image - Patch the init_boot.img

file

3. Copy/Move... through 8. Type..
[Google Pixel 7 Pro] mac796:
Ok need help pixel 7 pro. I updated to Android 14 had kershika kernel , powerhint, and safety net fix kdragon2.4 1.3. Aosp mods, Lsposed 1.9.2. everything worked great for about a week. Then I got the bright idea. I wanted to try viper again. I found the one that works for everyone 0.5.0 and the module. Installed it. It all worked. Then, I decided to try that shamika , along with the safety net fix. And it all work great too for a couple days. Today whenever I do a restart I'd lose root. I throw back on the computer and Fastboot root again. That would work for a little bit. Now I can't keep root no matter what I do. Most the time magisk shows it's rooted and zygisk okay and all that. I even dirty flashed the factory image again. And uninstalled magisk and all my modules. Still root will not stick. So am I where I got to do a factory reset? I'm running magisk canary too. I even tried to repatching a new download of the init boot image from the factory image. ? Thank you

Edit. I'm using platform tools. 34.0.4. Did I read somewhere i shouldn't be using that one. I should be using an older version.
[Google Pixel 7 Pro] Homeboy76:
I assuming you are using Kirisakura_Raviantah kernel and Displax's 240 Mod 1-3 safety net fix.

a. Check for more than one Magisk app installed on your phone:

If you hid the Magisk manager app the default name for the hidden Magisk app is settings. If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager:

Open the TB Checker app

Tap Run Xposed check

Scroll down to Magisk Random Package Name: to see Magisk's hidden name.

You can also use TB Checker to check if you have more than one Magisk Manager app installed.

b. You should copy your post and post it on the viper 0.5.0 thread where viper is working for everyone on Android 14. The XDA members on that thread would have the best solutions to your problem.
[Google Pixel 7 Pro] mac796:
Solved

Yes I was using using Kirisakura_Raviantah kernel and Displax's 240 Mod 1-3 safety net fix. I ran the xposed check I believe there's only one app installed. I usually don't name it. I just leave it named settings when I hide it. Right now I don't have it hidden because I don't really have root. Once I hide it, I can't go back into it without reinstalling magisk in fastboot. Not sure what happened but this sucks. Thanks for the help.

Edit I just tried to flash the stock init boot to both slots. Still no go. I'm going to try a dirty flash with the pixel flasher this time and see if that does any different. At least I'll have flashed both slots. I went back to the 33.0.3 platform tools to.

Edit. Okay I flashed both slots again with stock and same thing it just won't hold root it won't stick. I'm guessing something's corrupted. I remember there used to be a module that completely uninstalled Magisk and everything it saved. Is there a fast boot command or something like there is for removing modules? It's very strange. Magisk says it's rooted. But No root app can gain root access. Except for call recorder.

LAST EDIT: ok I'm not sure what happened and why. But my systemless hosts built in AdAway caused all kinds of problems I ended up removing it and AdAway and root sticks again. What a deal. I eventually reinstalled AdAway later. It was the only module I never removed because I never have had problems with it before. Lesson learned.
[Google Pixel 7 Pro] missionman:
I'm a little late here..Can anyone give me some advice?

I'm on Pixel 7 Pro, bootloader unlocked, Rooted, LSPosed 1.8.6 (6.7.12) Zygisk installed, Magisk 26.1 installed and I'm on Android 13.

My phone keeps promoting me to install Android 14. What will happen if I install it? Will it lock my bootloader? Lose root? etc?

It prompts me like once or twice a week and I just swipe backspace to silence it.

Just wondering...

Thank you all.
[Google Pixel 7 Pro] Homeboy76:
a. It will not lock your bootloader.​

b. You will lose root.​

c. You can turn off Automatic system updates and it should stop prompting you to update: Settings => System=> Developer options => Automatic system updates​

d. I'm assuming you have you reasons for not wanting to upgrade LSPosed Zygisk 192 and Magisk 26.3​

e. Last but not least you can update to Android 14 and keep your data (See OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,

3. (NEW) Manually Install/update the OTA image keep data and root/re-root your phone)

IMPORTANT:

Disable all modules (Magisk) before you patch the init_boot.img with the updated Magisk 26.3 app

.
​
[Google Pixel 7 Pro] missionman:
Thanks for this. IF I then installed Android 14, is Android 14 rootable on Pixel 7 Pro?

The reason also behind this is I'm trying desperately to fix this ongoing NO SERVICE/No Sim issue in my phone.

I disabled my eSIM and don't remember how to enable it again (network signal guru, network switcher). Can't remember for the life of me how I disabled the eSIM.

Anyways, I'm going to try the eSIM and Android 14 which I doubt will fix it since it seems to be modem related. I loved this phone and now I'm willing to lose root just to get the thing to keep service. It is beyond annoying and getting worse. I just replaced a new burned out visible sim card with another new one and now this sim is failing (the one I'm using now).

By the way I've tried everything you could possibly suggest except eSIM and Android 14.

Toggling off 2G, Adaptive Network, Wifi Calling, Disable NR, Disable private DNS, nothing works.

Right now I'm just trying to figure out how to re enable my eSIM.
[Google Pixel 7 Pro] State.of.mind:
P7P on A14. I am trying to root my device, but I don't understand the purpose of making both slots bootable? What will happen if I root as normal (patch the init_bootimg and then flash it)?
[Google Pixel 7 Pro] Josh:
Nothing will happen,you can flash just bootable slot as I flashed myself
[Google Pixel 7 Pro] Lughnasadh:
Two main purposes to sideloading the Full OTA twice, in my mind:

1. To make both slots bootable in case you run into trouble. When you flash the factory image, the inactive slot will be unbootable (without doing more such as flashing the factory image to that slot). Sideloading the Full OTA twice will make both slots bootable.

2. To have one slot rooted and one slot unrooted. For example, when you are on a rooted slot and want to use a banking app, etc., that may not work with root, you can switch to the unrooted slot (via Boot Control) without the need of a PC, etc., to switch slots.

However, there is a caveat. since you need to be rooted to switch slots without a PC, you cannot switch from an unrooted slot back to a rooted slot without a PC.
[Google Pixel 7 Pro] Homeboy76:
Yes, Android 14 is rootable, if your phone has an unlockable bootloader.

Your carrier should have some instructions for enabling your esim.
[Google Pixel 7 Pro] missionman:
I disabled my esim myself somehow using network signal guru or something but I cannot figure out how to re-enable it. I disabled it and 5G right after I rooted many months ago.

If anyone knows the enabling back eSIM on Pixel 7 Pro please let me know.
[Google Pixel 7 Pro] supermansaga:
There is a way to reset using network guru app. Separately there is also a way to reset network settings on Android 14. Worst case scenario, you also need to call customer service of the carrier
[Google Pixel 7 Pro] supermansaga:
It would be great if you can confirm this two boot approach totally works with intune company portal as discussed at https://xdaforums.com/t/tutorial-ro...-update-q3-2023.4402273/page-27#post-89105629. I am not sure if everybody is fine again. I haven't been willing to go back to root, fearing the amount of time that would get it going again.
[Google Pixel 7 Pro] Lughnasadh:
I'm not actually using the "Sideload OTA Twice" method, so I can't test. Sorry...
[Google Pixel 7 Pro] missionman:
I'm not seeing any network reset option in network guru app. I been trying to figure out how I disabled it for days and hours and I just can't remember.
[Google Pixel 7 Pro] Homeboy76:
Magisk Canary Update

Magisk (0352ea2c) (26302).

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

Diffs to v26.3

[MagiskBoot] Don't pad zeros if signed boot image is larger

[MagiskPolicy] Fix genfscon and filename_trans

[MagiskPolicy] Fix bug in libsepol

[Zygisk] Fix and simplify file descriptor sanitization logic

[App] Prevent OOM when patching AP tarfiles

[App] Fix bug in device configuration detection

[Daemon] Fix certificate parsing of APKs

[General] Fix logging errors from C++ code being ignored

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] tbv2005:
Hi, maybe I missed something, just got my P7P back from Google after a motherboard error and resetup. Installed Magisk (stable version), hide it, on deny list added the apps from OP, installed displax mod 2.4.0_Mod_1.3. Safety net is passing fine, no problem, but when installing my banking app (Barclays), adding it to deny list (completely, so all ticked) it's still detecting root. I'm not sure if I had a additional modul in Magisk before my motherboard died, but banking was working before. Any hint appreciated

EDIT: I'm also not a 100% sure if I had more apps on the deny list, then in OP before the motherboard died
[Google Pixel 7 Pro] Homeboy76:
Did you clear the cache of all the apps you put in the deny list?
[Google Pixel 7 Pro] tbv2005:
Thanks but yes, didn't even open barclays before adding to deny lsit, and yes, tried uninstalling, clearring cache etc several times.....

All other "root detecting apss" are working up to now, just not barclays
[Google Pixel 7 Pro] DracoPiece:
anyone tried rooting android 14?
[Google Pixel 7 Pro] Dragon1212:
I just rooted my Pixel about 10 min ago, instructions work perfectly. Haven't been able to pass Safetynet/integrity though.
[Google Pixel 7 Pro] Dragon1212:
Yea I just flashed the canary, have zygisk enabled, systemless host enabled, Play protect, store, wallet in full deny, The safety fix from the first post, ver 2.4.0 mod_2.0 installed and running.

Cleared storage from the above with airplane mode, but no dice. Always doesn't pass play protect certification

Edit: Got it working, used version 1.3 instead and it worked
[Google Pixel 7 Pro] DracoPiece:
have you managed to make Pixelify work? planning to go use android 14 now instead of evolution
[Google Pixel 7 Pro] Dragon1212:
I didnt even know about this module lol. I will give it a shot tomorrow and will let you know. But for now, work comes at six :P