yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
First, correct me if I am wrong but you wrote you wanted to try Q4 beta. So, why would you relock the bootloader. Second, AFAIK a Factory reset (Erase data) does not boot to the " bootloader unlock screen". After, a Factory reset it brings you to the Google login. Third, I do not know why it didn't Factory reset.

Suggestion, if you have twrp installed, are rooted, and have a custom kernel:

- want stock Pie, do #4 ' keep data'

- want Q4 beta, download Q4 beta Pixel 3 XL factory image (Update(s) 3.) do #4 'wipe data' with Q4 beta Factory image.
[Google Pixel 3 XL Guides, News, & Discussion] GartimusPrime:
I guess relocking the bootloader was just for ease of updates, or me being lazy. The biggest thing is, I have bricked a phone before because I didn't pay attention and I jumped the gun. My wife has made it very clear that this will be my last phone, ever haha. So I am trying to figure out my best option for getting firmware updates or downloading the Q beta. Also I do not have a custom kernel because I am honestly scared to death about doing something stupid, mostly just scared of the wife, haha!

Thanks for your reply though!
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
One piece of good news for you. It's almost impossible to hard brick these phones. Soft bricks are relatively easy to recover from.

Only way I've heard of hard bricking one of these is to successfully lock the bootloader on a phone that isn't 100% stock.

Just make sure you know at least the basics of adb and fastboot, that you have the latest versions of these, and that you have some clue about A/B devices and what makes them different from earlier phones. If you need to read up on A/B phones you can start here https://xdaforums.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123

