yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
removing the "-w flag" by editing the .bat or .sh file, you will

NOT

have to re-install all apps or reset up the phone settings (it's the beauty that Google gave all of its products vs. other manufacturer's). Only your last statement will stand -- You will only have to re-root, reinstall kernel (if custom kernel), custom recovery, custom ROM, magisk modules, and any[thing] that changes build.prop or other system root files. (*i'm not sure about Xposed and other root apps like those)

It's always good to have Titanium backups. Your internal storage will not be touched by flashing the full factory images. Also, it's best to have a Nandroid backup if you are backing everything up as well (TWRP is a good one and is what I use [issues may arise if using custom ROMs and using TWRP backup and restore]). Please keep in mind that TWRP doesn't normally backup internal storage, but there are special ways to get it to include that in backups...

It seems you are doing good and are prepared and set up; which is a very good thing to be before going about these types of things (rooting, custom ROMs, etc.). So it looks like you're in good shape! Some reminders: Some things you don't have to necessarily have on your phone as you only run it from your computer (extracted factory image, twrp image file, etc.), but you will want to have installation files (magisk [if you like to use twrp to install; which is easiest and less messy], kernel [if you like to have a custom one], twrp [if you like a custom recovery], custom ROM, etc.) somewhere on your phone. I'm telling you this because of your concern on making sure to have downloaded everything necessary.

Checklist:

Big downloads will most likely be the factory image

updated platform-tools

TWRP (image file)

Magisk

.zip if you intend to install through TWRP

.apk if you intend to use the app to root (typically more people have issues and errors doing this way)

[*optional] custom kernel

[*optional] TWRP (.zip file) if you intend to install and replace recovery/employ custom recovery

...hopefully I'm not forgetting anything myself in making that list, but I think that's mostly what you need to concern yourself with in terms of what things you need to be sure to have downloaded prior to rooting...

good luck and hope this helps...
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
Reading the above posts has me scratching my head a bit. The one and only time I tried to flash the factory images removing the w, my device was completely back to stock.

All user apps were gone, all system apps were back to the default; basically everything was back to stock with the exception of my internal storage remaining intact. I always thought this was normal behavior by removing the w in the factory image flash-all file:eek:

It's no big issue though, since I've now been flashing the OTA zip file in TWRP, which leaves basically everything intact, aside from root/cust kernel/etc.

Maybe I'll give the first method a try again someday, just for the sake of curiosity and see how things go!
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Hmmmm....it does sound that there might have been a misstep in your case...

By removing "-w" from the .bat (or .sh) file/script, it shouldn't go back to "stock" at all. I imagine the "w" means "wipe", which by removing takes away the option that does "wipe."

In any case, most (if not all) of the experts here on XDA for this phone say that it's better to flash the full factory image instead of the OTA as it is more stable and causes less headaches and incompatibilities later on -- especially so because flashing the factory images does not erase and wipe any data or personal settings (which, in my experience with past phones, usually isn't the case and flashing factory images usually reverts everything to stock; THANKS Google!). Also, there's as much trouble flashing OTA than there is in flashing the full factory due to the steps to unroot to make the phone pliable to sideload the OTA; and either way you have to re-root and re-install all the other goodies (custom recovery, kernel, modules, etc.).
[Google Pixel 2 XL Guides, News, & Discussion] pro4ever:
need help i have flashed going back to stock with flash-all.bat . once all done it just hangs on the white google screen.
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
This is really interesting for sure. I'll definitely give it another try and see how things go.

As for flashing OTAs, I've only done it once so far (April to May) and I've experienced absolutely no issues. If anything, my device feels a bit snappier, and has better standby time. I could have just gotten lucky though, since it was my first and only OTA flash.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Did you remove the "-w" in the flash-all.bat file? If you did, it does take a while since you returned your phone to stock (turning phone on for the first time always take a bit because a bunch has to be set up for the first time).

If you did remove the -w, can you try again and post what your command prompt/powershell returned? It would give a better idea if anything wrong happened during the flashing process causing your infinite loading...

