yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
I would be very happy to help....but it does seem that this/your issue is no longer a "Unlock/Flash/Root" from the GUIDE type of problem and more of a general recovery and/or restore issue...which probably means that this calls for it's own thread and not "hijacking" (not particularly, but in a sense) this thread about its issues rooting and/or flashing; I know this issue came upon originally when trying to flash/root, but still....

The lines "FAILED (remote: Check device console.)" and "Can't determine partition type. FAILED (remote: GetVar Variable Not found)" are curious to me and stick out. I'm curious to see what your phone (the "device console") outputted at that part. And the "determine partition type" and "GetVar Variable Not found" seems to point that the partition and "filesystem" may be wrong (for example: when you flashed the custom ROM, it put it at FAT32, but Android runs on EXT4 [*this is purely just examples and are nowhere near accurate or correct]). Most likely the GetVar command is searching for a particular variable as it assigns it to different partition types (1=ExFAT, 2=FAT32, 3=NTFS, 4=EXT4, etc. [*again, purely for example purposes only; not accurate or factual]) and yours is either not returning a specific number it wants which is the correct number and/or not returning a number at all. I have an idea as to how to go about fixing this (I think I have ran into a similar situation in my "dealings"; aka breaking my own to sh*t and attempting to fix it :p), but I'll save that once it's confirmed where/if this discussion should be set (here or its own thread...)

________________________________________

P.S. Actually, after doing some research of the "getvar" command (in trying to continue to help brackett5), I was close but not completely correct about my assumptions. The "getvar" command attempts to get data for various specific information from your phone and returns a "variable" (i.e. size of a partition: 0xD43FB0000 [hex value], or partition-type: EXT4 [which I was correct in guessing]). It seems, in brackett5's case, that it wasn't returning one and/or was returning an incorrect "variable"...

"...The more you know..." **~chimes~**
[Google Pixel 2 XL Guides, News, & Discussion] techlogik:
Good guide.
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I've created a new thread here in hopes I can resolve this issue.

https://r.tapatalk.com/shareLink?ur...share_tid=3791510&share_fid=3793&share_type=t
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
The 2 XL Q&A section would be a great place to post this as well.

That way, any Xda members having the same / similar issues will have a resource to search and participate in.
[Google Pixel 2 XL Guides, News, & Discussion] cognitivedissonance:
Sorry in advance for the stupid question, but do we have to disable the pattern lock and finger print unlock before making nandroid backups? I believe that used to be the case before TWRP was able to reliably decrypt the system (which it does in the most recent release.) I assume it's ok to leave it now that TWRP seems to be password compatible?
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Hey cognitive! It's been a while...

I believe most (if not all) of your assumptions are correct. If anything, I'm under the impression that along with not encrypting your phone, disabling any screen lock will leave the TWRP backup (and its data) unencrypted as well; that or, simply, it was only necessary for TWRP because it couldn't read it encrypted -- but I believe that the act of decrypting and/or compression somehow modifies the data in any case...

Hope this helps...
[Google Pixel 2 XL Guides, News, & Discussion] JazonX:
New User Here,

Can I follow the same guide on OP to get Root and TWRP on the Android P DP-2 ?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yup :good:
[Google Pixel 2 XL Guides, News, & Discussion] cognitivedissonance:
Hey simple, thanks for the help again! Seems like I'm always coming up with some weird question that I've seen discussed briefly but can't find an answer to when I need it haha. Anyway, if I'm reading what you're saying correctly, I believe you're saying that since the newest TWRP finally plays nice with passwords, we don't *have to* remove them before making a backup, but it still may be the best bet just to avoid any issues with encryption. Also, you seem to be indicating that it perhaps isn't a good idea to have TWRP compress backups either. Am I interpreting what you're saying correctly?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Always a good idea to remove screen lock security and disable or remove all theme overlays before making a backup of boot, data, and system. Personally, I've never made a compressed backup, so can't comment on that. However, I've never had any difficulties restoring a non compressed backup :good:
[Google Pixel 2 XL Guides, News, & Discussion] stslimited84:
anybody having issues pulling the factory images from google? They arent displaying for download and neither are the Full OTA images. Just the binaries show up.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
If using chrome browser, switch it to incognito mode. Or use another browser :good:
[Google Pixel 2 XL Guides, News, & Discussion] dnsmo:
thank you for the reference, I was having problem getting through that acknowledge thing. keep clicking on it but got nowhere afterward. I was going to send google an support ticket.
[Google Pixel 2 XL Guides, News, & Discussion] stslimited84:
Appreciate the reply. Tried firefox and chrome both normal/private browsing options to no avail :confused:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Go incognito chrome on your phone. Then move the dl to your pc :good:
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Of course! It's no problem! But as for the compression concern, I only mentioned it to indicate that the backup is "transformed" in a sense in any case. That's all. I actually employ compressing without any issue...is actually the only way I can get it to fit because I do a out-of-the-ordinary backup that includes my internal data and /sdcard. But I say you shouldn't worry about using compression...

