yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Homeboy76:
"Every time that I flash the patched magisk init_boot file my phone boot loops."

Please answer these two questions:

Did you use SDK Platform-tools r.33.0.3 to patch the init_boot.img?

Did you follow the instructions in

this threads OP (post #1)

to patch and flash the init_boot.img?

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

5. Root/Reroot with

Magisk

and Pass SafetyNet.

Patching the init_boot.img

- to root/reroot.

If your phone was previously rooted,

DO NOT

repeat

DO NOT

install another Magisk Manager app. Do this before you

patch the init_boot image

:

Open the Magisk Manager app and disable all Magisk modules. 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.

Extract the

init_boot.img

file from the

Factory Image

.

Download the latest Factory image to your phone.

Extract the Factory Image file (cheetah-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.

Open the folder you extracted the Factory image to and extract the Image file (image-cheetah-aa9a.999999.999.zip).

The, stock, init_boot.img file should be in this folder

.

Install Magisk Canary - Download app-release.apk

or

Magisk Beta/Stable App

Open Magisk Beta/Canary/Stable App

The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.

Tap Install (next to Magisk)

Tap, Select and

Patch a File

Select the

init_boot.img

file you extracted from the latest factory image.

Tap the ✓ (Check Mark)

Tap Let's Go

When you see done, the init_boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.

Reboot

Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:

Copy it to a USB drive and transfer it to your computer.

Move it to your computer using adb push

Boot fastboot mode

Connect the phone to the Computer with USB cord.

Open a Command Prompt in the folder you copied the patched boot.img to.

Type fastboot flash init_boot magic_patched....img at the Prompt and press enter.

Type fastboot reboot at the Prompt and press enter.

Important, if your phone boot loops try one of the following options:

Flash the 'stock' init_boot.img to both slots: fastboot flash init_boot --slot all init_boot.img

Remove Modules

Press the Power button until the phone turns off.

Press the Power and Volume Down to boot the bootloader.

Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules

fastboot Reboot.

Important, if the Magisk Manager app has the

Superuser

and

Module

buttons greyed out:

Read @badabing2003 post
[Google Pixel 7 Pro] Jamims88:
I'm using platform tools r34.04-windows and I unfortunately deleted my magisk app and reinstalled it after I kept having boot loop issues even though I was previously rooted.
[Google Pixel 7 Pro] Slim2none4u:
I believe your issue is your android sdk.

Use 33.0.3 https://xdaforums.com/t/guide-root-pixel-xl-android-11-r.3964112/post-88261787
[Google Pixel 7 Pro] Homeboy76:
Are you still having problems boot looping when you patch and flash the init_boot.img?

fastboot flash init_boot magisk_patched...img

If yes, follow @Slim2none4u advice to use SDK platform-tools r.33.0.3 (post# 552) and the ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~... (post# 550), to patch and flash the init_boot.img.
[Google Pixel 7 Pro] Lughnasadh:
Sounds like you may have a Magisk mod in need of an update that is causing your bootloop after flashing the patched init_boot.img. Did you have mods installed and if so did you disable them before flashing the patched init_boot.img?

If you do still have mods installed, then when bootlooping after you flash the patched image, go into safe mode and then reboot and that should disable your Magisk mods. Alternatively, to remove the mods:

adb wait-for-device shell magisk --remove-modules

Also, I've used the current version of Platform Tools 34.0.4 several times on both this device and on a Pixel 6 Pro to root (and flash the factory image via flash-all, without wiping) with no problems so I don't think the Platform Tools version is your problem. But of course, stranger things have happened...
[Google Pixel 7 Pro] Jamims88:
yes
[Google Pixel 7 Pro] Jamims88:
/system/bin/sh: magisk: inaccessible or not found. I disable my mods before but I entered this code in the cmd and got this message.
[Google Pixel 7 Pro] Homeboy76:
Thanks, for testing SDK Platform-tools r.34.0.4.
[Google Pixel 7 Pro] Lughnasadh:
No problem! Just be aware that there still may be a bug with it being able to wipe. I've seen a couple of reports where they used it (not sure which version of 34.0.4 they used as there have been at least two) but it didn't wipe even though they left the -w intact. Of course, other bugs may exist that I'm not aware of as I've only used it to flash the factory image (via flash-all) and to flash patched images to root.
[Google Pixel 7 Pro] Homeboy76:
What code did you enter?
[Google Pixel 7 Pro] Lughnasadh:
If you don't have any mods enabled, then make sure you are patching the init_boot.img that corresponds to your current build. May also want to try Pixel Flasher to root. I'm assuming you are not getting any errors after flashing the patched init_boot.img?
[Google Pixel 7 Pro] Jamims88:
I'm getting no errors after I flash and the patched init_boot.img corresponds to my current build. My phone makes it to the Google logo and loops after that.
[Google Pixel 7 Pro] Jamims88:
adb wait-for-device shell magisk --remove-modules
[Google Pixel 7 Pro] Lughnasadh:
Can also try different cables, ports and using command prompt if you aren't. As I suggested earlier, also try Pixel Flasher. If you still have problems after that you can provide a support.zip in the Pixel Flasher thread. That will give a lot of information to about your setup, errors, etc., that can be used to diagnose.
[Google Pixel 7 Pro] Lughnasadh:
You stated earlier that you disabled you mods beforehand though? Are you sure you disabled all mods before flashing the patched init_boot.img?
[Google Pixel 7 Pro] Homeboy76:
I want to make sure the Platform-tools you you downloaded from here that was Last updated 2023-08-16 UTC is the same SDK Platform-tools I am using. Please verify the SHA256 for the following:

platform-tools_r34.0.4-windows.zip

SHA256

520a453af1d0baf1939a80038a816cb8de40d000542b1a71bf60ba6fc80784d9

platform-tools_r34.0.4-linux.zip

SHA256

f2eee6e8220f3dfde6e1acc93c5b25d3d8bd215c0b03585b21665f1ea30d66ba

platform-tools_r34.0.4-darwin.zip

SHA256

c60d9ee0acade673b649543b2d53c632ba54f9ca083ed612176105117fa16102
[Google Pixel 7 Pro] Lughnasadh:
For Windows, same SHA256.
[Google Pixel 7 Pro] Homeboy76:
Please go to post #550 ~~~ Part II INSTRUCTIONS ~~~... Tap the

CLICK TO SHOW CONTENT

. Read and follow the instructions to patch and flash the init_boot.img

Note: If you use Platform-tools r.34.0.4-windows to flash the init_boot.img, make sure the

SHA256 verification

matches the SHA256 in post# 565.
[Google Pixel 7 Pro] Jamims88:
My module icon is greyed out on my magisk application. I used this command "adb wait-for-device shell magisk --remove-modules" after flashing the init_boot patched file and it stops the inital boot when it gets to the google logo screen, but after that it reboots continuing the loop.
[Google Pixel 7 Pro] Lughnasadh:
Your module icon is greyed out because you aren't rooted. I asked earlier if you are sure you disabled your mods before flashing the init_boot.img. Initially you said you did, but I asked again and you haven't answered. If you did, then you don't need to run any of those commands as your modules are already disabled.
[Google Pixel 7 Pro] Jamims88:
I apologize I thought I answered your question. I'm going to say no because I'm not 100% sure I disabled them all. When I initially tried to update my phone it was back in April so I don't recall. I've flashed the monthly updates and attempted to flash the init_boot patch each month.
[Google Pixel 7 Pro] Lughnasadh:
Okay, first try this after flashing the patched image and while bootlooping:

When booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode. Then reboot and modules should be disabled.

If that didn't work, then try this:

1. Turn off device

2. adb wait-for-device shell magisk --remove-modules in command prompt

3. Connect your phone to computer and turn it on.

4. Phone tries to boot and the command should be accepted

5. Wait until the command worked and the phone boots up without issues
[Google Pixel 7 Pro] Homeboy76:
<< Edited - Removed

barrier

creating reply. >>
[Google Pixel 7 Pro] Lughnasadh:
Okay, I'm out...
[Google Pixel 7 Pro] Homeboy76:
@Oswald Boelcke, Senior Moderator

I am truly sorry that @Lughnasadh might have been offended by my post# 571. He has made many insightful post not only in this thread but also in other threads. In hindsight I should have PM him. I am truly sorry for my post# 571.

My post# 571 was not intended to offend @Lughnasadh or lessen his valuable input to this guide.

My intention was to lessen the amount of instructions the member was receiving.

Why?

The member appeared to be confused as to which set of instruction he should follow to solve the boot looping problem he is having when he patched and flashed the init_boot.img.

I would have gladly dropped out and let @Lughnasadh continue to provide the member with instructions. Instead of having the member bounce back and forth trying to figure out which set of instructions would solve his boot looping problem.

@Lughnasadh, if I offended you in any way I apologize.
[Google Pixel 7 Pro] Slim2none4u:
I mean, it is your thread. Does that not carry any weight? Although classy to do so, your appology isn't required. Some should learn to stay in their lane.
[Google Pixel 7 Pro] Homeboy76:
UPDATE - Platform-tools r.34.0.4

You can use Platform-tools r.34.0.4 to

Dirty flash

the Google factory image. @Lughnasadh has tested it.

Multiple platform-tools_r34.0.4...zip were posted. You can verify you are using the correct revision of platform-tools_r34.0.4...zip by insuring the SHA256 matches the SHA256 below:

platform-tools_r34.0.4-windows.zip

SHA256

520a453af1d0baf1939a80038a816cb8de40d000542b1a71bf60ba6fc80784d9

platform-tools_r34.0.4-linux.zip

SHA256

f2eee6e8220f3dfde6e1acc93c5b25d3d8bd215c0b03585b21665f1ea30d66ba

platform-tools_r34.0.4-darwin.zip

SHA256

c60d9ee0acade673b649543b2d53c632ba54f9ca083ed612176105117fa16102
[Google Pixel 7 Pro] Homeboy76:
While it is true, I started the thread. It is not a matter of who carries the most weight or what lane someone is in.

XDA members are

human

and have

feelings

. That being said, it is imperative that communication be communicated clearly and without offense. An offensive response creates

barriers

, it does not

build bridges

. An

apology

, hopefully, tears down barriers and builds bridges. :)
[Google Pixel 7 Pro] Lughnasadh:
No worries
[Google Pixel 7 Pro] Homeboy76:
@Lughnasadh, thanks, your insight is always needed and appreciated.

That being said, would you please repost your reply to @Jamims88 post# 570 so he and other XDA Members can profit from it. :)

I edited my post# 571 reply.

I hope @Oswald Boelcke will edit post#571 by removing it or editing it: {Mod edit: Quoted post and

reply

was deleted on the authors and request. Oswald Boelcke, Senior Moderator}
[Google Pixel 7 Pro] Oswald Boelcke:
Gentlemen, my compliments how you solved this issue! That's the way it should be amongst reasonable adults. You've set a great example.

@Homeboy76 I can only act on request of or with permission by a post's author. If @Lughnasadh agrees I'm happy to reinstate his deleted post including its original content i.e. the reply to Jamims88. In turn I'd then set also post #571 to status quo ante.

Regards

Oswald Boelcke

Senior Moderator
[Google Pixel 7 Pro] simplepinoi177:
geez man....damn....thanks for calling me out on missing TWO WORDS "from Google" as it was rather late...guess it means i must never read every single word of every single post and I guess it means i'm just one of those "some people just can not read" all the time...was just trying to help...
[Google Pixel 7 Pro] Slim2none4u:
This isn't a chat room! Stay on topic!
[Google Pixel 7 Pro] jake.99x3:
Considering the post is on bootloader unlocking, I am seeing if anybody else has dealt with this issue... I'm also sure there are some members with the T-Mobile pixel who may be interested in this if it works out...
[Google Pixel 7 Pro] Slim2none4u:
People should be called out when they don't read. What "help" can you offer if you don't read? The help needed was already given.
[Google Pixel 7 Pro] Slim2none4u:
No your post is about maybe getting an unlocked bootloader from a sim unlock. This is a guide not a development forum on tmobile locked bootloader. Now grow up and stop arguing nonsense.
[Google Pixel 7 Pro] simplepinoi177:
It wasn't about not reading...it was a simple mistake of mis-reading due to it being late and simply overlooking two words. I guess you never make any simple mistakes like that.

And some help was already given; I was attempting to give

supplementary

help in terms of the benefits of running the Verizon image vs. the global one which wasn't discussed. Also, I was just making sure the person knew the difference between the two variants -- in case he might want to stop or reverse the transaction to switch to the variant from Google; albeit this is a simple mistake for bringing up on my part for missing the two words "from google".

I would hope that it would have been productive and just as helpful to point out if that was the case (if not to that person, then to any other user that might be reading here just to learn)....
[Google Pixel 7 Pro] cmh714:
I have a new Google unlocked phone, in order to Enable OEM Unlocking you need to have a connection to the internet or cell, otherwise it will remained greyed out.... GL!
[Google Pixel 7 Pro] Homeboy76:
I may have called you out for your mis-reading but I also thanked you for your contribution to the question.

All is forgiven: Your mis-reading, my reacting to it. Let's move on, or we all will be making the OT mistake. :ROFLMAO::ROFLMAO::ROFLMAO:
[Google Pixel 7 Pro] jake.99x3:
Yes and in order to follow the guide and unlock the bootloader you need to be SIM unlocked correct? Ironic you desire to reduce clutter from this thread yet you fill it with these nonsensical replies. Somebody woke up on the wrong side of the bed
[Google Pixel 7 Pro] Homeboy76:
Sims unlocking means you can change sim card/carriers. It does not mean you can unlock the bootloader

OEM unlock

your phone.
[Google Pixel 7 Pro] Homeboy76:
Nope! AFAIK, Most phones, if not all, that are bootloader unlockable are sold sims unlocked.
[Google Pixel 7 Pro] Homeboy76:
I think you're right he is trying to get his T-Mobile bootloader unlockable phone's bootloader unlocked. That is OT.
[Google Pixel 7 Pro] simplepinoi177:
I think in certain cases getting sim unlocked also means being able to unlock the bootloader as well...

I think there might be some misattributing going on here...jake.99x3 might be getting what is capable with AT&T mixed up with T-Mobile (and/or might be mistaken in thinking that AT&T policy applies to T-Mo...)

According to Superguy in the quoted post below...AT&T can have its bootloader unlocked once it is SIM unlocked...it may(probably) isn't that case for T-Mo...

In any case, according to Superguy, jake.99x3 would have to somehow get T-Mo to unlock it on their "server side"...not simply SIM unlock it...
[Google Pixel 7 Pro] Homeboy76:
@Superguy @jake.99x3

One of the Prerequisites of using this Guide is: A Pixel 7 Pro phone with an unlockable bootloader. See OP, ~ ~ ~ Part I - INFORMATION ~ ~ ~ 2. Prerequisites

If you do not have a Pixel 7 Pro with an unlockable bootloader the instructions, in this Guide, to root your Pixel 7 Pro will not work.

So, as @Slim2none4u stated, trying to use this Guide to get your bootloader unlocked is OT.

If you purchased you Pixel 7 Pro from these wireless carriers: AT&T or T-Mobile

The links below explain their policy to get your device/phone unlocked.

Note: Your device/phone must have an unlocked bootloader to root it.

AT&TUnlock your device Requirements

T-Mobile device unlock
[Google Pixel 7 Pro] AlphaTekk Epoch:
I just got mine delivered via FedEx from Spectrum and it came already on Android 13, it just updated to the most recent Security Update after setup.

Just wondering if unlock & root is still possible and which of all these steps I would need to follow?
[Google Pixel 7 Pro] Homeboy76:
It looks like OEM unlock is greyed out.

That usually means your bootloader is

not unlockable

. If your bootloader is

not unlockable

, you

cannot root your phone

.
[Google Pixel 7 Pro] cmh714:
Spectrum is on the Verizon network. Its possible its locked like a VZW phone. Just guessing....
[Google Pixel 7 Pro] AlphaTekk Epoch:
Ya, it's locked until I pay it off then, I guess, they give me an unlock code.

It's a nice, long 2 year contract but thx for the answers, I was hoping it'd still be an option
[Google Pixel 7 Pro] Homeboy76:
Before you pay it off, I would call the Carrier that you brought your phone from (Spectrum/Verizon) and ask them

will they unlock the bootloader

if you pay off the phone.

Why?

First, most (not all) carriers only do a Sim Card unlock. You can check their Unlock Policy via the links below.

Second, if you want to root your phone the

bootloader must be Unlocked

.

Spectrum Mobile Device Unlocking Policies

Verizon Device Unlocking Policies
[Google Pixel 7 Pro] Gruber008:
Is it alright if I use stable Magisk on my 7 Pro?

I mean, everything is working so I'm confused why's everyone suggesting to use canary version of Magisk.

If it's necessary to use canary, what's the easiest way to switch from stable to canary, do I need to re-flash init_boot?

Thanks in advance!
[Google Pixel 7 Pro] Lughnasadh:
If that's what he wants, I have no problem with it.
[Google Pixel 7 Pro] Oswald Boelcke:
Thanks a lot for the confirmation. Your post is back publicly visible in its original status.

@Homeboy76 I've removed my comment from post #572 (former #571).

Regards

Oswald Boelcke
[Google Pixel 7 Pro] Jamims88:
Your life saver! The first method worked perfectly. I entered safe mode while booting and when I restarted my phone the modules were disabled and I had root.
[Google Pixel 7 Pro] Jamims88:
Thanks a lot for your help!
[Google Pixel 7 Pro] theit8514:
Just tried following this guide on my new Pixel and couldn't get the Magisk patched file to boot. Using fastboot flash boot (from Section 5, Patching the init_boot.img, item 17) just brings me back to the fastboot prompt with a boot failure. Shouldn't this be init_boot?
[Google Pixel 7 Pro] Homeboy76:
Yes! :)
[Google Pixel 7 Pro] moichman:
hello,