And, if anything, be sure to that your platform-tools is up-to-date, try changing USB cords (USB-C to USB-A is most bug free), try using different USB ports, re-download the full factory image and compare Checksums to confirm you have an exact copy, and make sure that you have included every file you extracted from the factory image in with the adb.exe and fastboot.exe files (you may inadvertently left a vital file/image and as such your phone would be loading with an "incomplete set").

Good luck and hope this helps...
[Google Pixel 2 XL Guides, News, & Discussion] pro4ever:
no m8 i did not remove -w?
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Oh that's probably for sure! Updating will almost most definitely help and improve. The reason why it's said that Full Factory is superior to OTAs is because OTA's overwrite the current/previous partition, which can eventually (due to numerous "overwritings") lead to incompatibilities, bugs, glitches and the like. Whereas Full Factory flashings seem to wipe and/or completely replace rather than merely overwriting. So, since you had only flashed/sideloaded 1 OTA, you wouldn't be susceptible to the adverse effects, just yet;) .

It's a good thing to keep in mind. But yea, your initial experience really didn't go as normal to the rest of us so it might be worth trying again. If anything, make a backup/copy of your phone, just in case it returns to stock again.

Have a good one!

---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------

So you intended on returning your phone to stock....right? (hopefully) How long does it "hang" on the white screen? Or have long have you waited for it to be loading...?

In any case, my other requests and advice still stands. If you could post what your prompt returned when you flashed would be most helpful. Also, the other advice is more for issues that come with flashing that could cause errors and/or your type of issues (bootloops, infinite loading, etc.).

If anything and nothing seems to help, check out Deuces bootloop script. It's done wonders for a lot of users experiencing similar issues. You should already have most of the resources necessary for it...
[Google Pixel 2 XL Guides, News, & Discussion] MrPhilo:
I plan on flashing another kernel but want to return to a clean slate while retaining my data.

So if I did the 'flash factory image' step when you delete -w, would I keep my data? It be just a stock ROM with my data (apps signed in etc) and only thing missing is root and TWRP?
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Correct. Root, TWRP, and other modules and Xposed and other of those root related apps. Everything else should stay put, but should put you at a "clean slate". :good:
[Google Pixel 2 XL Guides, News, & Discussion] MrPhilo:
Thanks! If I was to stay in bootloader, boot to TWRP and flash Magisk, would my Magisk module still be there or is it actually gone?
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Only TWRP would be gone by booting that way. Your Magisk root exploit would stay; and even the Magisk app would automatically be installed and stay in your system as well!

Some advice I find makes less headaches (from my own personal experiences): If you intend on having custom kernel and custom recovery, flash the Magisk .zip installation file last, others first; or you will bootloop into recovery and have to flash Magisk again each time.

Good luck and hope this helps!
[Google Pixel 2 XL Guides, News, & Discussion] Brenneke:
Updated images for Telus variants are slow in coming. Can anyone see any potential problems switching to regular Google images to update? I have had best success with the full image -w removal method in the past, could I do the same if I was to go this way?
[Google Pixel 2 XL Guides, News, & Discussion] MrPhilo:
Hi, do I also need to have done unlock critical to flash above images? I've only unlocked
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yes sir! Unfortunately, it'll wipe your phone.....again ?
[Google Pixel 2 XL Guides, News, & Discussion] MrPhilo:
So even after deleting -w it will still wipe?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Nope, it just won't flash! It'll fail to update the bootloader ?
[Google Pixel 2 XL Guides, News, & Discussion] MrPhilo:
So if I backup via twrp, unlock critical, boot twrp restore and flash image, would that work? Still learning how pixel work as I moved from 5T! Sorry for all da questions
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yep, that should work. However, you'll have to transfer your backup to your pc before you unlock critical of course, just backings up the data partition is all you'll need. And then transfer it back in order to restore with twrp. There's really no way of avoiding loosing all your data when you unlock critical unfortunately ?
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Also, keep in mind that TWRP does

not

(*typically) backup your internal storage (internal sd or /sdcard) in its backups -- as your data "folder" doesn't really* include your internal storage therein. There are workarounds to include this internal storage data to your TWRP backups, but it certainly isn't the normal steps of simply clicking the Backup button and selecting partitions. If you are interested, you can PM me and I'll point you towards the right direction...

