TWRP 3.2.3-2 for Pixel 3

[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

 

[dcarvil]

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

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.

 

[heyChristo]

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.

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

 

[dcarvil]

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

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.

 

[heyChristo]

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.

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.

 

[dcarvil]

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.

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.

 

[heyChristo]

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.

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:

Android customization - how to transfer files using ADB push and pull commands

ADB push and ADB pull are solid file transfer techniques for your Android customization experience, even if there are easier ways to get files between your Android device and a PC.

www.androidauthority.com

 

[dcarvil]

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:

Android customization - how to transfer files using ADB push and pull commands

ADB push and ADB pull are solid file transfer techniques for your Android customization experience, even if there are easier ways to get files between your Android device and a PC.

www.androidauthority.com

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)...

forum.xda-developers.com