i have a pixel 7 pro, of course. it was rooted some months ago and all was well. this relates to using the platform tools to manually root per the instructions on page 1, but i had used pixelflash to root it, and have been using it for updates. (i used the factory image and "keep data")

somewhere in the last couple of months, it 's "rooted" but it's not rooted. i noticed that some apps, like amaze, no longer access root. after trying several times to redo it with pixel flasher, i saw this forum and tried to root it, manually.

the image was patched and transferred to the laptop platform tools directory.

i reboot the 7 pro into fastboot mode

i run the following commands with the following results:

./fastboot flash init_boot ./magisk_patched_[random].img

Sending 'init_boot_a' (8192 KB) OKAY [ 0.332s]

Writing 'init_boot_a' OKAY [ 0.048s]

Finished. Total time: 0.403s

./fastboot reboot

Rebooting OKAY [ 0.000s]

Finished. Total time: 0.050s

so it looks good, but just like with pixelflash, when i reboot and checke the phone is still not rooted. somewhere in all this, i tried installing the factory image with the stock init_boot, without patching it (again, keeping data). it didn't help.

so...i don't know if this belongs on the pixelflasher forum or here, but i chose here since the command line didn't work, either. if you think this belongs there, i will take it there.

thanks!!
[Google Pixel 7 Pro] Homeboy76:
I'm assuming your device is booting, and you are using a Linux PC?