Yea, a sure fire way (at least in my experience) to get that sure to work is, if u know how, use Internet Explorer 11. Hasn't failed me (specific to this site) yet! Just in case you're still having issues... It is weird that Google's browser isn't showing compatibility towards its own website :eek:
[Google Pixel 2 XL Guides, News, & Discussion] philip_rhoades:
It has been six years since I rooted a phone and converted from a stock ROM to a Custom ROM (Galaxy Note 1) - I was extremely anxious then about bricking the phone and I feel the same way about my second smart phone - the Pixel 2 XL.

To make sure I _really_ understand everything, so there won't be any tears re this very expensive phone, I have some questions about your notes:

At the end of "Unlocking the bootloader", you say to reboot - which suggests the phone will reboot to normal operation? - but at the beginning of that section you say:

"WARNING: This WILL wipe your entire phone. Please make copies or backups of any important data. This can also go wrong rendering your device inoperable. Proceed with caution."

Is that comment in the wrong place? Should it be in the "Flashing factory images"?

In the section "Flashing factory images" you say:

"Download the latest factory image from _Google's website_"

but when I try to click on "ACKNOWLEDGE" on that page, the page is just redrawn - I have found another site with the image file but I feel safer getting it from Google.

After unlocking the bootloader, is flashing the same or a new image necessary to get the phone working again?

Thanks for your work!

Regards,

Phil.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
There's a pretty detailed 2 XL step by step linked in my sig that should remove the vast majority of your concerns.

The Google site has been wonky a few days now, hopefully it's back to normal soon.

You'll love the 2 XL rooted and unlocked :D
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
[MENTION=4789007]philip_rhoades[/MENTION], you should listen to anything and everything Az Biker says; doubtful you'll ever be steered wrong. The step by step is the one that (if I recall correctly) I used myself...

But to give a quick answer to your confusion towards flashing -- when you enter the command to unlock and unlock_critical, it's like a simple switch. You need to "flip" this switch to flash, but entering the command is not flashing in of itself. Just activating this "switch" requires a full wipe, but it merely reverts to stock everything and it'll load up like you just turned on the phone for the first time...

And, I know you're worried, but "flashing" on this phone isn't as scary or perilous as flashing used to be with older phones. I can assure you that outside of physically damaging the internals of this phone, because Google made the bootloader as accessible as it is, you pretty much can't get to a point of "no return." I've personally experienced "breaking" this phone so corruptly that I had to change the partition type and partition size and reformat and wipe and a whole bunch of other crazy stuff -- and I'm still currently using that same exact phone, no RMA or replacements! Point is, even if you "wreck" it badly, there's a very good chance that it'll ever get so bad (most likely not near as bad as I had put mine) that it'll be as final unrecoverable as you fear...

And, in the end, if anything, you got some great experts here at XDA to offer help and guidance if then...

Good luck and hope this helps!
[Google Pixel 2 XL Guides, News, & Discussion] philip_rhoades:
Rooting Phone -> USB "Not Connected"

Thanks for that - I have started downloading stuff and working my through that - I think there is a logical problem though, wrt to installing TWRP, you say:

