yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] Carmenlove:
Help!

I have a Pixel XL - was rooted with Android 9 - Magisk, twrp, etc. Last week, I accidentally took an OTA update to Android 10. Lost root, phone was working though.

Started the root process again here.

I have flashed factory Android 10 images for the last 3 updates (marlin-qpa1....)

every time, the phone just ends up in a boot loop. from the unlocked warning screen - to the Google screen with unlocked padlock on the bottom - back to the unlocked warning screen. I cannot get a factory load to boot for some reason.

No problem getting to the bootloader and flashing stuff, the flash-all's say they completed - all "OKAY[ ]"'s

There are messages about things the archive does NOT contain, like 'dbto.img', 'dt.img', 'recovery.img', 'vbmeta.img' and so on. I'm NOT SURE if that is normal or not. There are many things it does find and send to the phone with OKAY's

Can anyone give me an idea of what I might be doing wrong?

Should I try to go back to Android 9?

I know better than to lock the bootloader at this point- learned that lesson the hard way two years ago.

Any help would be greatly appreciated, and even financially compensated too.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
First, there are only two Pixel XL Factory Images for Android 10: September and October 2019.

Second, You wrote you took the OTA to Android 10. So, why are you trying to flash/install the Android 10 Factory Image?

Try this:

- Extract the boot image from the Factory Image, see #6 in the guide. Note: If the OTA you took was September the extract the boot.img from the September 2019 Factory Image.

- Flash the boot.img to both slots.

fastboot flash boot --slot all boot.img

- If it boots, do #9 to root/reroot.
[Google Pixel XL Guides, News, & Discussion] flash713:
I am about to take ota to 10 then extract boot.img, patch using magisk manager and do the fastboot boot twrp.img then flash patched boot.img.

Does anyone have a boot image for latest Android 10 that's patched or not patched handy that they can upload? I am without a computer so i am using fastboot from a phone that I normally use as a security camera using osmosis's static fastboot zip. Which works excellent btw. ;)

If anyone does have a patched or non patched boot image from latest Android 10 factory image for XL please share and what month it is from , please. I appreciate all the info here and although I am a bit late to the Pixel party I've owned all Nexus devices ever made and got a new XL for 135! Absolutely love it!! ?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Are you still on Android 9 (Pie)?

Try this:

- Take the Android 10 OTA.

- Open Settings ==> About phone ==> Scroll down to Build number. If it is: QP1A.191005.007.A1

- In the guide Under 'prerequisites' download the October 2019 factory image to an empty folder on your phone. Make a temp/hold folder.

- Do #6A to extract the boot image. Once yo have extracted the boot.img, you can delete all the other files in the folder.

- Patch the boot.img you extracted with Magisk Manager by doing #9 D-G.

- Then using osmosis's static fastboot zip. Instead of fastbooting TWRP, use it to do #9 L.
[Google Pixel XL Guides, News, & Discussion] flash713:
As soon as I get home (got called in to work) I will follow this list and then report back in this same post. I appreciate your time.

I purchased a new XL and i am currently on 8.10 ? !
[Google Pixel XL Guides, News, & Discussion] Carmenlove:
Thank you for trying to help me!

OK, to the first, maybe I don't know what I am talking about. These are Pixel XL images I was referring to:

10.0.0 (QP1A.190711.019, Sep 2019)	Link	3f4a20d...

10.0.0 (QP1A.190711.020, Sep 2019)	Link	2db5273a...

10.0.0 (QP1A.191005.007.A1, Oct 2019)	Link	c27241e0a...

I know for sure, after the OTA completed, the phone said it was running the .020 build. Well, 95%. I'm 100% sure it was one of those two, .019 or .020. It was NOT the October version.

To the Second question: Because I am an idiot, I didn't know what was possible. I have rooting Android phones going all the way back to Donut and Motorola RAZR's. Many, many generations now. But I just follow the guides, I have never really understood what all is going on in there. I just do what the guides have said, and been mostly lucky so far. I was not sure what to do this time around. I have always had the best luck starting from a fresh factory image, totally clean and freshly installed. So that is what I tried first.

First I tried to install the factory image .020, the one I thought the phone had taken the OTA version of. When that boot looped, I next tried the October 2019 version, same boot loop. FInally I tried the .019 version, the one before the OTA, I thought I had, same result.

