Database Info

Root Pixel 3 XL

Edit: Update!
See My Guide: [Guide] Pixel 3 XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + September 2018 Security Patch

Doubtful being that the article's date is from May...

jrac86 said:
Doubtful being that the article's date is from May...
Click to expand...
Click to collapse
Edit: OP updated!

Fake News...

It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Sent from my Pixel 2 XL using Tapatalk

bxlegend said:
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Click to expand...
Click to collapse
Some think the link is "clickbait."
I thought if you installed MM only, you could patch a boot.img with MM. Are you saying that when you install MM it does it without intervention?

Last time I did it you had to get a boot image, transfer it to the device, MM can then patch it, you transfer it back to a PC, flash in fastboot.

Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.

the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too

kachaffeous said:
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
Click to expand...
Click to collapse
Edit: OP updated

TheUndertaker21 said:
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
Click to expand...
Click to collapse
Edit: OP updated.

I'm curious what the new Titan security chip will do for rooting and custom rooms. Sounds like something that if done right it can be flashed, but it could present a roadblock depending on how it was implemented.

Images are up.
Sent from my taimen using XDA Labs
---------- Post added at 08:01 PM ---------- Previous post was at 07:12 PM ----------
Current boot patch doesn't work. John will have his phone today.
https://twitter.com/topjohnwu/status/1052993970303889418
Sent from my taimen using XDA Labs

I found this out the hard way
Thought I bricked my phone; black screen. Finally after holding down the power button for a second it said boot incompatible or something in the bootloader. There was a new message I hadn't seen before on a Pixel bootloader. (It also says "button combo" in that message area if you use the buttons to get to bootloader.)
Current boot patch doesn't work.
Click to expand...
Click to collapse

No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.

Factory images are up

Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
northmendo said:
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Click to expand...
Click to collapse

I think I can still cancel my order but I''m hopeful it wont come to that.

Archangel said:
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
Click to expand...
Click to collapse
Root will come. Give it time

Same tried patching boot.img, fails to boot. Reflashing stock boot.img fixes it. Never really looked at the sizes before, but the patched_boot.img is roughly half the size of the stock boot.img

Android Q Pixel 3 XL ROOT users Q&A

I am starting this thread for us users and experiences while using Android Q. What works, what doesn't. I am not a dev. I am a user. Not here to bash anyone if something doesn't work. @topjohnwu just got root released for this last night.
So one thing I found which I am sure will fixed soon is
SD MAID not working.
Afwall is working.
Systemui tuner working
Button mapper working
I am sure as we go on and they will all work great. But like I said this is just a post what you found thread. If something does work, post it. If something doesn't, post it. Even if someone needs something like an apk. Ask and shall receive. This is a time of helping each other. Not flaming and bashing. Thank you to everyone that has read this and thank you to all the great devs out there and thank you to us users that can exchange information peacefully.

Is it still not possible to write to /system?

w0rdie said:
Is it still not possible to write to /system?
Click to expand...
Click to collapse
Same here. I would think the File Explorer devs would have to update to support Q?

Quickswitch is not working, back button did not work for me with it installed

I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?

kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
I am using a custom kernel so I didn't try to root the stock boot image. But it seems other people are rooting the stock boot image. I would hope they can help you. If I get around to it, I will try and root the stock boot image to see if it works. Someone should be able to help. Custom kernel roots just fine

kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL

Eudeferrer said:
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin

so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kevdog98 said:
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
Click to expand...
Click to collapse
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked

i42o said:
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
Click to expand...
Click to collapse
Custom kernel. Singular is a go. That's what I'm running. I didn't have to flash both slots. That doesn't make sense at all. I am going to get my lazy ass off the veranda and flash the rooted boot image.
Edit: I have Pie in my inactive slot and QBeta 4 in my active slot. If that makes any sense to you guys?

What's the problem? Flashed to active slot only.

Your doing something wrong if you can't root the stock boot image