In any case, yes, it is unfortunate that the unlock_critical command wipes it all. And that's why it's advised in most OPs of guides to issue the command at first and/or as early on as you can before you build upon something you'll have to wipe later on; most beginner users get nervous about it because they feel like they only want to "kind-of" root and don't want to risk failing SafetyNet checks or the like -- which is unfortunately not true as many (including myself) can have critical_unlock and still pass all those checks and even work Google Pay without issue or flags!

But at least you have the option of saving much (if not all) of your personal apps and settings before having to wipe...so there's something!

Hope some of this helps...Good luck to ya!
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
Could you use a USB C to USB flash drive to flash from?
[Google Pixel 2 XL Guides, News, & Discussion] lssong99:
Just want to make sure one thing. On the OP it states:

NOTE #2: If you have mounted /system as rw at any point (like in TWRP), you must upgrade using the factory image method. OTAs will fail because they cannot verify the integrity of the disk since its verity data has been changed.

Since I want to flash the new DP2 image and then use TWRP (temp boot) to flash Magisk. Just want to know if above case is still true, this means when DP3 out, I will have to flash everything with factory image (thus clear data) without possibility to use just adb sideload for OTA? (which won't clear data).

Or flash Magisk only modify boot.img, so not touch on /System (mount r/w), so no issue here?

I do know the risk of dirty flash, just want to know if about Note 2 still holds now...
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I flashed the factory image and I accidentally wiped everything and now it takes me to the white start up screen that says Google and shows the unlocked icon, but doesn't go any further or shut off. Just stays there. Any suggestions?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yes, it still holds true. Which is why you need to have stock recovery and no root to take OTA's. You can upgrade the factory image without loosing data, however, as you stated, you know the risk. Downgrading would require a clean install of the factory image, which, will wipe your phone.

Try fastbooting the factory image again, and/or try a factory reset. BTW, how did you "accidentally" wipe your phone? ?
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
When flashing the factory image, I deleted the -w in the wrong flash-all. So when I did the flash-all.bat...it wiped it.
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I'm having issues with ADB. It's saying it's out of date. I googled how to fix that, could that be why this isn't working properly?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Definitely yes!
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I've been googling ways to fix the issue and finding multiple answers. Is this going to be possible to fix with my phone in it's current state? What's the suggested way to fix this? I've seen to download a ADB fix thing or to kill adb and then root ADB....any suggestions?
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
New to taimen. Please clarify. Do I want Magisk 14.4 as it says in the official Magisk Pixel 2 XL thread or the latest, the beta 16.4?
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Grab the ADB files for your PC from post #1, that link always has the most up to date ones. Note the are called "SDK Platform Tools for Windows or MAC or Linux".
[Google Pixel 2 XL Guides, News, & Discussion] galaxys:
Go for the beta 16.4
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Grab the latest 16.4, Magisk Manager will be auto installed as well.

See my sig for Pixel 2 XL instructions that include links to all files needed, including latest Magisk. Once installed, you'll also want to go into Magisk settings and change CHANNEL from stable to BETA.
[Google Pixel 2 XL Guides, News, & Discussion] adkamble89:
My pixel 2xl not connecting or showing connection to computer after unlock bootloader

hello there, i have pixel 2xl and i was tried to flash android P dp1 with outdated fastboot/adb, and i was managed to unlock bootloader and flash dp1 but now after updating to dp2 via ota update, some problems occurs

1) headphone stops working, one pop up message show "usb supplying power to attached device".

2) whenever trying to connect mobile to computer always showing malfunction usb.

i was try several methods to solve but problem still there. i was contact a person from google but he told me u unlocked bootloader so we cannot solve your problem in warranty it will be charged for this . plz help me
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
The final most way to fix our phones (Pixel 2) is usually to flash the full factory image (and sometimes with "-w" intact). Of course even that might not work if you're not on the latest platform-tools/adb/fastbood version. And after doing all that, if it still "hangs" on the Google loading white screen, either something went wrong (or did something wrong) when you flashed or you're not waiting long enough for your phone to set up (as the "fresh" stock first-time set up can take a long time to load up first time around...)

Hope this helps....
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I let it stay on the Google screen the whole way to work which is an hour for me. I would hope that's long enough to tell. Lol

---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------