I just extracted the boot.img from the .019 factory. That is the last factory image I have loaded

>fastboot flash boot --slot all boot.img

Sending 'boot_a' (30989 KB) OKAY [ 0.788s]

Writing 'boot_a' OKAY [ 0.651s]

Sending 'boot_b' (30989 KB) OKAY [ 0.789s]

Writing 'boot_b' OKAY [ 0.598s]

Finished. Total time: 3.410s

Same boot loop.

I have tried it over and over, flashing the various boot.img files on top of the various versions of the factory image I have installed and nothing works. It turns on, gives the bootloader warning, then show the google logo for about 30 seconds and then repeats.

So frustrating. Any other ideas? I can't seem to get to recovery mode to try adb sideloading the OTA image either.

Is there something about installing newer bootloaders that makes it impossible to go back to old ones? Could I try going back to Android 9 and one of those facotry images and bootloaders? Could that even work?

Thanks for your help. anything at all is appreciated.

CL
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=4973996]Carmenlove[/MENTION]

First, please accept my apology. I forgot September had two factory images: QP1A.190711.019 and QP1A.190711.020.

Second, check which factory image is installed: open Setting ==> About phone ==> Scroll down to Build number.

Then, flash the boot.img of that factory image to both slots.

Third, if the second option doesn't help, do #4 'Keep Data' with the the October Factory Image: QP1A.191005.007.A1. You should get an error, please post the error.

Did you ever get out of the boot loop?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Wow, 8.10.
[Google Pixel XL Guides, News, & Discussion] flash713:
Device born date on my marlin was August 2018. I'm on latest 10 now October and patched boot.img using magisk manager from factory image. Soon as I get back to my phone with fastboot I'll follow through and report back...
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Two things:

One, if device born date is August 2018. How can the

"Android Security Patch Level" be July 5, 2018?

Two, is the bootloader unlocked on your Pixel XL phone?

How to check if bootloader is unlocked: Boot fastboot mode (see #1 B in guide). It should read 'Unlocked'.
[Google Pixel XL Guides, News, & Discussion] flash713:
I just tried the fastboot flashing unlock and it doesn't work... At times I've rooted phones using this same type method and it's worked and sometimes it doesn't. Pictures are what termux says after I type unlock command. I tried terminal emulator and termux multiple times. I will serious fly to where the guy is who sold me this phone and beat his ass if it's a Verizon because he confirmed it was not when I purchased it and was not a refurbished either .... Oh and I made sure it was connected first. I did the fastboot devices and device # showed right away.
[Google Pixel XL Guides, News, & Discussion] flash713:
I got it using the old school nexus "fastboot oem unlock." Lmao. ;P

When I try and flash the boot image it says --slot is an unrecognizabled command in both terminal emulator and termux. :/ Guess I'll have to get a computer for that. Otherwise it would only flash to one slot.... I'll hold off on that till I get my laptop going again unless there's some other command I can try and get it to flash the boot.img to both slots. Sorry I took up so much space on the thread. I'll try and wipe them out to a single post.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
That's strange it should have been "fastboot flashing unlock". I think I know why you are getting the error for --slot and why you were able to use "fastboot oem unlock".

You need the latest version Of SDK Platform-tools r29.0.4. on your computer. There is a link in the guide for it see "Prerequisites c.". I don't know if it will work on your phone. It might extract it on your phone, put the magisk_patched.img in the Platform-tools folder. Then open Terminal Emulator ==> change director to the Platform-tools folder ==> type SU ==> then type: fastboot flash boot --slot all magisk_patched.img

No worries about the post.
[Google Pixel XL Guides, News, & Discussion] flash713:
If I wanted to be on a rom and rooted couldn't I boot twrp 3300 then install Lineage 17 w/gapps? Correct me if I'm wrong PlEaSE (I already bricked another device..) ? boot twrp, wipe data and system, flash lineage w/gapps, flash twrp zip, reboot recovery, flash magisk root v20., reboot system.? Isn't that the proper install method far as custom roms go on 10? Appreciate your replies.

I am going now to attempt to update on termux and see what happens ...brb
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=6658916]flash713[/MENTION]

