yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] cavolo:
100% sure that I use the latest adb and fastboot.

[root@Raphael platform-tools]# fastboot getvar current-slot
getvar:current-slot FAILED (remote: GetVar Variable Not found)
finished. total time: 0.001s
[root@Raphael platform-tools]# fastboot getvar current-slot
Warning: Device A/B support is outdated. Bootloader update required.
getvar:current-slot FAILED (remote: GetVar Variable Not found)
finished. total time: 0.001s
[root@Raphael platform-tools]# fastboot getvar current-slot
getvar:current-slot FAILED (remote: GetVar Variable Not found)
finished. total time: 0.001s
[root@Raphael platform-tools]# fastboot getvar current-slot
getvar:current-slot FAILED (remote: GetVar Variable Not found)
finished. total time: 0.001s
[root@Raphael platform-tools]# fastboot getvar current-slot
current-slot: a
finished. total time: 0.001s

I've run it multiple times to be sure, and you can see that it doesn't work very well...

I'm re-downloading the latest OTA (because de full factory image doesn't want to be flashed) to re-apply it and I'll see, finger-crossed...
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Good luck bro. I'm going to see Star Wars....may the force be with you :good:
[Google Pixel 2 XL Guides, News, & Discussion] inffy:
Anyone know why the newest magisk beta patches the dtbo.img everytime after i root?

I Installed a custom kernel with the img files (patched the custom kernel boot img with magisk manager) and also flashed the custom kernel dtbo img. But after a reboot MagiskManager patches that dtbo.img and after reboot the phone keeps giving that "your phone has a internal error" message.

Is there a way to stop magisk doing that and is there a reason why it does it?
[Google Pixel 2 XL Guides, News, & Discussion] cavolo:
Re-applied the latest OTA but there no changes...
[Google Pixel 2 XL Guides, News, & Discussion] c0de_junkie:
Well I finally built up enough nerve to pull the trigger and flash a Kernel and Root the device... All went smooth and successful, thanks to the help from users in this forum.

So I just wanted to say thanks to everyone for the help and for putting up with my many noob questions, especially [MENTION=3730810]Badger50[/MENTION] and [MENTION=4670411]Az Biker[/MENTION] , thank you very much for your help because it is very much appreciated.
[Google Pixel 2 XL Guides, News, & Discussion] ilal2ielli:
Because that's how topjohnwu coded it.

It has already been removed in the most recent Magisk code, but the next version has yet to be officially published.

You can use unofficial Magisk builds to fix this.
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
Wait so if I just did fastboot flashing unlock, how do I unlock critical after? I accidently just did unlock but I wanted to unlock critical..
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Fastboot flashing unlock_critical
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
Alright I got that down but now I am having trouble with the fastboot boot twrp.img command, it says it is an unknown command. What did I do wrong? I typed the whole twrp image name by the way not just twrp.img
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Is the twrp image in your platform tools folder?
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
yea, and sometimes when I try again it just gets stuck at downloading boot.img..
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Holy crap! You are the 3rd person today that I've been trying to help out with the same issue. So, lets go down the checklist.

1. Are you on stock 8.1? If so, how did you get here.

2. You have the latest SDK and platform tools on your pc.

3. Evidently your bootloader is unlocked...good.

4. Have you tried a different cable?? Which I'm starting to think is the main culprit!!

So where are we at so far?
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
1. I am on stock 8.1 and I got it from an OTA update

2. I have the sdk and platform tools on my pc downloaded from this thread

3. Yep it's unlocked

4. when I try adb reboot bootloader my phone reboots into the bootloader fine so I dont think it's a cable issue
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
are you on 8.1.0_r2? id also try renaming the img to something easy like twrp.img and putting it in adb root directory then open a cmd window in the adb directory then just fastboot boot twrp.img

also not sure if it matters but i also did fastboot flashing unlock

also, i updated to the latest ota available bcuz originally i was getting my bootloader didnt match
[Google Pixel 2 XL Guides, News, & Discussion] cavolo:
In fact, I tried with an old laptop with usb 2.0 port and everything worked ¯\_(ツ)_/¯

And, as I said, the location of the img file doesn't matter as long as you know how to use a command prompt.
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
Well it seems like when I try fastboot flashing unlock nothing happens...so is it a fastboot problem? And do I need to install special drivers for my phone or something?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Dang, another OTA update. So, your active slot is B now. Which means, at least I think, your gonna need to set your active slot to B with a fastboot command that I don't know. If I were you, and I'm not, I'd wait for one of the masters to answer your question to hopefully fix this so you don't loose your data. The only thing I can suggest is to flash the factory image with the flash-all.bat script. Which will indeed wipe your phone. I've got to do some more studying into this matter myself.
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
Well the wiping the phone isn't a problem right now since I literally just unlocked the bootloader anyways haha, my phone has nothing on it anyways. So you want me to flash the factory image without taking away -w right? So it will wipe the device again?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
That's what I would do at this point. What the heck. That's what another guy did on another thread that fixed it for him :good:
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
Alright thanks ill let you know how it goes

