[CLOSED][Guide] Root Pixel 4 XL Android 10 (Q)

[Homeboy76]

i tried to flash the patched boot.img and i get back

fastboot unknown option -- slot

i literally copied and pasted your cmd prompt command from the original post what am i doing wrong

when i type fastboot flash boot--all with the boot.img file location i get this

target reported max download size of 268435456 bytes
sending 'boot--all' (32144 KB)...
OKAY [ 0.198s]
writing 'boot--all'...
FAILED (remote: Not allowed to flash (boot--all))
finished. total time: 0.352s

no matter how i type the command i get the same thing
FAILED (remote: Not allowed to flash (boot ?)
? ---- meaning what ever way i type it

there is a space between -- and slot
fastboot unknown option -- slot
should be :
fastboot flash boot --slot all magisk_patched.img

This command is just wrong: when i type
fastboot flash boot--all
with the boot.img file location...

It might help if you open a Command prompt (#1) in the Platform-tools folder (#4).

 

[mattwheat]

I didn't try it like that. I was merely following exactly what the O. P. played out as the method to do so. Then when that didn't work I tried all different way of entering the command. I did not try it with the file path before the partition to be flashed to. That's generally not the order fastboot commands are entered.

Is that what worked for you?

---------- Post added at 11:03 AM ---------- Previous post was at 10:58 AM ----------

there is a space between -- and slot
fastboot unknown option -- slot
should be :
fastboot flash boot --slot all magisk_patched.img

This command is just wrong: when i type
fastboot flash boot--all
with the boot.img file location...

It might help if you open a Command prompt (#1) in the Platform-tools folder (#4).

I've tried it with powershell from the platform tools folder I've also got fastboot and adb setup system wide to be able to just type cmd in windows task tray search bar or by using the keyboard shortcut to open cmd promtp and initially I copied and pasted the O.P. 's command that he lays out. Figured he was driving this bus so I would just follow the drivers instructions. But it didn't work. That's why I went to trying every variation i could think of.
And I know that fastboot recognizes my device due to the fastboot devices cmd returning the id. So with that said it shouldn't matter where I run cmd prompt from due to it being system wide and verified by fastboot returning the id. It never has been an issue before. As long as you're telling fastboot the file address to pull from.


What I was merely trying to explain is no matter what spaces I insert or don't insert, whether it's typed 100% correct or not it returns the same error. Regardless.
From both powershell opened in the platform tools folder or not. And with cmd prompt opened from the tools folder or not. With adb and fastboot setup system wide on my windows 10 PC.

 

[Homeboy76]

...That's generally not the order fastboot commands are entered.

Is that what worked for you?

---------- Post added at 11:03 AM ---------- Previous post was at 10:58 AM ----------

...What I was merely trying to explain is no matter what spaces I insert or don't insert, whether it's typed 100% correct or not it returns the same error. Regardless.
From both powershell opened in the platform tools folder or not. And with cmd prompt opened from the tools folder or not. With adb and fastboot setup system wide on my windows 10 PC.

fastboot flash boot --slot all magisk_patched.img
Yes.

I understand you are trying to explain what is not working. Here is the problem I'm having with your explanation of the problem:
a. several people have used this guide succesfully to root their phone following the OP.
b. You didn't try the Moderators suggestion.

So, that makes me wonder what is different about your phone or PC that is causing you problems.

This error is the key to the problem:
FAILED (remote: Not allowed to flash (boot ?)
Hmmm, is # 3. A. applicable?

So, if your phone is still not rooted:
- calm down
- stop blaming everything but you as the reason you cannot root your phone. Blame will not root your phone.
- reread the instructions from start to the Index, then read #1 and the other numbers that are applicable to what you are trying to do. Don't forget to read all the notes associated with each number (set of instructions).
- Try again.

 

[mattwheat]

I haven't tried it with the "=" in the command line. I'll try that ....

---------- Post added at 07:21 AM ---------- Previous post was at 07:14 AM ----------

fastboot flash boot --slot all magisk_patched.img
Yes.

I understand you are trying to explain what is not working. Here is the problem I'm having with your explanation of the problem:
a. several people have used this guide succesfully to root their phone following the OP.
b. You didn't try the Moderators suggestion.

So, that makes me wonder what is different about your phone or PC that is causing you problems.

This error is the key to the problem:
FAILED (remote: Not allowed to flash (boot ?)
Hmmm, is # 3. A. applicable?

So, if your phone is still not rooted:
- calm down
- stop blaming everything but you as the reason you cannot root your phone. Blame will not root your phone.
- reread the instructions from start to the Index, then read #1 and the other numbers that are applicable to what you are trying to do. Don't forget to read all the notes associated with each number (set of instructions).
- Try again.

Trust me I'm calm. And I'm not necessarily blaming everything but me. As youll see from some of me questions to you guys I've asked "what am I doing wrong". "what am I missing". That's all. And I'll be sure to go back through it very thoroughly. Trust me I'm not wanting to have these issues. I would love nothing more than to never had missed whatever it is I'm missing so I could already have root and have my phone mirrored to my GMC head unit in my truck. Not a big fan of Android autos style. The UI has gotten better. But thanks ill look over the stuff and try again. I do appreciate everyone's help.
And by the way who is the moderator?

 

[Homeboy76]

I haven't tried it with the "=" in the command line. I'll try that ....

---------- Post added at 07:21 AM ---------- Previous post was at 07:14 AM ----------



Trust me I'm calm. And I'm not necessarily blaming everything but me. As youll see from some of me questions to you guys I've asked "what am I doing wrong". "what am I missing". That's all. And I'll be sure to go back through it very thoroughly. Trust me I'm not wanting to have these issues. I would love nothing more than to never had missed whatever it is I'm missing so I could already have root and have my phone mirrored to my GMC head unit in my truck. Not a big fan of Android autos style. The UI has gotten better. But thanks ill look over the stuff and try again. I do appreciate everyone's help.
And by the way who is the moderator?

Great!
Is your SDK platform-tools r29.0.6?
The Forum Moderater is Badger50. The suggestion to use the '=' in the command line was his suggestion.

 

[mattwheat]

@Badger50
Great!
Is your SDK platform-tools r29.0.6?
The Forum Moderater is Badger50. The suggestion to use the '=' in the command line was his suggestion.

no its r29.0.5

im at a loss

 

[mattwheat]

heres everything i just tried

 

[mattwheat]

ok i downloaded platform tools r29.0.6 and tried again still the same thing

theres something very weird going on with this bootloader is unlocked i set all the seting in magisk per the OP instructions followed everything to a "T"

 

[mattwheat]

notice how when powershell returns the error it always puts a space between the "--" and "slot" notice how i type it without the space

 

[Badger50]

notice how when powershell returns the error it always puts a space between the "--" and "slot" notice how i type it without the space

Try using command prompt instead of Powershell. Pay close attention to step #2 in the link :good:

https://android.gadgethacks.com/how-to/open-adb-fastboot-command-window-platform-tools-0195269/

 

[mattwheat]

If by #2 you're referring to the fastboot devices command? Check the screen shot. I did that. Like I've said before I've don't all these steps from the cmd prompt and from powershell. I'm aware of how to open cmd prompt and change the directory by using "cd" and like I've said before I set up adb and fastboot system wide so I can fastboot from any folder. Been setting it up for years like that as well as I did it the way the instructions say to do it by dropping the patches boot img into the platform tools folder and open powershell or cmd from inside that folder with the fastboot.exe in it. I'm willing to try anything y'all can think up to throw at it. But I'm not real optimistic at this point. I've tried different USB cables. I tried watching CNN while doing it instead of FOX. Hell I tried holding my mouth a different way. But nothing. I can see any time now I'm gonna get one of those artistic images in the cmd window that's made up of strategically placed letters, numbers, and symbols that create a design and it's gonna be a big middle finger pointing right at me with an 80's style computer digitized voice laughing like Vincent price. Lmfao

 

[Badger50]

If by #2 you're referring to the fastboot devices command? Check the screen shot. I did that. Like I've said before I've don't all these steps from the cmd prompt and from powershell.

My apologies. I certainly was not trying to impugn your knowledge base or technique. I simply missed the SS for the CMD is all. I really don't know what the problem could be since both of the commands that have been discussed, work for myself and others. I suppose the work around would be to fastboot the boot.img, switch slots, then fastboot it again. However, I'm sure that won't mitigate your frustration as to why it doesn't work. I do like the "Vincent Price" retaliation technique though! ?

 

[mattwheat]

My apologies. I certainly was not trying to impugn your knowledge base or technique. I simply missed the SS for the CMD is all. I really don't know what the problem could be since both of the commands that have been discussed, work for myself and others. I suppose the work around would be to fastboot the boot.img, switch slots, then fastboot it again. However, I'm sure that won't mitigate your frustration as to why it doesn't work. I do like the "Vincent Price" retaliation technique though! ?

No need to apologize I was just merely explaining I'm not a noob at this. But hey I mess up and miss stuff just like any body can. That's why I've been reaching out to yall. Trusting that I'm pretty sure yall are a little more seasoned than I. I did a lot back with the nexus 7 2013 and razor hd and hd Maxx. And some galaxies around the s3 thru s5 days. And nexus 6 and 6p. Then had a family and didn't do anything more really than just root for viper and LMT launcher. But now LMT launcher works without root. But Android 10 basically has it built in with the gestures so kinda been out of the loop. But ive noticed the way the system and boot partitions are designed now is vastly different than the old days of odexed and deodexed Roms. And CyanogenMod. It's now gone a little above my pay grade if you will. But I think that's a good idea to try flashing the stock boot.img and start over. But for what it's worth do you think the stock boot will flash of cmd is returning the errors as unknown command errors and not something describing wrong partition size or invalid signature or anything really that would relay that it has the right paths just wrong format or size or something? Seems like the errors are really more like user errors. Meaning I'm typing it wrong it would seem but clearly, or from what I can see, I'm typing it correct. Hell I even copied and pasted the commands from y'all's advice y'all left in the replies I got.

 

[mattwheat]

My apologies. I certainly was not trying to impugn your knowledge base or technique. I simply missed the SS for the CMD is all. I really don't know what the problem could be since both of the commands that have been discussed, work for myself and others. I suppose the work around would be to fastboot the boot.img, switch slots, then fastboot it again. However, I'm sure that won't mitigate your frustration as to why it doesn't work. I do like the "Vincent Price" retaliation technique though!

done!!!!!!!!!!!! thank god thank you sir thank you very much that worked

 

[Badger50]

done!!!!!!!!!!!! thank god thank you sir thank you very much that worked

NOICE! "I love it when a plan comes together!"???

 

[Homeboy76]

done!!!!!!!!!!!! thank god thank you sir thank you very much that worked

@mattwheat
Woke up and saw what I had missed. lol
Glad you got it rooted

I was wondering why all your images were blue and not black like the Command Window.

Curious:
What worked for you, so other XDA members can benefit from it:
- Opening a Command prompt?
- Switching slots?
- What, exactly, did you do to resolve the problem?

 

[Homeboy76]

Try using command prompt instead of Powershell. Pay close attention to step #2 in the link :good:

https://android.gadgethacks.com/how-to/open-adb-fastboot-command-window-platform-tools-0195269/

You snooze you lose, I was inspecting the inside of my eyelids lol.
Woke up and saw what I had missed.
Ok, another way of doing #1. A. Option 2, Note: 1

 

[Badger50]

You snooze you lose, I was inspecting the inside of my eyelids lol. Woke up and saw what I had missed.
Ok, another way of doing #1. A. Option 2, Note: 1

Nothing wrong with a little eyelid inspection from time to time my friend?? if you think it's useful, add it to your excellent guide for more options.
Under option 2
Subset 2...code 1, 1A....and how the heck did I get here!?

 

[Homeboy76]

Nothing wrong with a little eyelid inspection from time to time my friend?? if you think it's useful, add it to your excellent guide for more options.
Under option 2
Subset 2...code 1, 1A....and how the heck did I get here!?

Don't know how you got there ROFLMAO.
Thanks but no thanks #1. A. Option 2, Note: 1. is all that's needed.

 

[Badger50]

Don't know how you got there ROFLMAO.
Thanks but no thanks #1. A. Option 2, Note: 1. is all that's needed.

Hahahahahaha....fair enough my friend! ???