Follow the instructions in Ithe lineage OP to install lineage 17.

What are you updating in termux?
[Google Pixel XL Guides, News, & Discussion] flash713:
I searched and located parts of the sdk that can be updated through commands... Maybe I should chill. I feel like I'm gonna end up screwing things up. I'll hold off. Have to go make a copy of Ubuntu today so that I can get my laptop back up running again. Thanks again man for the help.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
I don't think I've ever read about updating parts of the SDK. Would you mind posting the link to material you are referring to?

I think chilling is a good idea, at least until you laptop is working. :)
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
- Is your bootloader unlocked?

- How to check if bootloader is unlocked: Boot fastboot mode (see #1 B in guide). It should read 'Unlocked'.

- Do you have the latest version Of SDK Platform-tools r29.0.4. on your computer? There is a link in the guide for it see "Prerequisites c.".
[Google Pixel XL Guides, News, & Discussion] flash713:
https://github.com/termux/termux-packages/blob/master/scripts/setup-android-sdk.sh
[Google Pixel XL Guides, News, & Discussion] Carmenlove:
Yes, I have been using the latest version of the SDK from the start. In fact, every time I try a new factory image, I have been unzipping the latest SDK tools in that folder, then I launch an admin command prompt in the folder I am trying to install a factory image from, and I run everything from there. So that was not it.

I have several folders now:

M:\Pixel-XL 10 root\TRY HERE OCT> - This is the October factory image!

M:\Pixel-XL 10 root\TRY 2> - This is the Sept .019 factory image.

M:\Pixel-XL 10 root> - And this is the Sept .020 facotry image.

Three folders, with fully separate copies of the SDK tooks, factory image zip, unzipped and all the right files in the right places (android-info.txt, bootloader-marlin-xxx.zip, flash-all.bat, boot.img, etc...) I have everything isolated to make sure I don't screw up.

UPDATE: I GOT IT WORKING!!!

It was bothering me that the first try of writing the new bootloader was failing somewhat randomly. I would run it, it would fail. I would up-arrow and just run it again, and it would work. That bugged me. So I decided to switch USB ports on the PC. I had been running on a USB port that was daisy-chained off a multiport hub. I decided to try a port that was directly connected to the motherboard of the PC. THAT DID IT! I completely installed the Oct A10 Factory image and rebooted, and it WORKED!!! I am back in business!

Well, I have a working phone at least. I am not rooted yet. Now I have to root it again with Magisk. But I have a working phone, so I am feeling confident again.

All of this, and I all I really want is to disable the hot-spot tethering check. I hope I can still do that in A10 with magisk. We will see.

Moral of the story - the USP ports are finicky and just because it says everything is working, the port DOES make a difference!

Thanks for your help. Just tell me where I can show my gratitude in a more meaningful way...
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
To quote a movie line...damn it Gump you're a...damn genius... rotflmao

It is always the simplest solutions that solve our major problems.

I'll have to remember to suggest changing the USB port/cord when flashing problems occur with Android 10.

Good job, I'm glad you found the solution to the problem and shared it with the XDA Community.

You already have shown your gratitude. If you want it to be "more meaningful" Press the "Thanks button".
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Got it, it is a termux thing.:)
[Google Pixel XL Guides, News, & Discussion] flash713:
I couldn't seem to figure out what to do to get those parts to update in termux for sdk to see if I could get the --slots all command to work and be recognized. ?? I will figure this out or find an alternate way to get a flash on both slots and succeed at this, if there is a way. Going to read again now and see what I can find out... ✌️

October 23, 2019- 10:29am- Central Time

Update: I'm rooted, finally. I was able to unlock my bootloader, boot twrp, install twrp installer zip, flash magisk canary zip and then flash my magisk patched boot.img that I patched previously using magisk manager. Did it all using termux along with Osmosis's static fastboot magisk module from my old Samsung On5 phone to my Pixel XL. ?
[Google Pixel XL Guides, News, & Discussion] aholeinthewor1d:
**edit - delete**

---------- Post added at 05:11 PM ---------- Previous post was at 04:19 PM ----------