but all the following steps assume that TWRP IS installed . . I am going to install TWRP anyway but if you want your page to be the canonical install page - it needs to be perfect - numbered steps would help too so that people can refer to the step by number.

Yep, going again now - the file downloaded from there had the same checksum but it is good to know that the other site was not dodgy.

I certainly hope so! - I am really looking forward to it, however, I can't get started at the moment with the actual implementation:

Today I started to see about connecting it to my Linux machine via USB - after setting USB debugging on and selecting MPT for USB configuation - I got no action even after trying numerous USB cables and PC USB ports with the supplied Type C - Type A adapter. Then I realised that under "Connected Devices" that the USB device is showing "Not connected" and is greyed out - it is the same even when the phone is plugged into the supplied cable and into the supplied charger and charging OK - so it doesn't look like a cable problem - it looks like a software, port or phone problem.

I have seen that there are many reports re problems with charging / not charging and charging / not transferring files etc so I am concerned that the phone will need replacing . .

I will get a USB3 Type A - Type C cable tomorrow to see if that is any better but I have seen reports that only USB2 A-C cables work!

Now that the phone is fully charged again, should I do a factory reset and see if that improves the situation?

If anyone who could shed any light on this fairly annoying situation I would greatly appreciate it . .

Details: taimen-opm2.171019.029

Thanks,

Phil.

---------- Post added at 12:43 AM ---------- Previous post was at 12:33 AM ----------

Yes, I have sent a note to him to about the current issue which is a connection USB problem - so I can't even get started.

Yes, I understand the idea of a "switch" but unless this "flipping" changes the size of the boot track or whatever, I don't see why a re-flash would be necessary . .

Thanks for that reassurance - I appreciate it and have determined to press on!

Yes, there are some smart, helpful people here alright.

It did - and thanks to you too!

Regards,

Phil.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
The reason it is listed that way is you have to initially install TWRP by fastbooting the TWRP.IMG file.

Once it is temp installed, you flash everything from within TWRP (just as if it were permanently installed),

then once everything is flashed via TWRP, you reboot, and TWRP goes away.

I'm glad to see others reading instructions thoroughly enough to offer correction and/or suggestions, that's what makes this whole thing better; TEAMWORK!

As far as the USB issue you're facing, I'm not a Linux guy, but make sure you have the latest SDK Tools on your PC as well.

Best of luck getting everything up and running
[Google Pixel 2 XL Guides, News, & Discussion] philip_rhoades:
Ah! I see - makes sense now - thanks!

Happy to help of course.

It is definitely on the phone side - nothing is getting through at all - I'll see how the new cable goes - there are lots of reports of USB-related hardware problems . .

Thanks! Getting closer . .

Regards,

Phil.
[Google Pixel 2 XL Guides, News, & Discussion] aostrom:
Thank you, thank you, thank you!

[MENTION=6842057]nathanchance[/MENTION] and [MENTION=1164058]azb[/MENTION]iker,

As always, your clear instructions, based on experience, have made it a breeze to get my new Pixel 2XL up to speed quickly and safely. I'm sure I could have figured it out from the Google pages, but knowing that you guys had vetted the process was a real shot of confidence.

It was a piece of cake to unlock the bootloader, ADB load the "P" DP2 factory image, then boot into and flash TWRP. Installing Flash kernel & Magisk was straightforward, and then I copied all the crud from my 6P over to the Pixel 2. I know that some folks have had issues with USB-C connections, but I used a high-quality USB-C to USB-C cable (Anker USB 3.1) connected to a StarTech USB 3.1 expansion card in my PC, and the transfers were incredibly fast.

It's folks like you two that make the XDA community such a valuable resource for us all.

Thanks again!

Andy

