yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] CPngN:
Why is everyone so hung up on this script? it's just a script. A dangerous script, as it does not pause to give the user a chance to examine each run. All it does is this, and you're better off running these commands 1 at a time manually:

fastboot flash bootloader bootloader-taimen-tmz12bb.img

fastboot reboot-bootloader

fastboot flash radio radio-taimen-g8998-00164-1710262031.img

fastboot reboot-bootloader

fastboot update image-taimen-opm1.171019.021.zip

(Example for flash-all.sh from March update for Pixel 2 XL)

Sorry, not trying to attack anyone, but people seem to be hung up on this script as if it were hundreds of lines long and full of checks and balances, and it's not. It's beyond basic, to a fault. The "sleep 5" that is in between commands would better replaced by a pause/wait-for-user-to-hit-enter command to make sure you can validate there were no errors before rebooting.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Sorry if I'm missing something here, but are you saying that typing in the five commands above individually, is easier that typing; flash-all <enter>
[Google Pixel 2 XL Guides, News, & Discussion] tarroyo:
Is the rooting with magisk method still working on the march update? I'm a lil iffy with installing twrp as its still in beta.
[Google Pixel 2 XL Guides, News, & Discussion] pa.pn2:
Yes it works flawlessly
[Google Pixel 2 XL Guides, News, & Discussion] greyhd:
The new twrp works great with the march update, no need to delete your password anymore.
[Google Pixel 2 XL Guides, News, & Discussion] tarroyo:
Thank you, Was looking thru guides and see some users getting stuck on the google boot screen after flashing the patched img thats why I asked.
[Google Pixel 2 XL Guides, News, & Discussion] steviewunderr:
Stuck on "G"

Hey guys, some weird stuff going on lately with my device. I was mid-road trip whenever my phone randomly shut off and would not power back on beyond the "Android is starting..." screen. I had recently updated a bunch of google apps, and figured any issues were from these apps being meant for 8.1 and me still being on 8.0. So, I flashed a new factory image, but I'm on a Mac and had the boot.sig not found error when executing the flash_all.sh script (I also removed the -w and other bits in the script that cause an outright failure when flashed). I then went manually into the "image-taimen-opm1.171019.021" folder and fastboot flashed all .img files since the script would only flash radio and bootloader. I went back to fastboot and booted twrp, flashed the installer, flashed Magisk 16.0 and the device booted perfectly. I used it for a few days until just a few hours ago. I went to sleep and when I got up to get water, I saw the device just stuck on the white "G" screen. I have no idea when it rebooted to this state, but I tried all the previous steps that solved my last booting issue and have had no success this time. Anybody please help! Thanks in advance :)
[Google Pixel 2 XL Guides, News, & Discussion] stumpy352:
Not sure why you're quoting my post to say this. I was trying to put him on the right track to flash everything manually. I never suggested any script except for Google's own flash-all. Unfortunately, I haven't had the chance to go this process myself on taimen, which is why I suggested in an earlier post that someone else might chime in with a full list of commands.
[Google Pixel 2 XL Guides, News, & Discussion] ilal2ielli:
Nothing should fail to flash when using flash-all unless you don't have the critical partition unlocked.

Did you run both unlock commands when you unlocked the bootloader?
[Google Pixel 2 XL Guides, News, & Discussion] steviewunderr:
Yes, I have my bootloader entirely unlocked. I'm not sure what the underlying issue was, but I used my functioning twrp to do a factory reset and then just went through the same steps to root etc. It's working now, so that's good!! Also, it seems to be a common issue when trying to run the script on Mac, I remember seeing on Google that this happened to many others. Thank you for the reply though!
[Google Pixel 2 XL Guides, News, & Discussion] CPngN:
Yes, again sorry, I wasn't going after you directly, it just made me realize that a lot of people quote that script as if it were big and complicated, and it's just 3 individual flash commands in a row with some reboots, pauses, and comments. It would be nice if folks would just post those inline with their other instructions so the user could watch each one and verify that it didn't fail before rebooting bootloader and moving on. Not likely to matter when things are done right and there's no corruption or glitches, but it helps to be a little cautious and avoid making things worse! Anyway, thanks for helping, carry on! :)

---------- Post added at 07:56 AM ---------- Previous post was at 07:32 AM ----------