Thank you for this guide! I have an OG Pixel with unlocked bootloader. Haven't been paying attention to XDA for the past year. Updated to Android 10 and after seeing how there is no EASY way to switch the back button to the right side I realized I wasn't rooted anymore and I NEED to switch the buttons. I've only used Magisk once in the past but I was able to follow the guide and get my phone rooted again. Definitely a little more confusing/complicated than it's been in the past but still easy enough. I miss being able to just fastboot boot TWRP and then install TWRP and SU. I am pretty sure I am flashing back to Android 8 anyways pretty soon.

For anyone wondering I just used the latest stable Magisk Manager v7.3.5 and it worked fine. Didn't use Beta or Canary? or whatever that is
[Google Pixel XL Guides, News, & Discussion] Lemnefresh:
Unlock bootloader for root only

This might be a dumb question, but if all I want is root access, is it necessary to unlock the bootloader? Only reason I ask, is because I bought a used Pixel XL from Amazon, and it turns out it's the Verizon variant and the bootlader can't be unlocked.
[Google Pixel XL Guides, News, & Discussion] flash713:
Yes bootloader must be unlocked to root.
[Google Pixel XL Guides, News, & Discussion] Lemnefresh:
I figured as much. It was worth a shot. Thanks
[Google Pixel XL Guides, News, & Discussion] sudoxd:
for those running the october patch, i very highly recommend running the latest elementalx kernel with it as it greatly increases stability and greatly decreases the rate of random reboots i was having on the october patch with the stock kernel, i dont know if custom roms which are running the october patch have this issues but if they are then i recommend you flash elementalx and see what happens.

the twrp installer does **** all when on android 10 atm, just boot to twrp and flash what you need it works fine.
[Google Pixel XL Guides, News, & Discussion] LeMoise:
[MENTION=4810220]Homeboy76[/MENTION] Thanks man for the guides. Been rooting my Pixel XL with your help since OS 8.
[Google Pixel XL Guides, News, & Discussion] NewbRooter89:
I just got my pixel XL about a week ago, running P, stock rom. I'm just curious if it's worth upgrading to 10? Will edxposed still work?

I already feel like I haven't been able to do too much with edxposed on P and an thinking it will be worse on 10. Thanks a head of time!
[Google Pixel XL Guides, News, & Discussion] uservssystem:
So? Did it work?
[Google Pixel XL Guides, News, & Discussion] NewbRooter89:
I haven't updated to 10 yet. I was asking if it's worth it to update to 10. I already have root and edxposed and don't want to lose them if I update.
[Google Pixel XL Guides, News, & Discussion] crackerjack1957:
I would stay on 9 until they release a working TWRP for 10.

No more security updates for 10 anyways after December, might as well run another rom if keeping Pixel.
[Google Pixel XL Guides, News, & Discussion] NewbRooter89:
I was just reading that yesterday. Should I just go custom rom then? I've been thinking about doing that anyways.
[Google Pixel XL Guides, News, & Discussion] lichan:
For those with edxposed who want another option, look into TaiChi (also on XDA) as another Magisk module for xposed. It passes SafetyNet with no problems on Pie (which I use it on over edxposed). It may work better for you.
[Google Pixel XL Guides, News, & Discussion] psychokilla209:
OEM Unlocking issue

I have the Pixel XL with Android 10 and I have been trying to root my device, but I am stuck with an error "Please unlock your device to enable this command." The "OEM Unlocking" is grayed out. I have been searching how to enable it, but no luck. Anyone have any idea how to go about it? Thanks in advance.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Does the IMEI number start with 35?

If yes you cannot unlock the bootloader.
[Google Pixel XL Guides, News, & Discussion] Zaheen Jamil:
I have an unlocked bootloader and a custom ROM with magisk and and a custom kernel. My IMEI also starts with 35, my option is grayed out but my bootloader is already unlocked. My pixel isn't from Verizon, what does this mean?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Yes, your 'OEM unlocking' option is probably grey out in the on position and it was unlocked prior to September 2019.

