yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Spannaa:
It's off topic here but Swift is different to TiBu.

You can backup and restore apps, splits, data, external data and expansion both in bulk and/or individually for both user and system apps.

Read the Swift FAQ.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] klemi71:
I updated my Pixel 3 Android 11 from May to June. So far, so good. But flashing patched Magisk boot.img doesn't work, my device doesn't boot up. Reflashing stock boot to both slots works, but root is lost.

I can use fastboot to boot into twrp-3.4.0-0-test6 build, but data partition is encrypted though I set no password. Is there a way to fix this? I don't want to flash TWRP, just boot into it to solve my issue without having to set up my complete phone again after clean install.

Please try to help.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] dcarvil:
I don't think any TWRP builds work on Android 11. You may have a Magisk module causing your boot problem. Try disabling all modules. See https://www.didgeridoohan.com/magisk/MagiskModuleIssues, section "Disabling/uninstalling modules manually".

I had no problems with the June update, but have no modules.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] lunalsmojo:
For v3.5, is there an installable zip file? The link posted connected me to a download for img, but no zip. Thank you for the hard work on this.

To everyone else:

Come on guys, @bigbiff and @rawstar11 (and anyone else, I only went back one page) are spending their personal time building this for us. Let's do less hating and show a little bit more gratitude

I understand it's frustrating when it's not working how you want, or it doesn't immediately solve your issue. It's your phone, I get it. We live on our phones. But if we're so dependent on the people building these things that we can't ever solve any of our own issues, especially things like figuring out that the build is for Android 10 and therefore won't work on Android 11, then we probably shouldn't be flashing our devices in the first place.

Thank any/all developers that have built something that you have enjoyed. They work hard, they have lives outside of xda, and they are people too. People appreciate hearing a simple "thank you" from time to time
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] klemi71:
Ist there anything new? A working TWRP for Pixel 3?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Spannaa:
No, If there was, it would have been posted here 😉
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] p0werpl:
Does mtp work in this twrp build?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] klemi71:
Can Pixel 3xl builds be used on Pixel 3?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Portgas D. Ace:
No.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] WazaBe162:
OK, so pixel 3 is officially unsupported by Google and community?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
Look at Pixel 3XL ROMs. Often, both Crosshatch and Blueline are listed in the same thread.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Captain_Throwback:
Don't worry; updated blueline TWRP is coming...
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] laffin_boy:
I'm hoping for guidance in installing a TWRP boot image. My goal is to install TWRP, Magisk & then LinkageOS 17.1 - having no Google anything on this phone

I have a Pixel 3 with a newly installed version of A10 on it. (downgraded from A 11) The bootloader is unlocked. I have ADB, USB drivers, etc on my Win 7 computer.

From my Win console I reboot into bootloader mode and then send: "fastboot boot twrp.img" (twrp.img is renamed from "twrp-3.3.0-0-blueline.img" and is in the ADB folder). (I've checked the file's SHA-256 & it's good)

The console says:

"Sending boot.img (65536 kb) OKAY [ 0.328 s ]

Booting OKAY [ 16.526s ]

Finished. Total Time 17.009s

and then it reboots into the Android OS !

What am I doing wrong ?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] bigbiff:
Hello guys, can you test https://build.twrp.me/twrp-3.6.0_11-0-blueline.img out on A11 and A12? Provided it will only decrypt if you have no pattern/pin/password in A12.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] dcarvil:
No problems found on my P3 with LOS 18.1 and a PIN. Did a backup and cruised through the menu options. I didn't try to install anything, as I can't risk being without my phone at the moment.

Great work, thanks for it. I had given up on TWRP for this phone.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] bigbiff:
Thanks, I am going to make a new thread for supporting blueline since @Dees_Troy is busy these days.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] onesolo:
After flash TWRP, can I set again pin/pattern/password? Will it be possible to enter again on TWRP?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] bigbiff:
You can do it while you only need to access data in A12. When you boot TWRP, remove it. Please use the new thread for future replies.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] dcarvil:
New thread is at https://xdaforums.com/t/recovery-teamwin-recovery-project-blueline-official.4385769/
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] heyChristo:
I just got a pixel 3 unlocked activated. however it is stuck on this every time I try to send twrp using the instructions in the OP:

fastboot: error: cannot load 'path/to/twrp.img': No such file or directory

blueline MP1.0(ROW)

b1c1-0.2-6085603

g845-00096-200114-B-6134206

89CX08CCW

production

yes

4gb micron LPDDR4X

128 micron

unlocked

b

before i read through every post in the forum, I thought I would ask first.

FYI, on windows 11 tried standard adb and also adb from platform-tools directory including with admin priveleges.

fastboot devices shows device 89cx08ccw but i keep getting the twrp img error above when typing in:

fastboot boot path/to/twrp.img
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] dcarvil:
Are you litterally using "path/to/twrp.img" ? You have to use the actual path to the twrp.img file, and the actual name of the twrp.img file. If you have both platform tools and twrp.img in the current directory, you can eliminate the path/to part.

Use platform tools, not the standard adb.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] heyChristo:
Yup, Im a derp. that is exactly what I was typing in. getting a new error now that I have never experienced:

Sending 'boot.img' (65536 KB) OKAY [ 1.504s]

Booting FAILED (remote: 'Error verifying the received boot.img: Buffer Too Small')

fastboot: error: Command failed
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] dcarvil:
Since you are posting in this thread, I assume you are using an old version of TWRP that does not work with newer Android versions. There is a new TWRP build that works on Android 11, and mostly works on Android 12. Look just a couple of posts above your post.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] heyChristo:
I was using the newest one. That was the first one I downloaded and nobody had posted any comments on the other thread. I got it. Was having some trouble with the push command to send it to the device since MTP didnt work. After bricking it, reflashing it back to 12 then resending twrp, I got them both installed. This is my first pixel, and I'm not really experienced with the whole a/b partitions. Now to see if I can brick it again while flashing magisk, lol.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] dcarvil:
Please let me know how installing both TWRP and Magisk works out. It is my understanding installing both together is more complicated than on non-a/b devices. I just boot TWRP when I need it, instead of installing it.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] heyChristo:
It worked out pretty well from what I experienced. I am not that handy with the commands from the command prompt because I only mess around with it when i'm rooting a phone and had extra problems because for some reason this phone could not drag and drop files from my PC when connected. My one plus works fine with the same cable but I am assuming there are issues with the pixel 3 driver similar to pixel c. Soo with that being said, I had to use command prompts for sending the files back and forth and at one point i just installed mega on the phone to drop the modified boot image to the computer to flash it on the phone.

I had a couple reasons for this. First is that I did not want to login to this device with my google account. I am a sprint customer and I wanted to activate this device with a t-mobile esim so I can send it to my mom since she is on my plan. Since the device has been registered on my account, and on the network, I can now send it to her and activate it on her line when she gets it. I also wanted to root the phone and have ad blockers, you tube vanced, vpn hotspot, and a couple other beneficial apps on there instead of getting her a phone full of bloatware and limited capabilities. (or else I would have got her an iphone se, lol). That is the reason for magisk, even though the unlocked pixel 3 is nice with very little bloatware on it and the installed tmobile apps that came with the 12 update were very easily removed.

In regards to getting twrp installed, I did brick the device once because i flashed it to the other partition, which is a bad move. I reflashed from the google official image to upgrade to 12. Don't change from A to B in twrp when you are in there, just click boot to system and thats it. There is NO need to switch partitions. I just wanted to make sure this device is 'unattended' not like a tethered jailbreak. It also made me realize to re-root my pixel c, I will have to do something similar with sending that boot image back and forth, but once its done, good riddance. So the big challenge was sending the files back and forth from the device, but if yours loads up in your computer it will be way easier. Mine only shows up if i switch it camera mode, and only then the photo folder, but maybe its a defect from buying a used/refurbished phone. I mean it shows up in adb, but not as a device with folders in my windows explorer for whatever reason

This article was used as reference for pulling the files back and forth:

How to set up and use ADB

Android Debug Bridge (ADB) lets you install software updates, uninstall pre-installed software, and more. Here's a guide on how to use ADB.

www.androidauthority.com
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] dcarvil:
Thanks for the update. Many file managers have the capability to get/put files on your PC. Here is one you can install without the Play Store.

MiXplorer: Q&A and FAQ (User Manual)

MiXplorer: Q&A and FAQ (User Manual) Table Of Contents: i. INTRODUCTION, GETTING MIXPLORER, & INSTALLATION (This post) ii. UI, NAVIGATION, VIEW CONFIGURATION, BOOKMARKS, TABS iii. WORKING WITH FILES & FOLDERS (Copy Move methods, Trash option)...

xdaforums.com
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Aditmac1:
Hi, sorry to bother but what does path/to mean? Is it like a path that I have to creat on my computer and the put img in it?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Aditmac1:
AH I see, thanks alot, I will try this tonight
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] AhmedSaleem403:
man i am pissed badly i had installed lineage 19.1 and now unable to install google apps and also unable to install any other custom rom for god sake give me other recovery than twrp and orangefox and linage recovery ihad tried but in vain help me otherwise my mobile is dead
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Homeboy76:
Is lineageOS 19.1 still installed on your Google

Pixel 3 and does it boot up?

What do you mean "otherwise my mobile is dead"?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] georgs_town:
Hey guys