BTW - One question for folks - since I loaded Android "P" DP2 from the factory image is there any reason/value to signing up for the beta on the Google side?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Not at all. Much easier to do what you did instead of signing up for beta, then unenrolling and all that jazz :good::cool:
[Google Pixel 2 XL Guides, News, & Discussion] Susilo378:
Root
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Root Woot! :confused:
[Google Pixel 2 XL Guides, News, & Discussion] HACK3DANDR0ID:
So i just traded someone my Galaxy S9+ for a Google Pixel 2XL YaY! When i got the device it was on P Dev Preview, i did the Boot Loader Unlock and i wanted to put it back to 8.1.0. I downloaded the latest 8.1.0 ((OPM2.171019.029.B1, May 2018) and it BRICKED the device. I get 4 screens, The software in the device is currupt. The device may not work properly 2) BootLoader Unlock Message 3)Google Splash Screen and 4) I can get into bootloader, but it wont read adb or fastboot, i was gonna try and flash TWRP and get on a custom ROM, but no go.....

Before i ship this back to Google tomorrow, anyone have any ideas?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Did you run BOTH bootloader unlock commands?

How did you flash the factory image? With the flash-all.bat script or with manual fastboot commands? Are your platform-tools up to date? Have you tried different USB cables and ports? You may want to look into dueces recovery script if you want to have a go at fixing it. Btw, the bootloader warning screen is normal ?
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
I think any relocking of the bootloader will wipe the device.

I don't know how to decrypt with this device and I don't honestly recommend doing so.
[Google Pixel 2 XL Guides, News, & Discussion] Youngbloodx:
I was able to unlock bootloader and flash a 8.0 and 8.1 just to get the hang of using the android SDK, as this is my first time doing something this technical.

But I'm unable to root, I'm not sure what I'm doing wrong.

Step 1: I downloaded the factory image for 8.0 from google and extracted the boot.img from within the zip.

Step 2: moved the boot.img to my phone via google drive (i also tried this step via a regular usb cable transfer)

Step 3 (I think this is where I am screwing up): I downloaded the magisk apk 5.4.1 . Open the app, click install. This gives me a pop-up saying 'Do you want to install MagiskManager-v5.4.2apk now?' I click install. My device then downloads this in the background and click install. (I assume it's basically installing another version of the same magisk app)

Step 4: Another pop-up then reads "Do you want to install MagiskManager-v5.4.3apk now? My device downloads another app version in the background and installs it.

Step 5: Upon opening Magisk for a 3rd time a prompt shows up "do you want to install Magisk-v14.0zip now? I click install and this finally gives me the option to either download zip only or patch boot image file.

Step 6: I click patch boot image file that I transferred from my phone.

Step 7. I move the patched_boot.img file from the MagiskManager folder to my computer

Step 8: put my phone in bootloader mode (restart phone and hold the volume down button)

Step 9: On the command prompt window i type in "cd <location of my sdk platform tools> " then "fastboot flash boot <location of where the patched_boot.img file is on my computer>" (I read that its best for me to just drag and drop the file into the command window right after ...flash boot )

Step 10: I press enter and the command prompt window seems to do what its supposed to do. The command is completed in just under a second. (I'll take some screenshots when i get home). But my phone doesn't seem to do anything. It was in bootloader mode for a while and the background light had gone dark then lit up again when i hit enter on the last line of code, but that is the only response my phone had.

When i rebooted the phone to check if root worked, magisk app still showed me that the phone is not rooted. I tried this several times starting from step 1 with the same results. One time, however, it seemed to work but when i restarted my phone it was stock on the 'G' logo for about 10 minutes so I think it bricked (I was pretty scared cuz the phone obviously ain't cheap) I had to go back to bootloader mode and flash the factory image which saved me. Good thing I practiced doing that a few times before starting the rooting process.

So my question is... wtf am i doing wrong? lol. I think its step 3 to 5 that is not going so well.

Sorry for the lengthy post, but I just wanted to be thorough and make sure I communicate my steps properly. Thanks.
[Google Pixel 2 XL Guides, News, & Discussion] SimoJag:
Can I reset a Verizon Pixel 2 to factory (without the Verizon SIM installed) and 'restore' the phone as purchased from the Verizon store and successfully OEM Unlock it? The phone came with Build: OPD3.170816.012 and Kernel android-build@vpbs19.mtv.corp.google.com #1

I'm looking to replace the OS ... The reason I bought it from Verizon was I needed a phone in a super hurry... As I understand it, the radio ROM will work anywhere CDMA. GSM etc..
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
Magisk Root Issue

1) "unlock_critical" didn't work, but "unlock" did, so went with that

2) Did achieve root, but lag was pretty bad, so started again with uninstalling Magisk and flashing 025 image.

3) Attached the Magisk Install sequence. It keeps asking to install version 14.0, however, when I first tap the APK, it's Version 14.5. Any thoughts on why it doesn't complete the install process? The adb messages on the PC return no errors.