There is currently no bootloader unlock method for the Pixel XL if the bootloader is locked.
[Google Pixel XL Guides, News, & Discussion] Zaheen Jamil:
To me, it looks like the off position, that's why I got confused. Here is what it looks like
[Google Pixel XL Guides, News, & Discussion] miketucky350:
I just purchased a New in box Play Store Pixel xl. Well the ad stated that it was a Play store model and was bootloader unlockable. After peeling back the plastic I boot it up with NO SIM CARD. (Im on verizon) I it booted up with no account I noticed that OEM unlocking was greyed out. So I connected to wifi and instantly It let me check it. My IMEI starts with 35. Did I get a verizon model and get lucky? Homeboy76 are you saying that if I re lock it once updated that you cant unlock again? Of course Ill never lock the bootloader.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
You're right it is in the off position. So, I guess it is only Pixel XL that were purchased from Verizon that the bootloader can not be unlocked. :(

[How-to] Unlock bootloader on Verizon Pixel/XL by

The link above is full of examples of people who can not unlock their Verizon Pixel XL bootloader.
[Google Pixel XL Guides, News, & Discussion] G_Nious:
Does each set of instructions have to be followed if my goal is to just root with Magisk? What can be skipped/is optional? It looks like some sections are blank which has me worried that I won't be able to complete these.
[Google Pixel XL Guides, News, & Discussion] dfx12345:
From memory: 1) unlock bootloader, 2) flash stock image, 3) extract boot.img, 4) install Magisk APK, 5) use Magisk to patch boot.img, 6) flash patched boot.img
[Google Pixel XL Guides, News, & Discussion] flash713:
If you already have fastboot and adb and all setup then you can skip that just make sure your ADB and Fastboot versions are: 29.0.5-5949299. If you aren't planning on using stock rom you can always boot recovery and flash a custom rom or a GSI. These A/B devices are different. You'll understand soon if not already. Just do as much reading as you can. I'm definitely not the sharpest tool in the shed but always better to understand so you really get it and don't have issues later..

**Make sure you don't flash anything using TWRP when you have a lockscreen set on your device. Always set lockscreen to "NONE" before you flash anything using TWRP, for now anyway.... The TWRP guys are working on getting a 100% working recovery for Android 10 for this device and currently aren't supporting 10 just yet until they get some things figured out but I use TWRP 3.3.1.3 and it works for me.

*** And don't "flash" recovery with fastboot instead "boot" recovery using fastboot: fastboot boot twrp-3.3.1-3.img (enter) If you end up forgetting and you flash TWRP using fastboot the fix is to flash factory image.
[Google Pixel XL Guides, News, & Discussion] G_Nious:
Thanks for the information. I've actually decided to just not do this on my main phone, as I'm not really sure I want to reflash/factory reset. Now trying to look into if a Note 4 can work with Magisk.
[Google Pixel XL Guides, News, & Discussion] flash713:
And there are about nine million Verizon Pixels for sale across the world rn ? and watch out because some of those guys on the net will try and slip you. Maybe they don't know, maybe they do know but all refurbished Pixel 2 & 2 XL have encrypted bootloaders too from what I've read on here, reddit and Google's help forums. Then we have the unlocked Verizon Pixels. lol. Can be quite a pain in the ass shopping for one online, was for me. I read too many horror stories about people who ended up with encrypted bootloaders after they sent them in to get fixed (2&2xls) and getting slipped a VZN model...etc.

---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------

Sure it can. My old Samsung Galaxy On5 uses magisk and it wasn't even a word back when that bad boy came out. ?
[Google Pixel XL Guides, News, & Discussion] MattO:
Hey, first off thanks for the guide. I have been experiencing the same boot issue that a few others have. I am on the latest version of everything, android sdk, latest factory image, latest magisk (tried both stable and canary). I can patch the boot.img with magisk and after i flash the magisk_patched.img, i reboot the phone and it sticks on the google "G" with the progress bar underneath it. I am on the same build number as the one I downloaded ending in 007.A1, using the same boot.img from it. When it hangs up, I can flash the same boot.img that I used magisk to patch and reboot the phone and it is back to normal and goes right to the lock screen. I could be wrong, but it appears that my issue is with the boot.img being patched with magisk somehow. Any advice or help is appreciated, thanks.

edit: When it sticks on bootloop, i can still use a command prompt to "adb reboot fastboot" and then flash the stock boot.img and it boots normal.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Were you rooted on the September factory image?

Did you fastboot flash boot --slot all magisk_patched.img?

SDK Platform-tools r29.0.5?

Read this it might help.