yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] xDakos:
Ive literally tried any G screenloop guide/tutorial but nothing worked out on android 9

like I said Ive tried anything in the past week and always at the step I flash magisk its bootlooping

Btw It worked already one time but I locked my Bootloader for something and wanted to root it after that again since then it doesnt work anymore.
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
Have you tried booting to fastboot mode to re-unlock (and critical unlock) again? This will wipe your phone and probably allow you to boot System. Have you tried putting it in recovery mode and pushing a full OTA image from your PC? This assumes you have a working recovery. You really need to provide more info on where you are at and what you have tried other than saying "every guide out there".
[Google Pixel 2 XL Guides, News, & Discussion] xDakos:
Ofc I tried that but I found a working way 100% working everytime tested it 3 times now

1. Flash-all -w (I dont know if that is necessary if you do everything else like I say)

2. Setup your phone and install the magisk manager app

3. Put all your stuff you need magisk and custom kernel on you phone

4. Boot into bootloader and fastboot into trwp

5. flash custom kernel and magisk dont install trwp permanetly

6. profit
[Google Pixel 2 XL Guides, News, & Discussion] Valeriuz:
Deleted
[Google Pixel 2 XL Guides, News, & Discussion] Avasta:
Just updated to the newest Magisk Manager 5.9.1, ran into an issue when trying to patch the boot image with the newest V17.1. The output of the patched boot image is not in the location listed in the first post in this thread. The output is the normal sdcard/Download folder, meaning the correct command is

Just a note for those that tried to patch the image but kept booting the device to find that the version was not updated.
[Google Pixel 2 XL Guides, News, & Discussion] Ghisy:
Hi there,

Is anyone having problems with the latest Magisk update (17.1)?

Since I updated, my fingerprint reader hasn't been working well. It took me several attempts to register my fingerprints again and it refuses to unlock very often. It was working OK with 16.

I also posted this in the magisk thread but if anyone has another idea... I'm running Oreo 8.1 with Flash kernel 2.58.

Thanks!
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Dozens reported this in main Magisk thread.

NO ONE has posted a LOG, to find out why so it can be addressed. :confused:
[Google Pixel 2 XL Guides, News, & Discussion] Ghisy:
I would post a log but not sure how to get it! I haven't done that in a long time. What app do you use for logs?
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
ADB logcat - way more efficient and powerful filter ability.

https://xdaforums.com/showthread.php?t=1726238
[Google Pixel 2 XL Guides, News, & Discussion] Ghisy:
Thanks! I just posted the logcat in the Magisk support thread.
[Google Pixel 2 XL Guides, News, & Discussion] zard:
Hi, need some advice.

Got my XL at end August and updated to official Pie successfully.

Did the double unlock and use patch Rom method to root. Left recovery as stock.

Today, first time to flash security update.

I ran 'Adb reboot recovery' and it booted to a screen with Android lying down and '!'.

Is the issue because I did not uninstall Magisk?

I then booted into latest TWRP from fastboot and flashed Magisk uninstaller. Then I used sideload in TWRP to flash the OTA zip. After a short moment, my XL screen went blank and I couldn't wake the screen up. Luckily, I was able to see the sideload progress on computer. When it completed, I used fastboot to reboot. After successfully rebooted, I went back to TWRP to flash Magisk.

How can I prevent TWRP screen from going blank and how to wake it up if it goes blank?

Sent using Tapatalk
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You booted to stock recovery because you had stock recovery by your own admission, had nothing to do with magisk. The easiest way to keep twrp from acting up is to use a custom kernel, and set the twrp screen time out as high as possible :cool:
[Google Pixel 2 XL Guides, News, & Discussion] zard:
You misunderstood me. Yes, I wanted stock recovery. Question was, why I ended up with a screen showing Android character lying down and '!' mark and not the correct stock recovery screen? Was it because I'm supposed to uninstall Magisk before flashing OTA in stock recovery?