---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------

Well another problem now is that I can't even flash a factory image....

this is the message it gives me when I type flash-all:

target didn't report max-download-size

sending 'bootloader' (36344 KB)...

FAILED (remote: unknown command)

finished. total time: -0.000s

rebooting into bootloader...

OKAY [ 0.005s]

finished. total time: 0.005s

target didn't report max-download-size

sending 'radio' (60428 KB)...

FAILED (remote: Requested download size is more than max allowed

)

finished. total time: -0.000s

rebooting into bootloader...

OKAY [ 0.005s]

finished. total time: 0.005s

extracting android-info.txt (0 MB)...

extracting boot.img (40 MB)...

target didn't report max-download-size

error: Failed to identify current slot.

Press any key to exit...
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
I have not unlocked or rooted my week old P2XL *yet*, still learning as I go. That said, in my voracious reading, I found this script and it looks like a powerful remedy for issues. In particular the ability to flash both slots *might* help solve these issues? I'll follow to see if and what this does if you choose to try it.

Deuces Bootloop-Recovery & Flashing Script
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Don't type the command, just double click the flash-all file that's in the platform tools folder. Along with all the other stuff of course.
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
when I double click it still gives me the same errors :/
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
At this point, I would try the deuces scrip that Pkt posted just a bit ago. He's a great RC and knows far more than I do :good:
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Thank you, but with this phone I'm at level zero again. :D I just scour the forums for info that might help me or others.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Same here my friend. I really hope that Nathan, osmosis, or one of the other heavy hitters can help with this. This is the 4th one of these I've seen after an OTA. Gotta be an answer somewhere! :svetius:
[Google Pixel 2 XL Guides, News, & Discussion] ManImCool:
Just bought a new Pixel 2 XL and am trying to root this thing. I updated to 8.1 via OTA. I've unlocked the bootloader (critical). Downloaded MagiskManager-v5.4.1 apk and installed. Within Magisk app, when I click on Install -> Patch Boot Image File, I get the following error:

"Target Magisk version doesn't support boot image file patching"

What did I do wrong? I feel like I'm missing something very simple. Thank you.
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
FFS not even the deuces script works.......it gives me the same errors when trying to flash the factory image myself.
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Have you tried to reboot the computer and then do not open any apps, just the term window and try again?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Welcome to the party pal. This is crazy, your the 5th one I've seen today with the same problem after an OTA!! Quick question, can either of you try flashing the stock boot.img. You'll have to extract it out of the zipped file you get with the factory image. The command is..fastboot flash boot boot.img

Let's see what happens :eek:
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
lol i kno it doesnt.. ive just seen weirder things happen is all.. i didnt kno u were usin a 3.0 port haha, that wouldve been my first suggestion lol.. ive had and others have had nothin but issues with 3.0 ports..

glad u got it goin tho
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
"error: Failed to identify current slot" is the error I get when I try this
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
How bout this. Type the code in the pic, except use b instead of a at the end. If that works, then try flashing the stock boot.img again. Please let me know what happens.
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
alright ill try that, I have another question tho....I have used the command fastboot flashing unlock_critical to unlock my bootloader and when I check the device info using fastboot oem device-info it tells me that my device is unlocked but the critical is not unlocked....why is this? When I try fastboot flashing unlock or fastboot flashing unlock_critical now they both give me errors saying that my bootloader is already unlocked.

edit: and trying that code you gave me outputted this error: 'error: Device does not support slots'
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
wat does it say on screen when ur in fastboot? also what does it say when you do fastboot getvar all

---------- Post added at 02:51 AM ---------- Previous post was at 02:50 AM ----------