I also keep a copy of the latest stock boot image around (even if you're rooted and/or running a custom kernel). You can usually recover from a problem by using fastboot to flash that boot image to both slots. Worst case you flash the latest factory image. (Keep backups, off the phone, in case you ever need to do a full wipe).

Something else. Oh yeah - I recommend against flashing TWRP. Just use fastboot to boot it when you need it. That eliminates one possible avenue of errors to the boot image since there's no longer a separate recovery partition. Just a recommendation though, lots of people do flash it and they're fine.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Most people who unlock the bootloader usually do not relock it because they do no want to risk bricking their phone. Another, way to minimize the risk of bricking you phone is:

a. Read and re-read the instructions until you are certain you understand them before you apply them.

b. Ask questions if there is something you do not understand the instructions.

As far as the best way to get firmware updates for the pixel 3 XL. Many, do the following:

a. Download the monthly Factory image update.

b. flash-all it (#4 'keep data') - It takes approximately 5 minutes to flash-all the Factory image.
[Google Pixel 3 XL Guides, News, & Discussion] GartimusPrime:
Thank you for that article, it is very informative! I will probably read it again later since I just woke up but I get the gist of it! I will need to do some more reading on how to flash an update via fastboot. Also, I did actually flash TWRP.

I wish I wasn't an excited puppy when I got home with my phone and read first, haha!

I think my ultimate goal, is that I would love to try the Q Beta, is that flashable via fastboot? I am semi familiar with adb and flashing things, so I should be able to figure this out.
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
Yes, Q beta (like all factory updates from Google) is flashable via fastboot. One thing to keep in mind, TWRP does not yet support Q (and won't until it goes stable). Magisk does, finally, support it though.

Whatever you do - don't panic ? and have fun.
[Google Pixel 3 XL Guides, News, & Discussion] GartimusPrime:
Thank you! Honestly I don't care much about root right now because I have Magisk installed currently and have used root for nothing except Swift Installer, which is funny because I have rooted every device I have ever owned. I will look into how to flash Q when I get home. Just one question, is it safe to flash Q (or any update) with TWRP flashed and Magisk installed or do I need to uninstall those first?
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
It's safe. It (or any system update) will replace the boot image as part of the update. Since both Magisk and TWRP live in the boot image they'll both get removed.

When you flash Q the default install will completely wipe the phone so all secondary files will get deleted as well. (Make sure you've backed up, to your computer, anything you want to keep)
[Google Pixel 3 XL Guides, News, & Discussion] GartimusPrime:
Thank you so much everyone that has helped! First, I would like to kinda apologize for being stupid with my first posts, I have been looking at this thread via XDA Labs and there are no corrosponding Letters or Numbers in the OP so I was getting easily confused. I am now looking on my computer and its much easier to understand, haha!

I have downloaded the latest Q Beta to my computer and have downloaded the updated ADB drivers, here goes nuthin'

---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------

So, we are about to get an insane thunderstorm where I am so I think I will wait to try anything. I have a platform-tools folder and I extracted the latest Q beta into that folder. With TWRP physically flashed and magisk installed, it really is as simple as rebooting to fastboot mode and running that command? Sorry, just trying to cover all my bases.

I decided to just give it a go. I rebooted to fastboot, changed my directory to my platform-tools folder, made sure my factory image was extracted in the folder and ran the flash-all command. Nothing happened, just command not found. I googled it and saw I should make the .sh file executable so I did and tried it again. This time it said fast boot was too old and to dowoad the latest version, which I already did, r29.0.1
[Google Pixel 3 XL Guides, News, & Discussion] GartimusPrime:
delete
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
I'm not a 100 precent sure but I think you have to make fastboot executable too.
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
Yes fastboot needs to be executable, but I don't think that's the issue, otherwise it would say 'not found' rather than 'too old'.

Some assumptions. Correct me if any are wrong.

Linux box.

Running everything via terminal commands.

You downloaded the latest tools from Google and flash-all/fasboot are in the same directory.

I'd like the output of 2 commands, issued from inside the same directory.

type fastboot

echo $PATH

(if type doesn't work (it should) replace it with which)
[Google Pixel 3 XL Guides, News, & Discussion] GartimusPrime:
So I was using Linux and I switched to Windows. I did the command flash-all and it started to work then just stopped, as I was freaking out not knowing how to explain to my wife that I broke my phone, it continues to flash and now I am on Q beta 4, so far so good. Thank you for everyone's help!
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
I'd still like to know what happened on the Linux box. My guess is that there's 2 copies of fastboot installed - a system version and the downloaded version and that the system version is what was getting executed.

But I'm glad it worked out for you.
[Google Pixel 3 XL Guides, News, & Discussion] mcwups1:
Geez, I feel like I asked this already but I can't find it.

Does it matter, when updating, if you flash the Factory or OTA? One is larger than the other, so I want to make sure I don't forget something. I already know to delete the "-w", but when would I use either one?

TIA
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
If your phone is rooted do #4 'keep data', then #7 to reroot. It only takes a few minutes. If your phone is not rooted take the OTA.
[Google Pixel 3 XL Guides, News, & Discussion] cantara256:
How do I edit /system/build.prop? I used to be able to use ES Root Explorer but it won't work after updating to July Android update from the April update, I get "Error getting file content". I tried adb shell or SSH Droid, then su, but either way I get "Read-only file system".

I just want to get rid of that pesky navigation bar using the "qemu.hw.mainkeys=1" method. The navigation apps I've tried (OnePlus Gestures, Vivid NG) work for navigation but removing the nav bar is always wonky; it'll occasionally show up and then disappear. The only way to completely get rid of it is the build.prop way.

Suggestions welcome.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Try Build Prop Editor from the Play store.
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
In this particular case the simplest solution is to drop a script into /data/adb/post-fs-data.d/

Name it something like prop.sh

#!/system/bin/sh
setprop qemu.hw.mainkeys 1
exit

(no equals sign is correct)

Make sure you make the script executable

Alternate solutions:

Create a simple Magisk Module

/data/adb/modules/set_prop

/data/adb/modules/set_prop/skip_mount (0 byte file)

/data/adb/modules/set_prop/system.prop

# This file will be read by resetprop
qemu.hw.mainkeys=1

/data/adb/modules/set_prop/module.prop

id=set_prop
name=set_prop
version=v1
versionCode=1
author=anonymous
description=set prop to remove nav bar

-------------------

Install MagiskHide Props Config (Magisk Module). Among it's functions is the ability to set/modify build.prop props by using Magisk's resetprop command. (You can also use resetprop instead of setprop in the initial boot script I mentioned)
[Google Pixel 3 XL Guides, News, & Discussion] nick491:
Unable to boot device, think it's a softbrick or something...

After unlocking the bootloader, flashing TWRP I wiped everything using TWRP. After that I'm no longer even to pull up TWRP. So, tried to run TWRP off of PC using "fastboot boot twrp-3.3.1-1-crosshatch.img", the error is displayed: "Sending 'boot.img' (65536 KB) OKAY [ 0.289s]

Booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')

fastboot: error: Command failed"
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
Get a factory image and install it via fastboot
[Google Pixel 3 XL Guides, News, & Discussion] nick491:
Thanks. Had to figure how to extract each and everything to the fasboot folder, then ran flash-all.bat and everything was golden... Now when I'm willing to try flashing a custom rom on it again, hopefully golden.
[Google Pixel 3 XL Guides, News, & Discussion] Neyssi:
I try to install this ROM on my phone, after I did a wipe system/data/cache, I flashed the ROM and the twrp installer but my phone stayed on the bootanimation during all the night. Anyone can help me please, thanks.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
This thread is a [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery. If you installed a Custom ROM from 10. Custom ROMs for Pixel 3 XL. I suggest you click on the link of the Custom ROM you are trying to install and follow the instructions in the OP ( Post 1 ) to install it. Further, if you still are having problems installing it, post your questions on that thread.
[Google Pixel 3 XL Guides, News, & Discussion] dnsmo:
anyone has luck on the official Q yet? I fastboot twrp 3.3.1-2 to my phone and it went in without mounting the storage. So can't install anything after that. Is it broken and need update twrp now?
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
TWRP needs to be updated. They're aware. In the meantime what exactly are you trying to install? There are alternate methods, although, depending on what, you may have to purchase an app.
[Google Pixel 3 XL Guides, News, & Discussion] Otterbotanical:
Trying to install on a OS-less Pixel 3 XL.

I work in a repair shop and have a Pixel 3 xl that I'm just trying to install the stock Android 9 OS to, and then update normally to Android 10. Unfortunately, it doesn't have an OS on it already. When you cold boot the phone, you get "Can't find valid operating system. The device will not start." I can get to the bootloader (also called fastboot mode?), but it shows in green: "Device state: locked." I can't unlock the bootloader.

I can't get to the android settings to unlock it from the developer options, since it doesn't have an OS, and after figuring out adb, trying the "fastboot flashing unlock" code returns "FAILED (remote: 'flashing unlock is not allowed')".

I've searched the XDA forums for a bit, but all answers are to go to the developer settings in android.
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
If you could install an OS there would be no need to install 9 then update. You could just install 10 straight off.

However from what you've said I think you're screwed. How did it get in that state in the first place? At this point I think you'd have to RMA back to Google.
[Google Pixel 3 XL Guides, News, & Discussion] joedeuce:
If you're able to get to recovery, you can sideload an OTA, even with locked bootloader.

https://developers.google.com/android/ota
[Google Pixel 3 XL Guides, News, & Discussion] mcwups1:
So, should I not update?

Still issues with 10?
[Google Pixel 3 XL Guides, News, & Discussion] mgp53:
Yes, I would wait. Google is still shaking out some issues. At least from what I've read.
[Google Pixel 3 XL Guides, News, & Discussion] mriulvr:
TWRP not accessing storage

Bought a "new" Google Edition Pixel 3 XL that was a factory replacement and had never been used. I unlocked the boot loader, no problem. However, I am having a strange problem getting root. When I boot to fast boot mode and boot twrp-3.3.1-3-crosshatch.img, TWRP boots but does not ask me for my PIN, no swipe to allow mod, and does not access storage so I cannot flash Magisk. I tried removing security settings and then resetting security settings but same issue. Also tried without security settings but same issue. TWRP shows Internal storage as 0MB. Running Nov security patch for 10. Considered reinstalling Factory Image but thought I would check here first.
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
Twrp doesn't work on andriod 10. You'll need to use magisk to patch a boot. Img. Then flash that with fastboot.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
You're using the wrong guide this is the Guide for Android 10 (Q)
[Google Pixel 3 XL Guides, News, & Discussion] lingarajug:
so i have updated to android 11 DP2 and trying to flash magisk, used fastboot to boot twrp and it sends image to phone but then says command failed and reason being too many links, idk what that means and is it possible as of now to magisk 11 dp2?, thank you.
[Google Pixel 3 XL Guides, News, & Discussion] laupuy:
[MENTION=2479495]lingarajug[/MENTION]

Magisk is not ready for Android 11. You should follow Topjohnwu on Twitter to be informed.

Envoyé de mon Pixel 3 en utilisant Tapatalk
[Google Pixel 3 XL Guides, News, & Discussion] lingarajug:
But my problem is twrp temporary booting failing issue to flash zips, i have bl unlocked phone on stock dp2.
[Google Pixel 3 XL Guides, News, & Discussion] Slim2none4u:
Twrp doesn't work on Android 10 or 11 yet.
[Google Pixel 3 XL Guides, News, & Discussion] hawkz28:
I used this guide to unlock and root my phone probably 18-24 months ago. It's worked great until today. FC messages on random apps, go to open gmail or textra and it freezes and closes. No new apps or updates were installed prior.

Could I flash the stock file in TWRP followed by magisk to reroot, or do I need to install everything on my laptop again and start from scratch?
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Maybe this is the answer to the FC's:

https://www.theverge.com/2021/3/22/22345696/google-android-apps-crashing-fix-system-webview
[Google Pixel 3 XL Guides, News, & Discussion] hawkz28:
Interesting. Still having the issue after updating and disabling apps. Gmail wouldn't even work. I had to uninstall affected apps and reinstall. Also had to backup gmail, uninstall, reboot, and installed from play store as I wasn't given option to uninstall updates. Still didn't work. After restoring gmail from TIBU, and then uninstalling through play store, I got the OG gmail back and I can open email again. At least it's fixed.
[Google Pixel 3 XL Guides, News, & Discussion] Clark Joseph Kent:
Thread Closed as per the OP, thanks.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Are you flashing Magisk-17.3.zip in twrp or a patched_boot.img?
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
No. You can sideload it.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
No. When you flash the factory image you are stock.
[Google Pixel 3 XL Guides, News, & Discussion] brandonpa:
I have tried doing Magisk in twrp itself, patched_boot.img itself as well as both magisk in twrp and patched_boot.img after each other.

But I finally got it to work when I installed magisk17.4 from the build repository. patched it through the twrp.img and not the installed version of twrp this time!
[Google Pixel 3 XL Guides, News, & Discussion] sliding_billy:
Thanks, Homeboy76. I didn't think so, but that is completely contrary to what your instructions post claims. Maybe need to edit the OP.

If Magisk is installed, flash the latest Magisk-uninstaller-20180719.zip - Post 1, Downloads before installing factory image.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
First, tell me where you saw that in the Pixel 3 OP.
[Google Pixel 3 XL Guides, News, & Discussion] sliding_billy:
Page one of this post. #4 under index (click to show content)

Install Factory Image keep or wipe data

When doing a major upgrade, Android 8.1.0 (Oreo) to Android 9.0.0 (Pie). I suggest wiping data/Clean Install.

If Magisk is installed, flash the latest Magisk-uninstaller-20180719.zip - Post 1, Downloads before installing factory image.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
:eek:Blind in one eye can't see out of the other. lol

I will remove that, thanks.
[Google Pixel 3 XL Guides, News, & Discussion] sliding_billy:
If that's the worst thing to happen to us today, let's chalk it up as a win. :fingers-crossed:
[Google Pixel 3 XL Guides, News, & Discussion] jawonder:
Does rooting the Pixel 3 XL requires the Canary Magisk or the regular Magisk can now be used ?.
[Google Pixel 3 XL Guides, News, & Discussion] sliding_billy:
17.3 Beta works fine.
[Google Pixel 3 XL Guides, News, & Discussion] jawonder:
After installing TWRP zip and Magisk 17.3 beta then reboot system my phone is stuck on "G" then reboot back to TWRP .
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
I would flash the boot image from the factory image in fastboot. That will return you to the stock recovery and kernel. You should be able to boot again. Then boot twrp, don't flash it, and install magisk. I've had issues flashing twrp too.
[Google Pixel 3 XL Guides, News, & Discussion] jawonder:
I downloaded the November Patch and have it on my PC . So just flash the Boot.img from that ?. Does matter if i was on that firmware or not ?. matter
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
Yes, you probably have to flash both boot slots. fastboot flash boot_a boot.img. Then do the same for boot_b
[Google Pixel 3 XL Guides, News, & Discussion] jawonder:
Don't understand what ment by "Then do the same for boot_b"
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
Use the same fastboot command but substitute boot_b for boot_a.
[Google Pixel 3 XL Guides, News, & Discussion] jawonder:
What about just using this command "fastboot flash boot --slot all boot.img" ?.Saw it in th OP here.
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
I've not used that fastboot command. I know flashing both slots individually works. I'll try the other command next time I flash the boot image.
[Google Pixel 3 XL Guides, News, & Discussion] jawonder:
I'm booted up now . Thanks .

---------- Post added at 10:22 PM ---------- Previous post was at 10:10 PM ----------

So it seems my problem is with Magisk . I boot TWRP and installed Magisk Beta 17.3 and it got stuck again on the "G" then boot into stock recovery. How do i get out of stock recovery ?.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Yes
[Google Pixel 3 XL Guides, News, & Discussion] brandonpa:
1. It seems that when we install twrp that you are unable to flash magisk with the installed version on our phones. I have only been successful in installing magisk through the fastboot twrp.img version only.

2. Which begs the question if flashing magisk doesn't work with the installed version of twrp, does anything else? If not what is the point of installing twrp on the phone?

3. What greenify app are people using? I thought xposed isn't supported by the Pixel 3 yet.

4. Anyone know of any viper4 audio mods that are compatible with our phones yet? Tried the latest version in the magisk module repository and it wouldn't load. Would love to get that equalizer working as the equalizer in Google music sometimes works and sometimes doesn't.
[Google Pixel 3 XL Guides, News, & Discussion] chakra:
I can't seem to unlock the bootloader. Nothing was greyed out, fastboot shows the device but when I run fastboot flashing unlock nothing happens.
[Google Pixel 3 XL Guides, News, & Discussion] c_86:
Update your tools
[Google Pixel 3 XL Guides, News, & Discussion] chakra:
OK user error. I was just being a dummy
[Google Pixel 3 XL Guides, News, & Discussion] Bubba:
Very nice write up OP.
[Google Pixel 3 XL Guides, News, & Discussion] ART:
Will removing "-w" from the flash all bat file, wipe system and data or should we do it manually via twrp to flash factory image (without wiping internal)?
[Google Pixel 3 XL Guides, News, & Discussion] Badger50:
Just fastboot the factory image with the -w removed to both slots. No need to even mess with twrp :good:
[Google Pixel 3 XL Guides, News, & Discussion] canada2005:
I don't think Magisk beta 17.3 is working with the Pixel 3 XL on the Nov update. No matter what I do I cant get it to boot. I end up having to uninstall it then my phone boots right up.
[Google Pixel 3 XL Guides, News, & Discussion] Gordietm:
Are you using the 17.3 hotfix version? It's working perfectly for me.
[Google Pixel 3 XL Guides, News, & Discussion] canada2005:
Yup just downloaded it this morning and tried again. No go. Getting stuck on the google load screen then it switches over to an error saying something wrong with the boot.img and unable to enter recovery. I boot back in to twrp and flash the magisk uninstaller and then everything boots back in like normal.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
It's working. Start over do #6, then #8 to root.
[Google Pixel 3 XL Guides, News, & Discussion] canada2005:
I've tried that multiple times. Still the same result. I'm going to wait for a stable branch of magisk before I try again.
[Google Pixel 3 XL Guides, News, & Discussion] rspkt:
I'm having an odd issue trying to unlock my bootloader. I reboot the device to the bootloader fine and the device shows up fine when trying "adb devices" and/or "fastboot devices" but when I type "fastboot flashing unlock" in the bootloader nothing happens no matter how long I wait. If I disconnect the cable or reboot the phone to the bootloader I get this error:

iMac:~ *****$ fastboot flashing unlock

ERROR: usb_read failed with status e00002ed

FAILED (Status read failed (No such file or directory))

Finished. Total time: 42.722s

If I don't disconnect or restart the phone, the terminal just sits there after typing "fastboot flashing unlock" and nothing happens. The device was purchased directly from Google as an "unlocked" version since I have Cricket Wireless as my provider so I should be able to unlock it. I did make sure Developer Options is enabled as well as "OEM Unlocking" option is enabled. Ideas?