Thanks for sharing about custom kernel to increase TWRP time out. So does it mean that if I want to keep to stock kernel, I will continue facing the issue of screen blanking out in TWRP?

Sent using Tapatalk
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Sorry for the misunderstanding. Your likely right then. Most users I've seen remove magisk before side loading the OTA. As far as twrp and stock kernel, not necessarily, the screen time out is the easiest way to prevent that. What the stock kernel may cause is a lack of touch response in twrp. Which is why many of us use a custom kernel. If you want to stay as close to stock kernel as possible, look into Ex or Sultan's kernel. Those 2 Devs are outstanding, and keep their kernels very close to stock, especially Sultan :good:
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
That is normal behavior. Hold Power and press Vol Up to get to recovery menu. ;)

Mornin' honeybadger, maybe another cuppa? :D
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Heck ya buddy! I've been up most of the night awaiting the arrival of our first grandson! I'm psyched, but not quite firing on all cylinders! ?
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Congrats my friend, that is wonderful! :highfive:
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
You should be able to just tap the power button to turn the screen back on.

I did not remove Magisk before sideloading the September OTA in TWRP. The update ran fine, and Magisk was removed for me. I had to reinstall TWRP and reflash Magisk, then all was well (all settings and modules remained intact).
[Google Pixel 2 XL Guides, News, & Discussion] zard:
In my case, power button won't turn on my screen.

Sent using Tapatalk
[Google Pixel 2 XL Guides, News, & Discussion] sameerraja 929@gmail.com:
How to root my divecRoot

---------- Post added at 03:53 AM ---------- Previous post was at 03:51 AM ----------

:silly:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Read the OP.
[Google Pixel 2 XL Guides, News, & Discussion] zard:
You are right. This was the reason. Thanks.

Sent using Tapatalk
[Google Pixel 2 XL Guides, News, & Discussion] t-ryder:
As the newest TWRP was just released I wanted to update, so I removed fingerprints and PIN, did the quoted above (TWRP update, Magisk and Flash Kernel Wahoo) and after the reboot some of my most important apps (outlook, skype, online banking e.g.) did not work anymore. Cleared dalvik and cache, uninstalled the apps, cleaned with SD maid, reinstalled, nothing worked. The apps just FC'd no matter what I did. So I went back to TWRP and switched slots. Then I was caught in a bootloop. Ended up flashing latest factory image with the flash all script.

Ever since chainfire retired (no SuperSU anymore), there is force encryption and stuff plus I have to use magisk I have so many problems whenever flashing ROMs, updates or whatever - as it was on my Oneplus 5T and now Pixel 2XL. It really spoils the fun sometimes, as even the detailed how-tos from devs and supporters just do not work and things screw up.
[Google Pixel 2 XL Guides, News, & Discussion] ridobe:
I have none of these issues. I also leave everything encrypted at all times. Only problem I see with your method is the order. Magisk comes after the kernel.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Follow the 9x guide in my sig. At the bottom of that OP is a step by step to upgrade from 9x to latest 9x factory image.