Dread a factory reset, but is that the only answer?
[Google Pixel 2 XL Guides, News, & Discussion] xflowy:
ok, thx. i thought of doing it since "disable forced encryption" was a thing on my nexus 6p before.
[Google Pixel 2 XL Guides, News, & Discussion] sidhaarthm:
Hello mate,

Long shot, but I was facing a similar problem and here is what fixed it for me:

- Go to Magisk App Settings

- Under the Update Settings, change the 'Update Channel' setting to Beta.

- Now, refresh the app, you should see that Latest Magisk version is v14.5 and the installed version should also be v14.5, i.e. no version mismatches.

Previously I was unable to obtain root no matter which boot image (stock or custom kernel) I tried to patch. After the above tweak, everything now works and I'm running Flash v1.03 :)
[Google Pixel 2 XL Guides, News, & Discussion] Youngbloodx:
Thanks for replying. FYI: I also posted this reply on the main magisk thread https://xdaforums.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176/page104 but i didn't want to ignore your post. I'll just be posting there from now to avoid any more double entries.

After downloading 5.4.1 magisk apk from the first page, I was prompted to install but I clicked 'not now' . Then I followed your instruction to switch to beta under the settings menu. After doing that, I refreshed the app and then chose to install.

Screenshot 1 is what the app looks like after I've installed using the beta channel.

On screenshot 2 .... Before your post I was not seeing the 4th line "A/B partition detected..." so I guess that is a step in the right direction but I'm still experiencing the same thing with bootloop 'G' screen. The file size of the patched_boot.img is 25.17mb. Maybe I'm not following the right order during the step for beta channel switch?
[Google Pixel 2 XL Guides, News, & Discussion] raver445:
does anyone have images of stock recovery and the boot sig images i need them badly my phone bootloops and i only have access to bootloader mode. the phone says it cant load the operating system and even the factory reset doesnt work. any help would be appreciated,
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
What about the google factory images? You can't download them?
[Google Pixel 2 XL Guides, News, & Discussion] drewski_1:
I'm pretty sure that I got those messages for missing *.sig files. Probably something else causing the bootloop.
[Google Pixel 2 XL Guides, News, & Discussion] raver445:
i actually got it working.

---------- Post added at 08:25 PM ---------- Previous post was at 08:23 PM ----------

i was able to fix it using command prompt. using a flashing script.
[Google Pixel 2 XL Guides, News, & Discussion] azpatterson3:
Messing with rooting for awhile today. If you're running Linux, make sure you are in su. I was able to run ADB commands but kept getting hung up on fastboot. I must have been in su when I unlocked bootloader but forgot that when trying to push the patched boot.img. all good now.
[Google Pixel 2 XL Guides, News, & Discussion] DaveMar:
I'm boot unlocked with a Google phone and sideloaded nov OTA. I wanted to know if I can install latest twrp & magisk with just bootloader unlock... or is critical unlock needed? Second question then... can I just fastboot unlock critical or need to flash full image then unlock critical.. Thanks
[Google Pixel 2 XL Guides, News, & Discussion] drewski_1:
You can Unlock Critical, but that shouldn't be needed for twrp / Magisk flash.
[Google Pixel 2 XL Guides, News, & Discussion] DaveMar:
So TWRP will be fully functional without unlocking critical? That's great!
[Google Pixel 2 XL Guides, News, & Discussion] Fuzzy13:
edit
[Google Pixel 2 XL Guides, News, & Discussion] Prattham:
so i have rooted s4 n5 n6p op3 and damn this looks more complex and confusing