When I originally rooted Q I did it ota patch inactive slot. Bootlooped. I just went to factory recovery and wiped data. Has worked ever since. I believe mine was looping to modules not being compatible with Q yet. Also if you grab the Q image and pull the boot image. You can patch it that way too. With Q, it is finicky with apps because of isolated storage. Which is weird because zarchiver still sees all files but amaze only sees root directory. Files app I noticed is saying some files I have are folders and not disk images. Zarchiver says it right still. Fastboot -w to manually remove all data too. Sometimes Titan m drive can cause weird things that is why I go to stock recovery and wipe it that way, wipes the Titan m drive too.

Did anybody already try to flash ainur sound mod and can report if it's working? For me the main reason to unlock bootloader again and start root procedure on Q...

kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Same problem here. Already posted the issue at the Magisk thread.

alex1301 said:
Same problem here. Already posted the issue at the Magisk thread.
Click to expand...
Click to collapse
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304

Golf c said:
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Click to expand...
Click to collapse
Yeah, updated everyhting before getting started.

alex1301 said:
Yeah, updated everyhting before getting started.
Click to expand...
Click to collapse
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.

S8rooted&tooted said:
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
Click to expand...
Click to collapse
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.

alex1301 said:
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
Click to expand...
Click to collapse
Click on advanced settings. And make sure when you did patch it, it wasn't checked. It should not be now with 10. With pie it is. Q will not work with it checked. It will double check system to the other partition. And the slot with magisk doesn't match the untouched slot.

Root Available For Developer Preview

Don't know if you guys saw, but TopJohnWu released a new Canary Magisk for the developer preview.

spotmark said:
Don't know if you guys saw, but TopJohnWu released a new Canary Magisk for the developer preview.
Click to expand...
Click to collapse
Tried it but got a bootloop. Not sure what I did wrong. Used canary magisk manager to patch the factory boot.img and flashed the patched.img with fastboot. Then the bootloop.

Daisymae said:
Tried it but got a bootloop. Not sure what I did wrong. Used canary magisk manager to patch the factory boot.img and flashed the patched.img with fastboot. Then the bootloop.
Click to expand...
Click to collapse
Did you flash to both slots? Maybe that could be the problem?
Sent from my Pixel 3 XL

I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time

Eudeferrer said:
Did you flash to both slots? Maybe that could be the problem?
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I'll give it a try...
Addendum--Tried both slots=bootloop

Daisymae said:
I'll give it a try...
Addendum--Tried both slots=bootloop
Click to expand...
Click to collapse
Works! Downloaded latest MM then patched file. Root!

kngbn79 said:
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Click to expand...
Click to collapse
Try the very latest Canary MM. It works!

Daisymae said:
Try the very latest Canary MM. It works!
Click to expand...
Click to collapse
I tried last night with the newest MM and still ended up with the same result. Not sure if missing something or not but did notice the patched image was half the size of the unpatched one

kngbn79 said:
I tried last night with the newest MM and still ended up with the same result. Not sure if missing something or not but did notice the patched image was half the size of the unpatched one
Click to expand...
Click to collapse
Try again today. He just pushed a new magisk update. (Today)

Anyone tried this on dp3?

I just clean flashed dp3 and downloaded the latest magisk to test. Nothing but bootloops here.
Anyone care to upload their patched boot?
Update: works fine after all. Redownloaded .apk and made sure to select the canary channel in the app settings.

lafester said:
I just clean flashed dp3 and downloaded the latest magisk to test. Nothing but bootloops here.
Anyone care to upload their patched boot?
Update: works fine after all. Redownloaded .apk and made sure to select the canary channel in the app settings.
Click to expand...
Click to collapse
Update: SDK Platform-Tools: r30.0.0

It roots dp4 but after flashing module it unroots but the module is still active and reflashin boot.img wont reroot at that point
edit: Clean flashing DP4 5 times. lollolol. Each time i would have to copy the stock boot over to the phone an let magisk patch it then copy it back over to pc to flash. I could not use the previous patchedboot.img for whatever reason. And if i factory reset it wouldnt work period. The only module im flashing was busybox. but either way this time after clean flash i went to magisk settings changed the name of magisk package an turned on magisk hide. When restarting after busybox install I still had root. SO step in right direction for now

kngbn79 said:
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Click to expand...
Click to collapse
Cant you use direct method? boot the phone with patched boot and flash direct. This method eliminates most issues.