do fastboot getvar all and post results
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I've seen that before from a few others. However, I don't have a good answer. The only possible thing I can think of is that your trying to issue commands to a partition that isn't active. Which is probably wrong, but that's all I can think of. These OTA's are just driving me crazy with this particular issue. Mainly because I can't figure out a solution because I'm not smart enough with all this stuff! :(
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
looks normal.. shows ur unlocked and using slot a
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Now I'm really confused. If he took the OTA like he stated, then I though he would be on slot B. Yet the log clearly shows A. But then why can't he and others get anything to flash with the proper fastboot commands or with the flash-all.bat script?? I'm just stumped :rolleyes:
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
This is just a partial copy of the commands in Duece's script (note I'm on linux so the bash commands will be different than the batch commands) but the fastboot commands are the same. I just note how it changes slots. Your idea of what slot is active might be these errors, and using the fastboot commands from this script might help. As a final resort, running this script, knowing it will reset and wipe the device, might be worth the effort and save the trial and error frustrations that some users are experiencing.

echo "Flashing Bootloader & Radio A&B"
fastboot flash bootloader_a bootloader*.img
fastboot reboot-bootloader
sleep 5
fastboot flash bootloader_b bootloader*.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio_a radio*.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio_b radio*.img
fastboot reboot-bootloader
sleep 5
clear
## Flashing All Others (Without Reboot)
fastboot --set-active=_a
clear
echo "Flashing Slot A"
fastboot flash abl abl.img
fastboot flash aes aes.img
fastboot flash boot boot.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dtbo dtbo.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash laf laf.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
clear
echo "Flashing System A"
fastboot flash system_a system.img
clear
fastboot flash tz tz.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
clear
##Flashing Slot B
fastboot --set-active=_b
clear
echo "Flashing System B"
fastboot flash system_b system_other.img
fastboot flash abl abl.img
fastboot flash aes aes.img
fastboot flash boot boot.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dtbo dtbo.img
fastboot flash hyp hyp.img
fastboot flash keymaster keymaster.img
fastboot flash laf laf.img
fastboot flash modem modem.img
fastboot flash pmic pmic.img
fastboot flash rpm rpm.img
fastboot flash tz tz.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
clear
fastboot --set-active=_a
clear
##choices-format-relocks
clear
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
That makes some sense to me. I just don't understand why taking an OTA or side loading an OTA would cause this problem. I think they will likely have to wipe everything, if they can, and then start with a stock factory image to get the system back to normal. I haven't taken an OTA in 4 years and have never had problems like these with factory images. Heck, they can't even get Deuces script to flash! Such a conundrum!
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
This sounds scary ????
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
I understand, and being a two slot storage noob, I have no idea yet. When I got my phone on Dec. 4, was on 8.0 and I tried for about 30 minutes to get it to update to 8.1, then as soon as the OTA was on the developer site, and being an CLI jockey, I flashed it. So no actual experience with this, just trying to troubleshoot what is wrong, which also helps me learn.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
We're on learning on this one my friend. We need a Master Jedi hacker type warrior to decipher this one! I just really want to know the why and how behind it all.
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
i dont think the slot matters.. twrp its just fastboot boot twrp.img to start, not technically flashing it until he flashes the zip in twrp..

i personally did fastboot flashing unlock.. then fastboot flashing unlock_critical.. i rebooted after each step

it should work.. only thing i can think of its not the phone lol.. maybe pc or his driver setup

i pulled drivers from android sdk

---------- Post added at 06:36 AM ---------- Previous post was at 06:30 AM ----------

i dont personally think its the phone... if theyre tryna use twrp they arent suppose to flash it off the bat

i had issues with ota on my vzw pixel.. it was my download that was messed up lol

i had issues with various drivers too even the platform ones on the developer page with the images lol

---------- Post added at 06:50 AM ---------- Previous post was at 06:36 AM ----------

do me a favor... type *adb --version* then *fastboot --version* and show me the output
[Google Pixel 2 XL Guides, News, & Discussion] StuartRothrock:
me too syndrome for me - had inconsistent results with most fastboot commands and no problems with adb commands. I did large push/pulls testing adb and no issues. Moving to a USB 2.0 port resolved my inconsistencies and fastboot commands were 100% proper. BTW - I didn't notice any issues with 8.0.

BTW - thank you nathan for the development and the community for the support.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
For all of those having issues with fastboot...

