Nope, lol.
Really wish people who open up Github issues would provide logs, but that's a rant for another day
How To Guide [Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More
- Thread starter Homeboy76
- Start date
Really wish people who open up Github issues would provide logs, but that's a rant for another day
Do OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,
5. Root/Reroot with Magisk and Pass SafetyNet.,
• Pass Safety Net with SafetyNet Fix
use Displax's safetynet-fix v2.3.1-MOD_2.1.zip file.
right, got to work by just flashing safetynet & clearing cache on Google Play Store.
I chose direct install in magisk app and now have a bootloop. Phone boots up and it looks like home screen will show up but then it reboots. Don't know what to do and don't want to lose data.
Tried flashing stock boot.img & init_boot but still not booting.
Can access bootloader but not recovery (neither from bootloader nor through adb).
Any help?
Last edited:
This is the first time I've heard of direct installing Magisk bootlooping/failing. Thanks for the feedback.
I hope the following fixes the bootlooping.
Do OP (Post 1), 2. Install/Update Factory Image keep data, wipe data,...
• Important Note(s):
4. If you phone bootloops
@innit, Did you flash the init_boot.img to boot slots?
fastboot flash init_boot --slot all init_boot.img
Last edited:
Already did that and it didn't work. Could I just reflash factory image with Pixel Flasher & tick "Keep data"? Would that be enough to get it to boot?
I thought flashing the init_boot.img to both slots was an easiest: OP (Post 186)
Maybe @badabing2003 or @Lughnasadh has a better solution to fixing Direct installing Magisk failing.
Last edited:
fastboot flash boot --slot all init_boot.img causes boot failure (in bootloader Enter reason: boot failure)
I used these commands:
fastboot flash boot boot.img --slot all
fastboot flash init_boot init_boot.img --slot all
But it just keeps bootlooping.
I can`t contact badabing2003 (user restricts who can view his profile).
You can't contact me?
I don't have any restrictions, and others do manage to contact me, in any case if there is an issue with the board, use
@ to mention me.None of the commands you used are correct.
The correct way to use the flags (options) is to specify before the command.
usage: fastboot [OPTION...] COMMAND...Example:
fastboot --slot all flash init_boot init_boot.img
I used commands from this thread https://forum.xda-developers.com/t/...nlock-bootloader-pass-safetynet-more.4505353/
Will try the one you posted.
No I couldn't. When I clicked your name a warning poped up saying the user restricts who can view his profile or something similar.
I could be wrong, but I thought the command to flash the init_boot.img is:
fastboot flash init_boot --slot all init_boot.img. The fastboot command structure I used came from fastboot • man page
Am I wrong or do both commands achieve the same results?
Last edited:
I edited my post because according to the fastboot • man page the partition is required.
fastboot flash init_boot --slot all init_boot.img.
Yeah, I knew what you were getting at (I think, lol) so didn't mention the init_boot missing, but probably should have.
Both of theses should work:
fastboot --slot all flash init_boot init_boot.img
or
fastboot flash --slot all init_boot init_boot.img
I usually do the latter when flashing images/partitions, but it shouldn't matter either way, at least in my experience.
Last edited:
Top Liked Posts
-
There are no posts matching your filters.
-
4
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.3
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.3KernelSU 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...
github.com
Just another way to root or use both Magisk/KernelSU.3SDK 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://forum.xda-developers.com/t/...der-pass-safetynet-more.4505353/post-88261723 -
28[Guide] Root Pixel 7 Pro with Magisk + Unlock Bootloader + Pass SafetyNet + More
Android Security Bulletin—March 2023
Pixel Update Bulletin—March 2023
Introduction
This Guide is for Pixel 7 Pro owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
- Disclaimer
- Prerequisites
- Update(s)
- NEW
- My Other Guides
- Credits/Thanks/Recognitions
(The Instructions listed below are not steps, they are individual sets of instructions.)
- Unlock Bootloader/Return Phone to Stock/Lock Bootloader
- Install/Update Factory Image keep data, wipe data, or use @badabing2003 PixelFlashers
- Take the OTA Update and Maintain Root
- Extract the flash-all.bat and the init_boot.img files from the Factory Image.
- Root/Reroot with Magisk and Pass SafetyNet.
- Set Magisk App Update Channel/Update Magisk
- Install/Update Magisk Modules
- Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
- Test fastboot
- ADB Sideload
- Custom ROMs
- Themes, Apps, and Mods
- T.W.R.P. Backup/Restore
6
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.
If it is the former, then I don't want to waste my time, if it is the latter, perhaps modding is not for you.
I'm not asking those for my benefit, I'm asking them so that I provide you precise commands and instructions to get this to work.
Just because you downloaded a specific version of the SDK does not make it that it is being used.
How many times I have to ask you the provide the output of thewherecommands
You say everything is in C:\Platform-Tools directory, yet your screenshot shows that you are not operating in C:\Platform-Tools directory.
If your need my further assistance, please find a way to supply the information asked of you in this post.
Apologies if this sounds a bit harsh, put yourself in my shoes.5
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...
github.com
4
I would add to it that doing it to both slots assures that the inactive slot does not have anything non stock on it.4Update SafetyNet Net Fix Mod
https://forum.xda-developers.com/t/...al-safetynet-fix-2-3-1.4217823/post-87198517/
Displax's SafetyNet Fix Mod: v2.3.1-MOD_2.1
• Update module.prop - Disclaimer
