yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] lafester:
Nice
[Google Pixel XL Guides, News, & Discussion] crackerjack1957:
Probably should have used latest Magisk uninstaller before updating to v18.

Magisk v18 & Jan patch working fine for me.

https://github.com/topjohnwu/Magisk/releases
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Or you can use the link in OP #7 B2b to get Magisk's latest uninstaller (it's the same uninstaller).
[Google Pixel XL Guides, News, & Discussion] crackerjack1957:
Guess I should have checked but link had an older date & wasn't sure.........Thanks again for great guide!
[Google Pixel XL Guides, News, & Discussion] vlucchetti:
I went back to December. We'll see what happens for February.
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
Ok guys I need a little help. Here's the situation. Im trying to flash the Dec image buttttt this is what i got.

When i extract the file I have these 6 items in folder C:\SDK\platform-tools_r28.0.1-windows\platform-tools\marlin-pq1a.181205.002.a1

1 . bootloader-marlin-8996-012001-1811131534

2. flash-all

3. flash-all.sh

4. flash-base.sh

5. image-marlin-pq1a.181205.002.a1

6. radio-marlin-8996-130181-1808270817

when i type 'flash-all' in my command i get this error message......

flash-all : The term 'flash-all' is not recognized as the name of a cmdlet, function, script file, or operable

program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

At line:1 char:1

+ flash-all

+ ~~~~~~~~~