Update: SDK Platform-Tools: r30.0.1

billyt1 said:
It roots dp4 but after flashing module it unroots but the module is still active and reflashin boot.img wont reroot at that point
edit: Clean flashing DP4 5 times. lollolol. Each time i would have to copy the stock boot over to the phone an let magisk patch it then copy it back over to pc to flash. I could not use the previous patchedboot.img for whatever reason. And if i factory reset it wouldnt work period. The only module im flashing was busybox. but either way this time after clean flash i went to magisk settings changed the name of magisk package an turned on magisk hide. When restarting after busybox install I still had root. SO step in right direction for now
Click to expand...
Click to collapse
Weird I flash the dp4 patched boot without issues

On July 5th update, works great! (Though not all modules work due to the removal of /sbin, etc)
?

If you're new PSA: TWRP doesn't work with Feb Update

I just spent the last 3 hours trying to figure out why I couldn't flash TWRP after updating to the February security update. Turns out its apparently a commonly known fact that it doesn't work, but I wasn't able to find a single post specifically about it, so I'm just posting this here so that it hopefully helps someone.
What happens is: you flash the TWRP image, but when trying to boot into the recovery, it brings you to the fastboot bootloader and doesn't let you into TWRP. There is no (as far as I found) direct solution to this. However, you can use a stock boot image and use the Magisk Manager app to patch it, and then install the patched image perfectly fine. That way you still at least have a phone rooted with Magisk

Is there going to be a fix for twrp for the February update? Im asking because I recently bought a essential phone and was looking into rooting with magisk.

Vandan.Patel said:
Is there going to be a fix for twrp for the February update? Im asking because I recently bought a essential phone and was looking into rooting with magisk.
Click to expand...
Click to collapse
Not likely to happen. No updates for this device for the past few years.
Sent from my PH-1 using XDA Labs

DAE1964 said:
Not likely to happen. No updates for this device for the past few years.
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
This might be the wrong thread but how do you downgrade from the feburary update to the January update. Do i need to factory reset my device or any specific instructions?

Vandan.Patel said:
This might be the wrong thread but how do you downgrade from the feburary update to the January update. Do i need to factory reset my device or any specific instructions?
Click to expand...
Click to collapse
Just install the January build from essential it will format the data
Sent from my PH-1 using XDA Labs

DAE1964 said:
Just install the January build from essential it will format the data
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
https://www.essential.com/developer/current-builds
Just to confirm I just flash the January 2020 Release | Q 10 - Q Release 5 - QQ1A.200105.007 to my device with the instructions listed on the site and that is it correct? All my data will be cleared automatically?

Vandan.Patel said:
https://www.essential.com/developer/current-builds
Just to confirm I just flash the January 2020 Release | Q 10 - Q Release 5 - QQ1A.200105.007 to my device with the instructions listed on the site and that is it correct? All my data will be cleared automatically?
Click to expand...
Click to collapse
Yes
Just backup your data to computer 1st
Sent from my PH-1 using XDA Labs

I just tried to download the Jan update using firefox but received "Blocked by X-Frame-Options Policy", tried on chrome and it failed too. Finally I tried IE and it worked.

Just curious if anyone has tried dirty-downgrading just the January boot.img?

I didn't lose any data when I downgraded from February to January, what are you all talking about? Just flash the OTA.

DAE1964 said:
Just install the January build from essential it will format the data
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
No, fastboot flash the January OTA and you will NOT lose your data.

Vandan.Patel said:
https://www.essential.com/developer/current-builds
Just to confirm I just flash the January 2020 Release | Q 10 - Q Release 5 - QQ1A.200105.007 to my device with the instructions listed on the site and that is it correct? All my data will be cleared automatically?
Click to expand...
Click to collapse
If you fastboot flash the OTA you don't lose data. I've done it several times to both my daily driver and my backup ph-1 and I've had no problems.

aleph23 said:
Just curious if anyone has tried dirty-downgrading just the January boot.img?
Click to expand...
Click to collapse
No but I assume it will work as expected