This is one command not two:

./fastboot flash init_boot ./magisk_patched_[random].img

[/ICODE]./fastboot flash init_boot magisk_patched_[random].img[/ICODE]

Note: there is a space between init_,boot and magisk.

Please, try the single command and post the results.
[Google Pixel 7 Pro] moichman:
hi and thanks for replying,

yeah, Debian laptop. the pixel is booting just fine. I also have the [shareduid] shell enabled in magisk. I have the 2 button module installed and it works...but I tried deleting it and tried to root again but it didn't take. I also used a root checker that said not rooted

I'm not sure why that got split into two lines, but it was a single comman with the space you mentioned d. maybe the paste split it because it was too long?

what's weird is that it was rooted for some months. nothing stands out that makes me wonder. I just noticed one day that apps with root access weren't acting like it.
[Google Pixel 7 Pro] simplepinoi177:
You know...your issue sounds a lot like this Magisk canary-build bug that was going around a few months back where Magisk and other root checkers would say device is rooted, and many apps would work initially, but once a command/aspect that requires root would be called, the app would crash or be unable to work as intended. It ended up being that Magisk was sort of half-patching the init_boot where it was enough to be detected as "successfully rooted" but actually didn't apply (maybe the su permissions [i'm probably speaking out of my 🐴, but you should know what I mean])...