+ CategoryInfo : ObjectNotFound: (flash-all:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

Suggestion [3,General]: The command flash-all was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\flash-all". See "get-help about_Command_Precedence" for more details.

what am i doing wrong here? I did it when I first got my pixel last summer but I cant seem to find/figure out how to replicate.

plz help, thanks...
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
"C:\SDK\platform-tools_r28.0.1-windows\platform-tools\marlin-pq1a.181205.002.a1"

- Did you open a Command Prompt (#1) in the above folder?

Are the files fastboot , adb, etc in the above folder.

What happens if you double click flash-all.
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
The 6 mentioned files are the only ones in that particular folder.

Yes I opened the command in the folder, that's when I get the error message.

And if I double click on flash all it says waiting on device
[Google Pixel XL Guides, News, & Discussion] jeffshead:
You may need to edit your Windows system settings so file extensions are visible. Try using "flash-all.bat" instead of "flash-all" if your flash-all file has a .bat extension. Try renaming the folder and files with simple names and remove all dots except for the one dot before the file extensions.

Try CMD instead of PowerShell. One of the first things I do when I build a new Windows system is edit the registry so opening a CMD as Admin is easy peasy. Refer to the following link:

https://www.tenforums.com/tutorials...ndow-here-administrator-add-windows-10-a.html

If you decide to add this functionality to your system, you just go up one level and right-click on the folder that contains the bat or exe file, select the "Open CMD..." link in the context menu and run your command. This way you avoid path typos.

Does your Windows system actually see the device? Refer to the link below:

https://www.youtube.com/watch?v=4LHh9OLxAG8
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
yes my laptop sees the phone because i can do other adb commands but for some reason this isnt working
[Google Pixel XL Guides, News, & Discussion] jeffshead:
Info about PowerShell:

https://superuser.com/a/1251228

Did you try my other suggestions?
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
Ok here's what i just did...

1. went to the folder and made extensions visible

2. opened a cmd prompt instead of using open shell

3. manually booted into bootloader then connected

4. double clicked on flash-all.bat

5. bingo bango go lick a mango it flashed

oddly enough i still have all my apps even tho i am on the stock file, is that normal/right? yes i removed the -w because i do have stuff on my phone that i want(ed)... I just thought it would take away all the apps too and start fresh
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Do you get the error message when you open the Command Prompt or when you type flash-all at the Command Prompt?

- Try using a different usb cable

- Try using a different computer

- Try moving the files in this folder:

"C:\SDK\platform-tools_r28.0.1-windows\platform-tools\marlin-pq1a.181205.002.a1"

to this folder: C:\SDK\platform-tools_r28.0.1-windows\platform-tools.

then open a Command Prompt (#1 in Guide) in that folder and type 'flash-all'. The hypen is part of the file name.
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
no error messages, it just flashed and pushed everything over.

Im just wondering did it complete correctly since i still have my apps even tho i did remove the -w
[Google Pixel XL Guides, News, & Discussion] jeffshead:
You remove the '-w' if you want to KEEP your data. If you did not remove the '-w', you would have lost all apps and data.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=2392121]kinfolk248[/MENTION]

:good:

To help others that may have this problem. Please explain ,exactly, how you got it to work?
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
OHHH it keeps data AND apps.... :-O

---------- Post added at 10:01 AM ---------- Previous post was at 09:58 AM ----------

@jeffshead
[MENTION=4810220]Homeboy76[/MENTION]

thanks, if only I would have known this 3 months ago lol. Im either stupid or you guys are extra smart....lets meet in the middle lmaoo
[Google Pixel XL Guides, News, & Discussion] Dr0idGh0sT:
Hello

I have issue on my Pixel XL

I'm installing magisk and when phone reboots it stucks on boot logo. I have tried 18.0 and 17.1 versions. Phone starts booting and about 2 minutes later reboots to TWRP. When install magisk uninstaller phone powered on normally. Have any ideas?

Also i can't root my phone.

I tried method mentioned in this post. Also tried this methods: https://xdaforums.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886 ; https://techlector.com/how-to-root-google-pixel-and-google-pixel-xl-easiest-method/

So, I need any help to root my device, I have installed latest TWRP and Android is also on latest update.
[Google Pixel XL Guides, News, & Discussion] Dr0idGh0sT:
I have installed Pixel dust ROM, And again, When I'm install Magisk phone stucks on boot logo. What I'm doing wrong?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
- Do #4 'keep data,' in this guide to install the January Factory image.

- Then go to the Pixel Dust OP and follow the 'Installation Guide - clean install' and 'Need to root' .
[Google Pixel XL Guides, News, & Discussion] Dr0idGh0sT:
I have downloaded and flashed January Factory Image. Than booted into TWRP, flashed Pixel Dust ROM and booted normally. But again when I flash Magisk phone stucks on boot logo. I have tried TWRP 3.2.3-1 and 3.2.3-0 ; Also Magisk v18.0 and Magisk v17.1.

I'll tell exactly what I'm doing:

First, Flash Factory Image with flash all bat file. Phone booted normally. I tried to install magisk via TWRP, Booted to TWRP via fastboot and flashed twrp-pixel-installer-marlin, Next I rebooted and tried install Magisk. I got bootloop. I have flashed Factory Image again and tried another Magis version, But bootloop again. I have flashed Factory Image one more time and then booted into TWRP recovery, Wiped data/delvik/system and flashed Pixel Dust ROM. Phone booted normally, But when flashed Magisk I got bootloop again. Then I have flashed Factory Image, Flashed Pixel Dust ROM again, flashad another TWRP version and another Magisk version, But I got bootloop.

So, What I'm doing wrong?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Post the, entire, quote above on the Pixel Dust thread they will help you figure out what is the problem. There is a link to their thread in this guide (Custom ROMS).
[Google Pixel XL Guides, News, & Discussion] Dr0idGh0sT:
Actually, I don't need Custom OS, I need root on stock image. This is why I'm posting on this thread. I returned to stock already. If anyone knows something please help me getting root access on my phone.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Did you try flashing the January boot.img to both slots (#6) > fastboot boot twrp-3.2.3-1.img > install Magisk (#8)?

If yes, ¯\_(ツ)_/¯
[Google Pixel XL Guides, News, & Discussion] Dr0idGh0sT:
Yes, I have tried. I think I'm doing everything right. :eek:
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
I agree I don't know what is causing the boot loops :(
[Google Pixel XL Guides, News, & Discussion] djl236:
Mine was stuck at the Google logo for probably a half hour to 45 minutes. I pressed volume down + power to reboot and when it rebooted, it booted normally into the OS. Saw Magisk was installed too. Ran root checker, verified I had root. Ran SafetyNet and passed and then ran and applied Adblock. Weird but that reboot worked.

Re-cap:

Copied Magisk 16.7 zip to my phone's internal storage (Downloaded from XDA thread. It said included Magisk Manager 5.8.3).

Dirty flash 9.0 image by removing -w from flash-all.bat

Boot into OS, took a few minutes (be patient).

Confirmed was updated to 9.0

Everything good but no root. Just stock Android 9.0.

Boot to twrp.img (I do not install TWRP. I run everything stock but rooted)

Install Magisk 16.7 zip

Reboot

Got stuck on Google logo for 30-45 minutes, don't remember but it was way too long and figured something was wrong.

Rebooted phone via volume down + power buttons

Phone actually reboots into OS.

Check to see Magisk 16.7 and Magisk Manager 5.8.3 are installed. They are.

Run Root Checker to see if phone has root. Phone has root.

Run SafetyNet. Phone passes.

Run Adblock. Apply it and reboot.

Phone is rooted, stock OS, stock kernel, stock recovery.

Definitely something not right with Magisk 16.7 and Android 9.0
[Google Pixel XL Guides, News, & Discussion] LeMoise:
What do you mean something is not right with Magisk 16.7 and Android 9? I've been using 16.7 to root all the developer previews and the official release of Pie without any issues at all. I used the same method you did, fastboot into twrp, flash magisk and reboot without installing twrp, works like a charm.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
First, most of the links in this post are in the OP

Second, if you had search the thread you would have found an eaiser way to root Pie.

Third, did you follow the instructions in the OP?

Fourth, if you did not follow the instructions in the OP, post this information where you got the instructions.

Fifth, the answer to your question are probably on the Magisk BETA thread or Magisk general discussion thread (search). If not, post your questions there.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Key word 'dirty flashed'.
[Google Pixel XL Guides, News, & Discussion] boostedduece:
I flashed 9.0 last night, wiped data with flash all script, booted twrp image, flashed twrp zip, reboot and setup phone, flash the magisk 16.7 beta.

No issues, no bootloops, just used the links in the OP.

Lot's of good info in this thread and your 8.1 guide, thanks again.
[Google Pixel XL Guides, News, & Discussion] SiXandSeven8ths:
And yet, like others before me, I've never been able to get root on 9, trying all the various methods people mention and still end up in a bootloop and the only fix is to reflash the os and start over. Twice it booted but everything was quite broken. Funny thing is though that I had no major issue getting it on 8.1. I got lucky when that happened I think.

What slot are you supposed to be in when you flash magisk? Or does it matter? Does installing twrp screw it all up?
[Google Pixel XL Guides, News, & Discussion] NepoRood:
If you get a bootloop, just flash the stock boot image with TWRP or fastboot. Magisk will be overwritten, I tried with 16.4 because it was on my device. Ended up just getting stuck at the Google logo, so I flashed stock boot with TWRP and rebooted fine (note: TWRP needs to be re-installed).

I then went back to TWRP and used Magisk 16.7 and rooted without issues.
[Google Pixel XL Guides, News, & Discussion] LeMoise:
I wish I knew what to tell you man.

I flashed the Pie update, wiped everything on my phone too so that it was a completely fresh install. Did the initial set up and then rooted. I had to make sure I had NO password/pin because with one twrp could not decrypt my phone in order to write to it. I did NOT install twrp, just used it to flash Magisk. I believe on first boot it was stuck at the logo but upon force restarting it, it turned on, installed Magisk Manager and it was all good from there.
[Google Pixel XL Guides, News, & Discussion] SiXandSeven8ths:
Well, I'm gonna give it a shot again tonight and see what kind of results I get. Wish me luck.
[Google Pixel XL Guides, News, & Discussion] Ringfinger69:
Thank you for all your hard work.

Did a clean wipe (just to be safe), flashed TWRP, Flash Magisk and verified SafetyNet.
[Google Pixel XL Guides, News, & Discussion] salpsuc:
Thank you for this great guide! As always, read EVERYTHING and follow all the steps, got into trouble because I missed the part about removing PIN before trying to install TWRP. Also, curious if Xposed works? If it does, that's great, but if it isn't ready for 9 yet, shouldn't it be removed or at least mentioned it's not updated yet? Regardless, thanks again for your hard work!
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
You're welcome. Good point, I will edit #10.
[Google Pixel XL Guides, News, & Discussion] FreeSoftwareServers:
I like sharing my tech experiences hence why I have a blog/website (https://freesoftwareservers.com), there is a LOT of information in the OP and people may do what I did, read the gist of it and think they are good to go. My post may have been long but that is why I added "TLDR; Use MagiskMGR to download the correct/newest magisk.zip. " I spent hours testing + time recording my trials, then I posted it in the hopes it can help other people save time. Hit Thanks if I saved you time :)

I am running Pixel XL Marilin 128Gb White - Google Store Variant + Android 9 + TWRP + Custom Kernel ElmentalX + Magisk (Root/SuperSU) & I love my phone

---------- Post added at 09:59 AM ---------- Previous post was at 09:54 AM ----------

The real question is:

What did XPosed offer that you want/miss?

Answer: Magisk Modules are the future(.replacement for XPosed) and can/will offer all that you miss from XPosed + a system-less root!

Loving Magisk and excited for where this goes in the future~!
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Your first post was excessive. You can write about your adventures with your Pixel XL in your Blog. All most readers want to know is 'How do I fix my problem?'

Which you answered in 'Run Seven' but it added nothing new to fix the problem.

So if you want to "help other people save time" answer the question without the drama.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Deleted double post.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
You're welcome.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Thank you. I appreciate your, many excellent, contributions to XDA.
[Google Pixel XL Guides, News, & Discussion] woody1:
So, I haven't updated yet, but I noticed that in the OP, Step 7 shows both Magisk 16 and Magisk 16.7 as possible installs. Shouldn't the reference to Magisk 16 be removed, since that version apparently won't work with Pie?
[Google Pixel XL Guides, News, & Discussion] crackerjack1957:
Thanks for effort & updates on this guide!

Just curious if you have found a Dolby Atmos that actually works with Android 9 & Magisk 16.7?

Viper & Ainur working well with AML but miss Dolby.
[Google Pixel XL Guides, News, & Discussion] Aguys:
Hi, my unlocked Pixel using latest stock and rooted. Today, when I was browsing, it suddenly hangs then reboot and it stuck on google logo, can't boot to OS (I think it's bootloop). I can access bootloader, so I decided to fastboot stock firmware and wipe everything and again, it still can't boot to OS (stuck on google logo):confused:.

Then I tried to install a custom rom, fastboot boot twrp.img->wipe data, dalvik, cache, system->flash rom zip, the big problem is while rom on flashing process, after a few seconds TWRP also hangs then reboot (again, stuck on google logo:confused:). I tried many times, many wipes, many versions of TWRP, but I'm facing the same problem, hangs and reboot, I can't install a rom.

Is there something wrong?
[Google Pixel XL Guides, News, & Discussion] Aguys:
Update: i put phone into freezer for few minutes, now i can flash rom successfully via twrp, booted and finish setup process. But if phone gets warm, it hang, reboot, and stuck again :confused: Possible hardware problem??
[Google Pixel XL Guides, News, & Discussion] crackerjack1957:
I would say you just proved a hardware issue.....motherboard/component related.
[Google Pixel XL Guides, News, & Discussion] jeffshead:
Just wanted to pop in and say thanks again, Homeboy76! I just successfully updated to February 2019 patch (without losing any data or settings) with Steps 4 & 7.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Thank you for the feedback:)
[Google Pixel XL Guides, News, & Discussion] ChevyNexus:
Hey all, I tried to update to the Feb update and i keep getting the same error in the CMD prompt. I extracted the file to the ADB folder in my local drive and go to Flash-All and well....the error message arises.

https://imgur.com/gallery/W7pknQ4
[Google Pixel XL Guides, News, & Discussion] jeffshead:
Maybe you downloaded the wrong image file??? I compared the names of the files depicted in your Imgur image to what I have in my folder and they are different. I have a first gen Verizon Pixel XL (Marlin).

Here is a link to the image that I downloaded and flashed:

https://dl.google.com/dl/android/aosp/marlin-pq2a.190205.003-factory-8a9a1ff8.zip

If you used the same folder (that contains ADB and fastboot) for a previous update, did your system actually overwrite all of the image files if you unzipped and saved the new image to the same folder? Maybe the 'flash-all.bat' is from a previous image??? Also, one time I encountered an issue when using the "flash-all" command. I always type out the extension so I use "flash-all.bat" now.
[Google Pixel XL Guides, News, & Discussion] crackerjack1957:
It cannot find the bootloader image.

Must be your 1st time or either you just forgot how to extract files after you downloaded.

Look a 4c on 1st page under instructions
[Google Pixel XL Guides, News, & Discussion] jeffshead:
When you stated that you "extracted" the files I assumed you unzipped them.

Does the folder named "Thaddeus" contain all of the unzipped files from the downloaded image zip and ADB and fastboot?
[Google Pixel XL Guides, News, & Discussion] badabing2003:
I applied #4 and #7 as I always do which has worked great all this long.

I wonder if anyone else encountering this issue with the Feb update and Magisk 18.1

When the phone is booted, Magisk is working fine

After a while Magisk says that it is not installed

Even though all the root apps are still working as root.

So something is wrong in the way Magisk 18.1 is trying to detect if it is installed or the Feb update as changed some things.

Thanks

BB
[Google Pixel XL Guides, News, & Discussion] badabing2003:
Do a dir in the directory you are doing flash_all and post the results.
[Google Pixel XL Guides, News, & Discussion] jeffshead:
No issues for me. I have opened the Magisk Manager app several times after the Feb. update but I have never had it say it's not installed.

Did you flash the latest Magisk uninstaller in step 4 before re-installing the latest stable Magisk in step 7?
[Google Pixel XL Guides, News, & Discussion] badabing2003:
Yes,

in fact I did it in step 4 as well as in step 7

Perhaps I shouldn't have done it in step 7, looking back, to step 7

Perhaps this is a typo and it should say install

Thanks

BB
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=5974571]jeffshead[/MENTION] [MENTION=4851555]badabing2003[/MENTION]

The step for flashing/installing Magisk's uninstaller.zip was put in steps #7K and #8H purposely. Why? Flashing/Installing Magisk's uninstaller.zip removes all Installed Magisk's Module(s), but if you read the Note with #7K and #8H you can keep your module(s) by not flashing/installing Magisk's uninstaller.zip.

There is no typo in #7 K.
[Google Pixel XL Guides, News, & Discussion] 1xdroid:
I'm having an issue I hope someone can help. I updated the software on my phone from Jan to Feb and kept data. Forgot to do magisk uninstall and reinstalled magisk 18.1 and custom kernel. What is the correct order to do this?This guide says select custom kernel then add zip and then select magisk. The magisk web page says to install magisk first then custom kernel? After the magisk install in twrp everything was good, but after reboot no magisk manager. I flashed the boot.img and tried again and still no manager even after magisk uninstall. Will I have to flash boot img go back into twrp and do magisk uninstall and then install magisk again and custom kernal and after reboot if there's no manager, install the magisk manager apk? I haven't tried this yet because I'm not around a pc. Thanks.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Did you check the app drawer?

If it is not there, download Magisk Manager 7.0.0 apk and install it.

If that doesn't work.

I don't know what Kernel you are trying to flash but if if you use EXKM or Franco's Kernel Manager to flash it, it makes things a little easier.

- boot bootloader (#1 in guide)

- connect phone to computer

- fastboot flash boot boot.img --slot all

- Do (edited) #7 in guide
[Google Pixel XL Guides, News, & Discussion] 1xdroid:
I did check the app drawer and it wasn't there. I'm flashing

EX kernal, but I don't use the manager I flash the zip through twrp. Is it better to use EXKM? I will try to install the magisk manager when I get home. If I install the manager do I still have to flash Magisk in twrp? Is flashing the boot.img in twrp the same as doing it in cmd on pc? Thanks for help.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
If you use EXKM to install the kernel you do not lose root.

After, you install the manager use root checker to confirm you are rooted.

If you flash the boot.img with twrp you will remove twrp. I don't think you can flash the boot.img to both slots with twrp.
[Google Pixel XL Guides, News, & Discussion] 1xdroid:
ok I flashed boot.img. Fastbooted to twrp. Installed twrp and rebooted recovery. I selected the magisk 18.1 zip and installed. After restart the manager wasn't there. I tried installing the 7.0.0 manager and it failed, it wouldn't install.

I first ran into this issue because I had a magisk manager update through manager. I did the update and afterwards I had 2 managers there. I Uninstalled the old one through the manager but it removed both. I then tried steps through twrp as we've been discussing. I chose for magisk to hide itself and it repackaged to a new name. I didn't unhide before uninstall. Is that the problem?

Update:I solved my problem by downloading magisk manager to my pc. Put apk into platform tools folder. Opened cmd as administrator,did adb install and it failed because it didn't match the same name as the one installed on the phone. I then took the package name and did adb uninstall. After that i successfully got Magisk installed. Thanks for the help Homeboy76.