I used all the latest twrp, flash kernel, and magisk, and I haven't hit a single snag. Safety net passes and "preserve force encryption" is unchecked in Magisk manager (it matters not to me whether I'm encrypted or not) but just stating the status of my most recent install.
[Google Pixel 2 XL Guides, News, & Discussion] chazall1:
I followed the same order and have 0 issues.
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
It's not just the order that's important, it's the multiple reboots. Don't just install everything back to back and expect everything to work right.
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
Not exactly true. It's a finicky device. I did the sideload, rebooted and did twrp, flash kernel and magisk all in one go, no issues at all. Might not work next time or work for everyone, good ol pixel phone has serious attitude issues lol.
[Google Pixel 2 XL Guides, News, & Discussion] ranasrule:
So its not possible to downgrade from Pie 9.0 to Oreo 8.1 ?
[Google Pixel 2 XL Guides, News, & Discussion] Reechings:
Yeah you can, I don't know why this has been said. Just make sure you're unlocked and flashing a factory image. You won't be able to save data though.
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
After booting TWRP on a new image, I always queue up TWRP, EX Kernel, and Magisk zips and install all 3 before booting system for the first time. This method has never failed me. Give it a try.
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
Just a heads up as TWRP 3.2.3-1 would not decrypt at one point for me.. Started with Aug update, Magisk 17.1 , Flash 3..07 and Magisk Manager 5.9.1. Still on stock recovery. Ran Sept 9.0 update, restarted OK. Fastbooted TWRP 3.2.3-1 img and PIN would not enter, rebooted system OK. Removed security, fastbooted TWRP img again and flashed Magisk 17.1. Restarted OK. Then Flash 3.07 from Franco Kernel Manager, also OK. Reinstalled security and apparently OK now. Maybe I should have installed Flash's kernel before flashing Magisk.
[Google Pixel 2 XL Guides, News, & Discussion] bartoszkasprzyk0906:
Hello. Can you unlock the bootloader for the verizon version?
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
https://xdaforums.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
[Google Pixel 2 XL Guides, News, & Discussion] iamjimmy:
That is what I always do. In TWRP - queue up TWRP, Kernel and Magisk. But can we use this method to update from Oreo to Pie? I'm on Android 8.1 July Security patch and want to update to Android 9 September patch.
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
[MENTION=5601653]iamjimmy[/MENTION] Yes. That is exactly how I upgraded from Oreo to Pie. There were no surprises. Just make sure you use the kernel specific to Pie. That, and there is a new update to the fastboot/adb binaries.
[Google Pixel 2 XL Guides, News, & Discussion] iamjimmy:
Deleted
[Google Pixel 2 XL Guides, News, & Discussion] iamjimmy:
Perfect. Many thanks and much appreciated.
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
command box not working

I have downloaded all files needed for rooting pixel 2 xl form this thread and have been unable to get the command box stay up pops up then goes away. On the root guide it says that adb and fastboot will be in same folder. On the files downloaded from the link they are seperate do the files need to be in the same folder? How do i need to have the setings on my PC? I am running the latest version of windows with the latest updates. I have searced the thread and found no info on this. pixel is not updated to pie
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
Below is a pic of my pc screen, I have the folder on the desktop. What OS are you running on you pc? Also, windows 10 deleted my command prompt and replaced it with powershell instead, I had to manually add command prompt, make sure you have that as well, I noticed it was gone because I would get a quick pop-up when I tried to open the command prompt.

ADB and fastboot are all in the same folder, just have to extract the platform tools folder, works best on the desktop instead of in a sub folder (just my opinion).

Hope this helps
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
folder was placed on desktop

windows 10 home version 1803 os build 17134.8

How do I add the command prompt? (All i get is a quick pop up and it goes away as fast as it popped up)

I have unzipped the entire folder already. The last phone I rooted was a Skyrocket so its been awhile.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
While in the folder with the fastboot application and your files to fastboot, highlight the URL / address line and type in CMD and hit enter.
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
What I had to do... https://www.google.com/amp/s/www.wi...-window-here-back-context-menu-windows-10?amp

Google has a lot of info on this too
[Google Pixel 2 XL Guides, News, & Discussion] bnbagiz:
this is bugging me for 2 hours now. i have adb installed but it says its version 0.0.1-4500957 and the information at the beginning is saying i should have installed at least vers. 26.

so i stumble across the official android developer site and installed android studio, since there is no sdkmanager provided (?! i guess) .. at the end i am confused.

can someone please provide not outdated news?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Are you getting SDK from here? https://developer.android.com/studio/releases/platform-tools#downloads

The latest version is 28.0.1
[Google Pixel 2 XL Guides, News, & Discussion] bnbagiz:
thanks, this helped my confusion!

another question I got:

I am running the latest build on my pixel 2xl / PPR2.180906.005, bootloader locked, not rooted of course.

after setting up the first couple steps and unlock my bootloader etc., is it necessary to flash the factory at all? is it possible to continue with the rooting process "rooting with Magisk"?