It has been a while since I last installed twrp and rooted a phone, so I am really happy for a step by step "how-to", best combined with a video. I found this video online:

[YOUTUBE]https://www.youtube.com/watch?v=XhPNDGagKn8[/YOUTUBE]

Can anybody confirm that the process should work like this?

cheers
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jd1639:
That guy recycled some old video and labeled it for the pixel 3. What he shows won't work. The twrp version is an old version that doesn't and never will exist for the pixel 3 and there is no specific recovery partition to flash the recovery to like he shows in the video.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] jsauder2:
There's step by step instructions in the OP.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] .\\D-ZFR:
Nice. Thanks man. Appreciate it
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] melgar:
Hi,

i just tested TWRP-3.2.3-0 and Magisk 17.3 after i "ADB-sideloaded" the November-2018 Update(blueline-ota-pq1a.181105.017.a1-7f2186c3.zip) that was released today and everything worked without any problems.

regards,
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Archangel:
Thanks for letting us know I will be doing this tonight thank God for TWRP!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] .\\D-ZFR:
May I have the latest build.prop please. Thanks
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] PuffDaddy_d:
What order did you install twrp and magisk?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Archangel:
Hmm I am getting some weird error 51 something about a kpayloadtimestamperror? When I try to sideload like I have done in the past? Nervermind got it by flashing the factory image with -w taken out,,all good
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] melgar:
strange.

did you tried to sideload from stock recovery or from twrp recovery?

i used the stock recovery and didnt had any errors at all.

regards,
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Mrnicgeuy633:
I started from scratch and it's all working now. Factory image flashed, temp boot to twrp img, and installed both, one at a time. It seems to be finicky. Getting restore to work after I break something seems to not work. Just boot loops. I wonder at what point are restores not effective?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] PuffDaddy_d:
If restore doesn't work, then that is a deal breaker for me. The only real reason why I would need twrp is to backup and restore on the device quickly and easily. Otherwise, I can just use ADB commands with my computer and fastboot to flash any zips. I'll check back again in a couple months after the bugs are worked out.

Thanks!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
I will be a Pixel 3 XL/Pixel 3 "noob" tomorrow. I have been on a BL unlocked 1st gen Pixel XL (and the wife on a Pixel that I do all the work on) for the past 2+ years, so none of this is new to me. I am just getting a little overwhelmed by all of the threads on TWRP and Magisk in the past few days. Patched system images, installing Magisk without TWRP, uninstalling Magisk modules, etc. If I have grasped everything, I can upgrade to November (after unlocking the BL) using the flash-all, Fastboot boot TWRP and install the Magisk zip from the .img instance of TWRP while leaving stock recovery in place. I won't bother to setup a password/pattern/fingerprint until I am done, and I won't install any Magisk modules or a permanent install of TWRP until stuff settles down. Both using the .img TWRP only and removing passwords, etc before loading even the .img TWRP have been needed multiple times over the past couple of years, so I can live with this all short term. Any other insight or confirmation from those of you who have started treading these waters would be helpful.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] melgar:
don´t worry about password/pattern/pin or whatever. none of these will make things harder or more difficult.

if you are on stock recovery, these are the the steps for rooting with magisk:

1. reboot to bootloader mode (e.g. adb reboot bootloader)

2 fastboot boot twrp-3.2.3-0-blueline.img

3. enter password/pattern/pin or whatever in twrp

4. install magisk_17.3.zip in twrp

5. reboot & install magiskManager_6.01.apk (enable "install from unknown sources" in settings)

when already rooted, next firmware update is done with latest OTA.zip and adb-sideload in stock recovery:

1. reboot to stock recovery (e.g. adb reboot recovery)

2. select "apply update from adb" in recovery

3. on PC: adb sideload latestOTA.zip

then continue for root:

4. reboot to bootloader

5. fastboot boot twrp-3.2.3-0-blueline.img

6. enter password/pattern/pin or whatever in twrp

7. install magisk_17.3.zip in twrp

8. reboot

In case you have twrp permanently installed then you need to "fastboot flash boot boot.img" (from currently installed factory image) in order to be able to sideload the latest OTA.

(this will install the stock recovery overwrting twrp)

regards,
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] cambunch:
Do a bootloader unlock on your phone first (since it will wipe it). Then you should be fine with setting up a pin/password on your phone before flashing anything. This release of TWRP will sometimes not detect touch inputs, but if you just restart it will work fine. Nothing to do with encryption.

People (myself included) were getting bootloops with the newest update because of a specific module that hadn't been updated yet. You shouldn't need to worry about it now as the developer has fixed it.