From what I recall reading, that is mainly because people do not set their adb up to be executable from anywhere. The recommended method to get the latest install probably does not update your PATH to add a path to adb and fastboot. Since the script just calls "fastboot" but does not have the full path (/usr/local/bin/fastboot usually), it will fail unless you make the hacky move of copying your files to the adb folder and running it from there. You'll see people also have to modify the commands to add "./" in front to tell it to run from the current directory. All of this is solved by a proper installation where /usr/local/bin is added to your PATH. For most folks, they are using the 'bash' shell, and can fix this in FUTURE sessions by adding this to ~/.bashrc:

export PATH='$PATH:/usr/local/bin/:~/bin'

(That will also add your own personal bin folder to your path - a good place to put your custom scripts if you ever have any, and harmless if you don't.)

You can also run that directly on the command line to fix the current session.

If you put your adb and fastboot somewhere "strange", you can find them again the brute-force way by scanning the drive:

find / -type f -name "fastboot*" -ls

The files in /usr/local/bin/ are often links to a longer, uglier install base. If you use homebrew on the Mac to install adb (brew install android-platform-tools), they link like this:

/usr/local/bin/fastboot -> /usr/local/Caskroom/android-platform-tools/27.0.1/platform-tools/fastboot
[Google Pixel 2 XL Guides, News, & Discussion] jrbxx7:
Lolol yes the script from the manufacturer is very dangerous... Running it on every update has ruined my phone. The log shows everything as it runs including errors...
[Google Pixel 2 XL Guides, News, & Discussion] ryknow27:
This may be a stupid question but I am on Verizon and I saw that Best Buy has Verizon Pixel 2 XLs that are unlocked and can be used on any carrier. If I buy one from there would I be able to unlock the bootloader as stated in the OP or can you only unlock the bootloader on ones from the Google store? :confused:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
For use on any carrier is not the same as unlockable bootloader IIRC.

You want to get the Google version, which is good for any carrier,and has the unlocked bootloader.
[Google Pixel 2 XL Guides, News, & Discussion] sirxdroid:
If you care about unlocking the bootloader, do NOT buy the Verizon version.
[Google Pixel 2 XL Guides, News, & Discussion] ryknow27:
Thank you both for the info!:good:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I'm assuming you used the command...fastboot boot twrpxxxxxx.img. If so, then check to make sure your SDK platform-tools is up to date, maybe try a different USB cable and port, and you do have the twrp.img in your platform-tools folder correct?

---------- Post added at 03:22 PM ---------- Previous post was at 03:20 PM ----------

Also, I'm assuming that the toolkit unlocked the _critical partition as well. You can check by running...fastboot getvar all.... to check the status of your bootloader and slot your on.
[Google Pixel 2 XL Guides, News, & Discussion] 93fuelslut:
Dude thank you for the info on the fast boot command getvar. I didn't know that. I just deleted the twrp img file and redownloaded it. That solved it, or me using an older twrp img
[Google Pixel 2 XL Guides, News, & Discussion] 93fuelslut:
So I entered the command, but I don't know what to look for. I don't see anything about unlocked critical or anything
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Your unlocked. However, if you want to make sure, run the command...fastboot flashing unlock_critical.......be advised, if the toolkit didn't perform this, it WILL wipe your phone!! If it was performed by the toolkit, you'll just get a message that says already unlocked. Tough choice I know :eek:
[Google Pixel 2 XL Guides, News, & Discussion] 93fuelslut:
Yeah it wiped everything. But I just didn't know how to read all that to see if I was unlocked or critical unlocked. But all seems to be well since I just flashed nitrogen. Thanks again
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Cool beans man. Glad everything is working ??
[Google Pixel 2 XL Guides, News, & Discussion] BIGWORM:
Oi! Don't say that!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
No doubt! That's just wrong! ????
[Google Pixel 2 XL Guides, News, & Discussion] 93fuelslut:
When you reboot your phone and the message says your vendor doesn't match, does that actually hinder your service and anyway
[Google Pixel 2 XL Guides, News, & Discussion] BIGWORM:
No.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
It's super easy to fix.

Just unzip the factory image, then unzip the second zip and copy the vendor.img file to your sdcard, boot into TWRP and flash that bad boy to the Vendor partition and reboot... no more message.

It's happened to me on the last two DU updates, so now I just leave the vendor image in my "to be flashed" folder on my sdcard. Just remember that the vendor must come from the same month the OS or cust Rom your flashing does (ie: the latest DU is MARCH security, so I used the MARCH vendor from the factory image file)
[Google Pixel 2 XL Guides, News, & Discussion] Wartickler:
Having rooted and flashed many devices over the years I've been through many types of root management tools. Magisk seems to be yet another new flavor of root management. If I don't care about passing SafetyNet must I go through the hoops of Magisk or are there simpler root management schemes? Do any of the old tools work on 2XL? Searching doesn't seem to lead me anywhere but Magisk.
[Google Pixel 2 XL Guides, News, & Discussion] galaxys:
Magisk is it for now. It takes some getting used to, but works a treat!
[Google Pixel 2 XL Guides, News, & Discussion] BIGWORM:
Yep. I was adamant on staying on SuperSU for the longest, but finally took the plunge back in March or so of last year, and it's pretty great. I like that a majority of the mod zips I was using can be flashed systemlessly, including Xposed, which is crazy. Do note that flashing the Xposed Magisk module will have you fail safetynet, though. I'm running a bunch currently (excluding Xposed), and I'm passing just fine. Finally tried Google Pay for the first time earlier.
[Google Pixel 2 XL Guides, News, & Discussion] myk.robinson:
Morning, folks. I feel somewhat like an idiot for asking this but would like some opinions.

I am far from new to the custom ROM/rooting/flashing scene, however, I am somewhat cautious due to what this phone cost me.... I bought a Pixel 2 XL yesterday from my local Verizon. My previous phone was a Moto G4 Plus, which was rooted and running a custom 8.1 ROM (AICP). The experience on the Pixel 2 is for the most part the same, a nice stock Android experience with a few bells and whistles. That said, I am happy with the stock ROM but being a bit of a tinkerer, am looking at this thread...

I would like to root the phone for the sole purpose of installing AdAway. So risk versus rewards?

To make sure I understand, I just need to unlock the bootloader using the instructions in the original post, then flash the factory image, then install Magisk Manager apk, then install AdAway and be done?

Seems pretty simple compared to some other root processes I've done in the past, so I suppose I just want to make sure that dyslexia didn't jumble the instructions before I start.

Thanks for entertaining the question.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
If it's a Verizon variant phone, then unfortunately my friend, you can't unlock the bootloader :(
[Google Pixel 2 XL Guides, News, & Discussion] myk.robinson:
Thanks for the confirmation. Just to be on the safe side, other than the fact that I bought it from a local Verizon store, what is the difference? Is there some indicator in the System Information or something that would say "this is a verizon variant?" And possibly more importantly, is this phone not actually "carrier unlocked" since it came from Verizon?

Guess I should have gone to Best Buy or bought it direct from Google :(
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
When you enable developer options by tapping on the build number 7 times, if OEM unlocking is greyed out, it's likely the Verizon variant. Not to mention, you bought it directly from Big Red :cool:
[Google Pixel 2 XL Guides, News, & Discussion] myk.robinson:
Hah! Fair enough ;) And yes, it is greyed out. Poop.

Thanks
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You could always return it, then order the Google variant if you want to unlock and root it :good:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I would reco this option! Google has a $200 off PLUS a 18w charger deal on the 2 XL right now, and they offer the same financing you'd pay through VZW around $40/mo for 24 months 0% interest.

As a VZW subscriber myself, I'd turn that locked phone back in and go Google unlocked :D
[Google Pixel 2 XL Guides, News, & Discussion] liver20:
Can i flash if i am un Locked only booting twrp and flashing magisk and later flash kernel? [MENTION=6842057]nathanchance[/MENTION]

Enviado desde mi Pixel 2 XL mediante Tapatalk
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yes. However, flash the kernel first, and then flash magisk without rebooting.
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
Best Buy only sells the Verizon model.
[Google Pixel 2 XL Guides, News, & Discussion] myk.robinson:
Thanks to all who have responded. I have ordered two more directly from the Google Store and will return these to Verizon next week. I miss my ad blocker....
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Oh sweet dude! Now we can help you blow that sucker up! ????

Seriously though....that's a good move on your part! :good:
[Google Pixel 2 XL Guides, News, & Discussion] myk.robinson:
Especially since I got them for $200 off each, and a free spare charger for each one.... Granted I will have to pay a $25 restocking fee at verizon, but it sounds like its still a win to me ;) All this just to get an ad blocker (and styay on budget)
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Definitely a win win!! :good::good:
[Google Pixel 2 XL Guides, News, & Discussion] T6D16C84:
Attempting these steps, Magisk keeps force closing while trying to patch/install the factory image file. Any ideas?

nevermind, figured it out.
[Google Pixel 2 XL Guides, News, & Discussion] tarroyo:
Got a Pixel 2 XL bout a week ago, Thinking about unlocking the bootloader. Will I still be able to accept OTA's when I get a system notification that there's a update available without issues?
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Well... If you are unlocking the bootloader, I am assuming you want to do something else with it after that. If you are rooted you will not be able to take ota.

BUT

Those of us in the know prefer to flash the full factory image each month as it has less rules and potential baggage. Lol

If you download the factory image and unzip it, you will find the flash-all.bat file. Edit it and remove the -w from the line near the end of the script. This will allow you to "dirty" flash without wiping your data. I have done this for the last 3 updates without a hitch. If this interests you, ask away for more info and one of us will get you squared away!
[Google Pixel 2 XL Guides, News, & Discussion] asad_23:
Hello everyone, I think I foolishly installed twrp incorrectly (in order to go past the password requirement.) and now my phone is stuck on recovery on my pixel 2.

I have spent several hours trying to get different combinations of steps to flash the factory image so I could start over. but it kept failing: it would run the script but then it would fail with giving me the errors like xxxx.img file not found, xxxx.img file not found... at then end "unable to create image."

Today, I can't even get my device to show up on adb devices. so I can't even go to step 2. what could be causing this? can anybody help me please?

Also, what is the reason I can't flash the stock image?
[Google Pixel 2 XL Guides, News, & Discussion] p70shooter:
Just use the button combo and reboot to bootloader, then flash the image
[Google Pixel 2 XL Guides, News, & Discussion] asad_23:
hey, so thats where i am stuck. is there a way to flash the image when adb is not working? i am at the bootloader screen on my phone but i still need to use adb or something else to flash the image. what is that tool? since adb isnt working for me.

adb shouldnt be the issue, i have the current sdk files installed, and it was working for me yesterday so, just a mystery to me.
[Google Pixel 2 XL Guides, News, & Discussion] p70shooter:
You don't use adb at bootloader, it's fastboot.
[Google Pixel 2 XL Guides, News, & Discussion] asad_23:
okay, now i'm getting somewhere. thanks for your help! i was trying to follow the steps exactly, but it turns out i can skip the adb since i'm already there. duh!

ok here is the other problem, the problem i was running into yesterday before i gave up:

when i flash the img. i get this:

Asads-MacBook:~ asad$ cd /Users/asad/Desktop/walleye-opm1.171019.021 ./flash-all.sh

Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh

target reported max download size of 536870912 bytes

sending 'bootloader_b' (38652 KB)...

OKAY [ 0.292s]

writing 'bootloader_b'...

(bootloader) Updating: partition:0 [MENTION=702555]0000[/MENTION]2000 sz=0000B000

(bootloader) Updating: partition:1 [MENTION=702555]0000[/MENTION]D000 sz=0000B000

.......

(bootloader) Updating: abl @0255A000 sz=00065000

OKAY [ 0.897s]

finished. total time: 1.189s

rebooting into bootloader...

OKAY [ 0.000s]

finished. total time: 0.000s

target reported max download size of 536870912 bytes

sending 'radio_b' (60428 KB)...

OKAY [ 0.431s]

writing 'radio_b'...

(bootloader) Updating: modem [MENTION=6558468]00001[/MENTION]000 sz=03B01000

OKAY [ 0.554s]

finished. total time: 0.985s

rebooting into bootloader...

OKAY [ 0.000s]

finished. total time: 0.000s

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

extracting boot.img (32 MB) to disk... took 0.191s

target reported max download size of 536870912 bytes

archive does not contain 'boot.sig'

archive does not contain 'boot_other.img'

extracting dtbo.img (8 MB) to disk... took 0.029s

archive does not contain 'dtbo.sig'

archive does not contain 'dt.img'

archive does not contain 'recovery.img'

extracting system.img (1920 MB) to disk... took 11.459s

archive does not contain 'system.sig'

extracting system_other.img (568 MB) to disk... took 4.011s

archive does not contain 'system.sig'

extracting vbmeta.img (0 MB) to disk... took 0.000s

archive does not contain 'vbmeta.sig'

extracting vendor.img (345 MB) to disk... took 2.310s

archive does not contain 'vendor.sig'

archive does not contain 'vendor_other.img'

wiping userdata...

/usr/local/bin/mke2fs failed with status 1

error: Cannot generate image for userdata

i'm probably missing something, have something in the wrong folder or something... is anything clear by looking at this?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Wait!....are you using a taimen or walleye phone!! ???
[Google Pixel 2 XL Guides, News, & Discussion] asad_23:
walleye. its a pixel 2. i realize this is a pixel xl forum but couldn't find another forum as comprehensive as this one.
[Google Pixel 2 XL Guides, News, & Discussion] p70shooter:
I had the same error the other day. Have you opened the flash all script and removed the -w? I did that and it worked fine then.
[Google Pixel 2 XL Guides, News, & Discussion] asad_23:
that worked!! you are awesome!! i am going to now try to start everything from the beginning and be more careful this time.

I can finally take a break!
[Google Pixel 2 XL Guides, News, & Discussion] p70shooter:
Glad you got fixed up. Stay safe out there ?
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
I've actually been dealing with this exact error since day 1 on my 2 XL, using a Mac. I tried all the basic things like making sure my platform tools are up to date, different usb ports and cables, no luck.

I think I found a fix, somewhere online, I found that you have to run a command, something like "sudo install make2fs /usr/local/bin/"

That may not be the exact command but I ran it a week ago, and today I may finally have some time to try flashing-all to see if it fixes it. I'll update this post on the results.

I know you mentioned removing the -w fixes it, but the flash-all should be working if you want to wipe userdata as well.

Another potential fix I found was adding a "./" In front of every instance of fastboot in the script. So if the first method doesn't work, I'll give this second potential fix a try.

If neither fix works, looks like I'll be using my virtual machine to use Windows and flash-all in there, since it works perfectly fine on that OS.

Strange issue for sure, and apart from this, I've had no other issues with flashing/modding things on my device; so I'm really hoping this fixes it!

Again, I'll be sure to update this post once I give it a shot! :)
[Google Pixel 2 XL Guides, News, & Discussion] tarroyo:
I won't be rooting, I just wanna have one step out the way in the future when I do.
[Google Pixel 2 XL Guides, News, & Discussion] chevycam94:
OK, so I have a question. If I flash the developer preview of Android P, and want to go back to a stable 8.1.0, am I stuck on P?
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
If your bootloader is unlocked you are not stuck, but you will have to wipe data to go back. But if it isn't unlocked, yes you would be stuck on P. Most probably it will become a public beta at some point. Under that system you could unenroll and get an OTA that rolls you back.
[Google Pixel 2 XL Guides, News, & Discussion] chevycam94:
I wondered because [MENTION=6842057]nathanchance[/MENTION] mentioned in the OP:

Not that I want to go back to the December release or anything, but being able to test a new one, and go back to a stable one is a must.
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
No idea what he means there, but you most certainly can flash backwards. I would do it and post pics but dont want to endure the wipe.

It is totally stable for me, not seeing any reports of issues. I did have a few minor odd issues, widgets disappeared, Google now cards were freezing. All fixed with a wipe, which I didn't do when I first installed it. So that is probably on me.
[Google Pixel 2 XL Guides, News, & Discussion] chevycam94:
Gotcha. I wipe and reinstall images on my Pixel XL all the time, but mine is a 32GB, so I don't have a ton of stuff to back up. I'll be working on a custom ROM as soon as I get my Pixel 2 XL. Should be here in a couple days. I decided to hold off and NOT save up for the Pixel 3. I'm fine with having the Pixel 2, and surviving updates for the next couple years. Then I'll see where things are at.
[Google Pixel 2 XL Guides, News, & Discussion] galaxys:
The Pixel XL 2 has come a long positive way! Looking forward to one of your cooked ROM dishes!
[Google Pixel 2 XL Guides, News, & Discussion] chevycam94:
I know I sort of abandoned the Pixel XL, but this new phone has got me all giggly. lol Might take a little bit, but I'll get it working.