Just know that I appreciate everyone's help whether this works or not. I should have had a better grasp of what I was doing. I'm a flash junkie from the old school. I got over zealous about all this and got myself into this mess.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Yeah...then something is going wrong when you're flashing the full factory image...

What would help is what your command prompt/powershell returns or log of what is stated when you flash...might point towards what's going wrong or failing...;)
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Without intending at all to sound condescending, did you make sure you grabbed the TAIMEN factory image? I know at one point, the Walleye image was directly below the TAIMEN image.

When all the normal things have been covered, start looking at the abnormal :D
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
I dunno....I've been helping him and pm'd him the direct link to the taimen image because I had the same thoughts and was along your line of thinking...

...And it's been happening a lot lately in this forum...a lot of Pixel 2 (non-XL) walleye users are coming over here (I imagine because a lot of the experts chose the XLs) and they show/use the walleye images around these taimen parts which causes and starts all sorts of confusion....
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
Definitely taimen. I'm going to grab the sdk and all that and start over. It was working fine and all of the sudden the ADB said it was out of date and such. The mistake I DID make was grabbing the Fi version of taimen and used it first. Not sure if it's the culprit, but I know I made that mistake.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
yeah, unless you're using Fi, that most definitely would've caused problems...

Those are usually the 4 culprits in like 95%+ issues on this forum: 1) out-of-date platform-tools 2) USB cords 3) images of wrong models 4) not reading the OP and associated warnings

But at least you have an idea so it can get sorted out and on the right/correct path...
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
It was worth a shot :D

If you need a single place to find what you need to start from scratch, there's a link in my sig that has links all the latest files, tools, and images to get you up and running.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
God you're awesome Az Biker! Even your signature is ridiculously helpful!

...just wondering...I hope you have a script or code that keeps that stuff up to date for you...or that would possibly be one of the most tedious things (as it's updated frequently enough)...?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Haha! A script? I'm not a code guy. I can't even run fastboot by memory :p Those guides aren't to help others, they're to help me remember how to not screw up my devices :D

Seriously though, the Note 3 and 6P resources aren't really changing/updated much any more, and the 2 XL link just gets updated as major stuff comes out, so it's no problem at all.

I'll never forget how lost I was when I first started rooting and flashing my first device. Every word I typed screamed NOOB.

So I do what I can to make that transition for other new users, or users not familiar with how the 2 XL runs... Especially those who are obviously trying to help themselves.

You know, the whole "teach a man to fish" mentality.

There are plenty of super helpful regulars on the 2 XL, just like the 6P, the Note 3, etc. etc. I just jump in when I can :D
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Haha awesome...! Yea i'm not a code guy either (that's probably why I'm under the impression there's some magic way to link all of your stuff to the most up to date things automatically; haha magic:p)

But yea, we've all started from scratch at one point in time, so it is super helpful that you (us) help out and try to make it easier to those who are the new ones now... The only reason I'm so proficient in computers, software, and smartphones is because I kept experimenting, breaking the f*ck out of the devices, and I had to learn to repair and nearly rebuild them from scratch (thus learning the ins and outs from the bottom up). So I find -- like you probably -- that many of the problems I see here on the forums and threads are problems I created and encountered for myself and have experience on. I would say that I probably broke my phone the furthest to the max (without the need to send for a RMA or replacement); I got it so bad of a corrupt device error message that I had to manually flash individual images towards individual partitions and even manually had to edit the sizes of partitions! (I was googling like crazy not finding any others who have encountered my issues; also this was in November when the phone was still relatively new)

So it's nice to give back and help others like when I was panicking because there was really not much resource or anyone else going through the same thing...

My apologies, I don't mean to hijack or go too off-topic....

"Now, back to your regularly scheduled programming..." on Unlock[ing]/Flash[ing]/Root[ing]....
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
AZ and Simple man are on the case. Y'all should have this puppy screaming mayday by midnight!! Well done guys! :good::good:
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I hope, because I'm getting nervous here lol.

---------- Post added at 10:12 PM ---------- Previous post was at 10:04 PM ----------

Should I leave the -w in the .bat or delete it?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
If you want to wipe data, leave it. If not, remove it :good:
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
Deleted