At this point, most of it should be identical to the OG Pixel. Get your phone setup, then update to the November build (either via OTA or flashing the full image). Grab a copy of the latest Magisk Beta 17.3 zip, boot to TWRP, install the TWRP ZIP if you want, and/or then install the Magisk ZIP. Done.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
Much appreciated. When you say "next firmware update," I assume you mean December and not to root before updating to November. As for the OTA sideload, I have done a couple of OTA sideloads (from TWRP and bootloader) just for giggles, but almost exclusively I have done flash-all with the -w removed. Is there a reason you are saying to sideload the OTA instead of using flash-all every month?

---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------

Does Magisk Manager need separately installed for now, or is it bundled with 17.3?
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Archangel:
I believe, and I am not sure but, I think the sideload through TWRP is not working as I have yet to see anyone do it that way correctly. I have tried like I did on the OG Pixel with TWRP and sideloading the OTA and it works perfect on that phone but I get really strange errors with the Pixel 3. I did however, flash the factory firmware for the Nov update through fastboot after I updated my Platform Tools. That is most peoples problems with the Pixel 3 is that they are using older Platform Tools and they need to update. As for Magisk yes Magisk Manager is bundled in with the zip. I dont do all that patched boot stuff because I keeps TWRP installed therefore I can flash the Magisk zip easy peasy. For Dec i will do the same thing, uninstall any Magisk Modules, fastboot into bootloader flash the Dec update with the -w taken out of the flash-all.bat file so I keep my data, reboot to make sure it flashed fine, boot back into bootloader reflash TWRP and then Magisk. Reboot and make sure that any Magisk Module that I had before is compatible with the latest update before loading it up again.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
Thanks. Probably the only thing I do differently (normally at least) is just using the .img version of TWRP to install Magisk instead of doing a permanent install. TWRP permanent install support has been a little hit and miss, and I don't flash .zips that often or need to backup and restore often (even though that worked fine with the .img anyways).

Any Magisk modules that are "must haves?"
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Archangel:
Yeah I thought about uninstalling TWRP and just going with stock recovery as there are no roms or pretty much anything to flash that needs a custom recovery. Its just nice sometimes when I play around with my Substratum themes and do something bad to the systemui and it f/c then I will wish that I had TWRP installed and flash the Substratum rescue zip lol.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
Roger that!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] melgar:
yes, when i write "next fw update" i ment the december one, since there is no point in rooting if you are going to update the fw right after.

as for sideloading the OTA, i did it since my first Pixel 1 and just keep it that way because i never had any problem with it. of course you can also "flash-all" it, i think there is no big difference. i would use what is more comfortable for you.

i had to install the MagiskManager seperatly the first time only. after the next OTA you will still have it installed - so no need to do it again.

regards,
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sliding_billy:
Thanks!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] anyinnn:
About the flashing error

When I flashing the latest full ota zip file. It shows error 51.Then I try to flash factory image via fastboot ,the vendor image cannot be flash to my phone. Can anyone solve this problem? Thanks :)

sideload has the same problem,and I don't see any option in factory recovery
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] chowhoundb:
I had the exact same issue. Factory image failed at Vendor_A. Then the phone wouldnt boot. I tried multiple versions of fastboot. The older versions failed with a different error.

I ended up sideloading the OTA from the stock recovery and that got the phone booting again. The only problem now is the corrupt popup on every reboot, that you have to hit the power button to skip.

Also when you dont see options in stock recovery, you need to hold power and press volume up. that brings up the menu and you can choose sideload.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] sirebral123:
Restores Broken?

Hey all,

I've taken a few backups with TWRP and tried full system/data restores with both the September and November patch levels and after the process completes the device fails to fully boot. It gets stuck on the google boot page indefinitly. Is this a known isssue/bug and is there a fix? The only thing I've found to work (sometimes) is to run the flash-all.bat without the -w after a restore, yet this is not what I'd expect to have to do in the case of a full wipe and restore.

Thanks!
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] NYCHitman1:
Flash the stock product.img -- that should fix the "your device is corrupt" annoying message.
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] adhusky:
I have no issue boot into the twrp and install the magisk 17.4

but It keeps telling me that no slot is found when I was trying to reboot from the twrp.

so I had to flash the boot again to fix the boot slot.

Then I installed the magisk mangaer 6.01.apk and it showed magisk 17.1 not 17.4? even I have installed the magisk's uninstaller.zip.

Do you have any idea why it does not find the slot after the reboot? and any idea why it still stuck with 17.1?

Thanks in advance,

Adrian
[Google Pixel 3 ROMs, Kernels, Recoveries, & Other ] Archangel:
Unless your using the canary builds for Magisk it should say latest version 17.1 and installed version 17.3. I only use the beta and it has worked for me since it came out. I didnt know there was a 17.4 beta?