This is the closest workaround we've found so far:
Bill720 said:
I got it working... kind of
That's too bad, given the importance of this final software update. At any rate, I worked on this for a few hours yesterday and found what I consider to be a viable solution by taking advantage of the ever-irritating "slots" function.
Basically, with the January 2020 Rom (stock, rooted, and EdXposed) on both slots, I used TWRP to install the PH1-OTA-QQ1A.200105.032.zip to one of the slots. I booted the phone and verified that it had received the Febuary Rom (032) on that slot and was still running the January (007) on the other. I used Fastboot to apply the FebRoot.img image to the slot that I had upgraded to 032 and restarted.
With that done, and after verifying that everything was working as expected, I now had one slot with a fully rooted/working 007 and, most importantly, one with a fully rooted/working 032 (Febuary 2020). To have some access to TWRP, I installed the same old "Dec_boot_patched_TWRP.img" on the slot with the old January (007) Rom that I wouldn't be using anymore. That slot now has only TWRP. When I need to use it, I just flip over to slot A, do whatever needs to be done in Twrp, switch back to slot B, and boot normally.
While this is a bit annoying, the only times I ever should need to use TWRP anymore will be for emergency recovery purposes (in case of broken Magisk/EdXposed module updates) and for doing backups. The 30 extra seconds that I'll have to spend (maybe 2-3 times per year) are worth it in exchange for not having to dismiss the ever-irritating update nags ever few days. Even if Twrp never gets updated, I'm happy with leaving it as-is, since this setup is essentially 100% functional.
For anyone who might be playing along at home, here are some of the most useful commands, all compiled into one place, in no particular order:
adb reboot fastboot
adb reboot recovery
adb shell getprop ro.boot.slot_suffix (this one tells you what slot you're currently on, after booting up, or from within TWRP)
fastboot getvar current-slot
fastboot --set-active=a
fastboot --set-active=b
fastboot reboot recovery
fastboot flash boot_b FebRoot.img (or, alternatively fastboot flash boot_a FebRoot.img)
Click to expand...
Click to collapse
You could also stay on the previous build indefinitely, but nobody found a good way to get rid of the update nags.

Android 11 Release

Android 11 has been released. Anyone upgraded yet on a rooted device?

Subscribing for root results.

I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.

fkofilee said:
I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.
Click to expand...
Click to collapse
I'm curious to know too!

We gots Root!
So far so good root is working

XMayhem2099 said:
So far so good root is working
Click to expand...
Click to collapse
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?

dimm0k said:
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?
Click to expand...
Click to collapse
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?

antiochasylum said:
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?
Click to expand...
Click to collapse
oops, I was hoping to do it via full image rather than OTA

dimm0k said:
oops, I was hoping to do it via full image rather than OTA
Click to expand...
Click to collapse
Probably better to do that lol. My ota is sitting at 1.72gb so it would seem to be a full image.

Did the 1st flash... Didnt boot - Unlocked BL - Looks like nothing flashed to Partition A / Boot A.
Flashing again now ^^

I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Do you use the canary build of Magisk or the stable release?

Anyone got a replacement for overscan?

matekaneve said:
Do you use the canary build of Magisk or the stable release?
Click to expand...
Click to collapse
Canary

Well after redownloading the Core Files and updating ADB - Looks like we are alive...
Checking root now.

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Not working here either, we need to wait for Magisk update, most probably.

gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt? Did you flash the full image or OTA? Next step for me (after creating a new patched boot.img) would be to clean flash the full image. Best of luck.

do you have a link to the canary apk?
I tried going to the canary page, but the download link is dead. TIA
v12xke said:
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt?
Click to expand...
Click to collapse

Further down the page youll see it
https://github.com/topjohnwu/Magisk
---------- Post added at 20:29 ---------- Previous post was at 20:27 ----------
Also to add - Magisk Canary outputted a 4MB Boot Image which was wrong - Correctly patched it should be 32.55 MB roughly.
Make sure you pay attention that the boot.img has been patched properly.

I had trouble rooting but eventually got it to work. I deleted all previous boot images and patched images from phone and pc. Reinstalled platform tools. Grabbed fresh boot img from the factory image, patched it then flashed it. And we're in biz