If you are using a Windows machine, can you check what driver is being used in Device Manager? I remember having certain issues because the driver being used was identified as "[something, something]-taimen" (sorry I can't remember the specific identification nor be able to reproduce the mislabel) when it should be identified as "ADB Bootloader Interface".

It may be a long shot, but it seems everyone on the issue is stumped and it might not hurt checking...At the very least, correcting this helped me get past comparable complications...
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
At this point, nothing is a long shot my friend. It's just really interesting that several folks are having the same problem after taking an OTA :rolleyes:
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
uhh.. adb doesnt show when its in fastboot mode, theyre different interfaces/protocols.. but yes, very possible its driver related.. i see on the script guys page he says to b sure to dl most recent fastboot drivers from oct.. but oct was known to have issues so they should be using the dec. drivers.. thats y i asked the guy earlier to tell me wat version hes on, no response tho

---------- Post added at 12:30 PM ---------- Previous post was at 12:29 PM ----------

how many? at least 1 confirmed it was ausb 3.0 port lol

i bet if i teamviewed into their computers id get it goin lol
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I have no doubt that you could get it going Hoss. Like I said earlier...we just needed a Jedi Master tech warrior to solve this problem :good:
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
lol ud b surprised at how many times ive helped ppl and turned out to be the first thing they shoulda looked at haha.. but who knows, theres always a chance the phones defective but so far doesnt sound like it to me..

when they figure it out they will probably be angry haha
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yea, I don't think all their phones are defective. Too many similarities between all the ones having problems. I have learned many lesson since my DINC days. I've bricked a few in my day as well. So now, my #1 rule is...Read..re read..and then read it again before I do anything to modify my devices. Especially now that all these devices ain't what you'd call CHEAP! :good:
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
last time i helped someone with similar issues i mustve told him it washis drivers for days and he kept insisting he knew what he was doin to the point i believed him.. team viewed into his pc, checked device manager and what ashock lol not recognized.. 2min later correct drivers installed and hes swearin up n down they were updated haha

or the ones that dont realize theyre on a usb 3.0 port until weeks later when they all a sudden "figured" it out haha
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Hahahahahaha...I hear ya my friend. I've definitely had a few...Oh Duh, you Dumb Arse, moments with this tech stuff. You make a good point though. Most all of them have said their drivers and SDK's are up to date, however, maybe not. Not to mention the USB cables. Hmmmm...definitely a plausible idea :good:
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
its usually the blatently obvious that is the solution
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
Yea I have noticed this, in Device Manager, my phone doesn't even show up until I plug it into my PC and then 'Portable Devices' will pop up and then my device will be recognized as 'Pixel 2 XL'. I don't know how to get it to recognize as 'ADB Bootloader Interface' (I have tried manually installing the latest usb drivers from google but it doesn't work...

---------- Post added at 08:18 AM ---------- Previous post was at 08:16 AM ----------

When I type adb --version:

Android Debug Bridge version 1.0.39

Version 27.0.0-4455170

When I type fastboot --version:

fastboot version 27.0.0-4455170

---------- Post added at 08:27 AM ---------- Previous post was at 08:18 AM ----------

Also, for the cable I am using the usb type c cord that was given to me with the pixel 2 xl box and plugged it straight into my laptop because I have a usb type c port there already, there shouldn't be a problem with this? Or maybe it is a problem.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I know Elliwigy will weigh in on this. However from what I've read, the adapter that comes with the device has had issues in this matter. Can't believe Google didn't include a decent cable with the device! I had problems with it myself, until I used my USB-A to USB-C cable that came with my 6p. Then all was well. How to get the device to be recognized properly by your pc is outa my league. Although I'm sure the tech smart guys will be able to help. There ya go Elliwigy! :good::good:
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
yoooooo changing usb cords worked yessss!!! I switched to a usb-a to usb-c cable like you and it woooorrrrrkkksss
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Glad to hear it. Elliwigy was right :good::good:
[Google Pixel 2 XL Guides, News, & Discussion] Ap3xGam3r:
I have one more question, I have went ahead and flashed elementalx and magisk with no problems, but when I try to wipe dalvik and cache from twrp it says /cache not found.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Meh...nothing to worry about. Cache is not recognized anymore on this device due to ART taking it's place. If you want to do a good cache wipe. Go into TWRP, select wipe, then advanced wipe and select ART/dalvik. :good:
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
lol use a usb male a to c cable
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Did you get the Verizon variant or the Non-verizon?
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
i think i kno how to allow vzw unlocks.. just need a way to write to the partition
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Oh dude...if you figure that one out, your gonna make some greenbacks, and BIG RED is gonna be pissed! Bwahahahahaha :laugh::laugh:
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
all im here to do is piss off verizon haha
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
of course i also have more data but i am pretty sure thats where irs stored lol
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You apparently have many Chainfire Jedi Master hacker like skills master Obiwan! :laugh:
[Google Pixel 2 XL Guides, News, & Discussion] DaveMar:
I followed you closely in the Sammy S8/+ threads where you achieved root for those devices... Very tough thing to do- good. Now been seeing you in the P2xl threads! I love my google phone with it's unlocked bootloader, but to break open Verizon would sure make people happy dance! You're a great developer and know your stuff, if anyone can pull this off it's you!