So with all that in mind, what Magisk version have you been using to patch?
[Google Pixel 7 Pro] Homeboy76:
I'm curious to read your answer to @simplepinoi177 question. What version of magic are you using to patch the init_boot.img?

Then try the following on your phone:

Pull down

quick settings

tap the power icon, tap and hold

Power off

until you see

Boot Safe Mode

tap

ok

. Let Safe mode boot fully, then reboot.

Then use TB checker to check for duplicate Magisk Manager app installed:

Open the TB Checker app

Tap

Run Xposed check

Scroll down to

Magisk Random Package Name:

to see a

Magisk's Manager app name

. Delete that Magisk Manager app.

Then do this on your computer

Flash the 'stock' init_boot.img to both slots to remove root: ./fastboot flash init_boot boot.img --slot all

Then flash the Magisk patched image.

./fastboot flash init_boot magisk_patched_[random].img

Check if you have root.
[Google Pixel 7 Pro] moichman:
it's the stable version 26.1. also magisk is set to notify upgrades only from the stable channel

i will do this, but it will be tomorrow evening. i will still check the thread, though.

yesterday before i posted, after i flashed the factory image with stock init_boot.img with keep data, i uninstalled magisk, then reinstalled and reapplied the patched init_boot.img. what i *didn't* do, though, is go through the entire process from the beginning, first....i used the patched img that i had already on the laptop.

i will try the suggestions and if that doesn't work i will install factory with unpatched img, then i will grab the init_boot from the zip file and start over.

i know i keep adding little details to what i've done, so far. i try to be detailed, but everything doesn't always come to mind unless it's triggered.