If that's not the case and I need to flash the factory image, which method is the right one "Updating to a new release (factory image)" or "Clean flashing a factory image (wipe everything)"?

I am confused because I am on the latest version of Android so far, so this would not be an "updating to a new release". so I assume I should do a clean flash with the last method?

Thanks for helping out!
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
If you're already running the Sep update, then you don't need to flash the Sep factory image (but why not be a crack-flasher and just do it because it's fun and gives you practice for when you will need to do it:) )

You'll still need to temp boot into TWRP.IMG via fastboot to flash magisk.zip

I believe this will get you what you want which sounds like stock factory image with root.

For more detailed steps, follow the "update" link in my sig...
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You do not need to flash the factory image again after you unlock the bootloade. However, your device is going to get wiped when you unlock it, so backup whatever you can to your pc. Once your unlocked, you can then fastboot into twrp, and flash your kernel and root :good:
[Google Pixel 2 XL Guides, News, & Discussion] ranasrule:
Does this mean that it isn't recommended to flash TWRP permanently and just boot it using fastboot boot <path_to_twrp_image> when required?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Depends on who you ask. Personally, I install twrp, and the latest version has been working fine for me :good:
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
I installed it as well, flashing kernel updates on the go is a great option to have.
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
The latest version of TWRP (3.2.3-1) should have fixed the issues with decryption, and everything should work properly now.
[Google Pixel 2 XL Guides, News, & Discussion] matekaneve:
I would install twrp as well. If something goes wrong and let's say you need to flash the Magisk uninstaller or flash anything through recovery and you don't have access to a pc then you're basically screwed. It doesn't cause any harm to have it installed, just makes your life much easier in case of any trouble happen. ??
[Google Pixel 2 XL Guides, News, & Discussion] AwkwardUberHero:
Just updated to P from O last night. I'm wanting to take the leap to and try to root my 2XL.

Reading through this, I'm not fully comfortable, but I'm semi confident I can make this work.

Two questions;

1. Is there a video anywhere that shows these steps? I do better with a visual example.

2. I'm just wanting to root with a stock image. I've read that using a custom kernel can help with better battery life or speed up your device if you want better performance, causing in what you prefer.

I'd like to go the route of battery life. Which kernel with be best for that, and where in the process does one flash the kernel?

Thanks everyone!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Hey bud, so, your ready root and roll. I'll do my best to help out.

Questing #1....not that I'm aware of. Although, using the instructions isn't that difficult, and I think you learn more by reading and doing as compared to watching a video.

Question #2.....kernel and battery life are just too subjective to be technically accurate. There's just too many differentiating factors between users. I will say that I've used all the kernels available, including stock, and really can't tell the difference as far as battery life goes. Although, my 2 favorites are Flash and Ex kernels.

As far as installation goes, if your bootloader is unlocked, and you have your SDK platform-tools up to date, and, all your necessary files in your platform-tools folder, your ready to roll.

I would recommend removing your screen lock security, fastboot into twrp, flash the twrp installer zip, version 3.2.3-1, then flash your custom kernel, and boot up to verify your OS is working properly. Then, go back into twrp, and flash your magisk 17.1 and then boot up, and you should then be rooted.

Now, don't freak out if things don't go as planned, it happens to all of us at times. Just let us know what your situation is, and you'll get lots of help. Now go have some fun :cool:
[Google Pixel 2 XL Guides, News, & Discussion] AwkwardUberHero:
Thanks Badger! I'll try and see what I can get done in an hour or so, let me coffee up for a bit and then I'll see what I can do.
[Google Pixel 2 XL Guides, News, & Discussion] AwkwardUberHero:
Before I go about this, wanted to check something. I am doing this on a Mac, which is running Parallels 14 and a Windows 10 virtual machine. The Macbook has only USB C (thunderbolt 3) ports on it, which is just like the cable that came with the phone. I have read that some users have had issues with the device being recognized on a USB C cable, and had to use a usb 2.0 to usb c female end. That part worries me.

Has anyone tried this with a virtual machine, on a mac that only has USB C (thunderbolt 3) ports? Want to get all of these things checked before I test this out.
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
If you type this in your command window while in your extracted platform tools folder "fastboot oem device-info" without the quotes, it should show your phones status info, if it does, your cable, USB and other settings can see it just fine and you should be good to go.
[Google Pixel 2 XL Guides, News, & Discussion] infatality:
Is it possible to use twrp to flash OTA zip rather than using adb sideload? I'm currently on Android 9 stock rooted with magisk, twrp installed, on flash kernel.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Absolutely yes. You'll likely have to fastboot twrp, and flash root again. But that's about it. I would also recommend disabling screen lock and substratum themes before you begin as well. Not to mention that it's always a good idea to back up your data to your pc, just in case things go awry :good:
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
Also, TWRP has a built-in method to sideload OTAs. Under Advanced, select ADB Sideload. It will then prompt you that's it's waiting for the ADB command to come from your PC. That's the way that I've always done it.
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
I've looked and not found directions for sideloading the OTA with TWRP. Always used the Factory Image .bat file with the -w removed. Sideload seems so different for me that I'd like to see a detailed step by step. Do you know of a "for dummies" post here on xda? I'm up to date and comfortable with adb and fastboot. Do I need to install the TWRP zip? I get the impression there are advantages to sideloading as opposed to updating with the Factory Image.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
If your good with the fastboot method for updating, why change it? I've used both methods, and I prefer fastboot myself. I've not seen any benefits of one way or another. They both get the job done :good:
[Google Pixel 2 XL Guides, News, & Discussion] xDakos:
So again the full guide is just

flash all with or without -w

set the phone up

make sure your bootloader is unlocked and enable usb debugging and open adb

adb reboot bootloader

fastboot boot twrp.img

flash (kernel you dont really need it but nice to have) and magisk you can do both without restarting dont install the twrp app

restart and youre rooted without a problem
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yeah, you've pretty much got it. Just unlock the bootloader first of course. And keep OEM unlocking and USB debugging on all the time :good:
[Google Pixel 2 XL Guides, News, & Discussion] kickenwing13:
Successfully Installed Magisk

Now what?") This is the first time I've done any of this stuff without using a toolkit. First time doing anythign since the 6p...... So generally, what can I do next? what's the real point? I have root confirmed. where do I go now and what are the real benefits at this point in android in rooting ?
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
You should have gotten the answer to that question before rooting, otherwise there's no point.

What do you want to do? You can now install any apps which require root. Since Magisk is installed, you can install Magisk modules.

Are you asking for suggestions on how to take advantage of root, now that you have it?
[Google Pixel 2 XL Guides, News, & Discussion] kickenwing13:
I mean, I know I can run root apps, I've learned a little about modules but don't know how it relates to Xposed . I'd like to install custom ROM. Do I still need twrp I assume ? Process Seema different than it used to be. Used to unlock . Root. Twrp. Install room . Success. Seema different now .
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
Xposed is unrelated, but there is a Magisk version of Xposed. Xposed is basically a Magisk module now.

I wouldn't install anything you don't need. Don't bother with Xposed, if you don't need a particular module. Personally, I wouldn't even have bothered with Magisk if I didn't want root access. I'm also happy with having a rooted stock ROM.

If you already know you want to install a custom ROM, you don't need to waste your time with rooting & Magisk, Xposed, etc. Just boot to TWRP and install the custom ROM.
[Google Pixel 2 XL Guides, News, & Discussion] kickenwing13:
Very helpful man. These are the things I need to hear. Been out of the game too long. Thanks you so much ..

You don't need to be rooted to install rooms anymore ? So should I flash stock and get rid of magisk? Then just install a rom . ?
[Google Pixel 2 XL Guides, News, & Discussion] Reechings:
If you're interested in flashing custom all you have to is flash the stock image (8.1,9) that the custom rom matches with then boot TWRP and factory reset then flash custom.