FORUMS

TWRP 3.3.1-1 for Pixel 3A XL [OFFICIAL]

967 posts
Thanks Meter: 1,517
 
By ZVNexus, Recognized Developer on 27th June 2019, 10:13 AM
Thread Closed Email Thread
Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Code:
#include <std_disclaimer.h>

/*
 * Your warranty is not void.
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this recovery
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */
Note: Please be aware that you cannot install this without a kernel with LZMA compression support, I believe most ROMs have included my commit for this so you should be good for all custom ROMs and kernels. If not please file a request to the maintainer.

In addition, please be aware that TWRP is currently not compatible with Android 10. If you would like to use TWRP you will need to go back to Android 9. If you would like more information you can read at the link here.


Not a huge problem, stock users can just temporarily boot TWRP if you have access to a PC.
Not compatible with Android Q.

Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.


Installation:

If you already have TWRP installed: Download the latest zip and install the zip using TWRP.

If you do not already have TWRP installed: Download both the img and the zip. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:

fastboot boot path/to/twrp.img

This will temporarily boot TWRP on your device. Use ADB or MTP to transfer the zip onto your device.

Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.

If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.

Changelog:
[BETA]
3.3.1-0: Initial release for Pixel 3A XL devices
3.3.1-1: Fixed having to manually change slots before rebooting.
3.3.1-2: Updated to July blobs!
3.3.1-3: Can now install TWRP to boot image. ADB, MTP, LOGD, Repack Tools and Logcat have all been removed to save the necessary space for this to work. You can grab stuff while in the OS, then flash it in TWRP (Keep in mind I have only tested this on stock as of now, feel free to test it on whatever ROM you use. It should work, but let me know if it doesn't).
3.3.1-4: Changed back to LZMA compression, also added back all the features besides ADB/Logcat. As long as your kernel supports LZMA you will be able to take advantage of installing it permanently without having to worry about space restrictions.
3.3.1-5:
Add persist entry to fstab
* To allow TWRP to store a backup settings file on /persist
and also to be used as QCOM time fix source during early boot.
Revert "Don't include logcat."
Revert "Don't include repack tools."
3.3.1-6:
Revert "Revert "Don't include repack tools.""
Add haptics firmware.
* This obviously on it's own isn't enough to get haptics working for the 3A in TWRP, but its a start.
Don't include a precompiled update_engine_sideload
* This should fix the issue of flashing officials for StatiXOS

[STABLE]
3.3.1-0: Initial official release!

Download:
https://twrp.me/google/googlepixel3axl.html

XDA:DevDB Information
TWRP, Tool/Utility for the Google Pixel 3a XL

Contributors
ZVNexus, janjan
Source Code: https://github.com/TeamWin/android_device_google_bonito


Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-07-17
Current Beta Version: 3.3.1-6
Beta Release Date: 2019-06-27

Created 2019-06-27
Last Updated 2019-11-15
The Following 33 Users Say Thank You to ZVNexus For This Useful Post: [ View ]
27th June 2019, 10:13 AM |#2  
ZVNexus's Avatar
OP Recognized Developer
Flag Rocky Hill
Thanks Meter: 1,517
 
Donate to Me
More
Reserved
The Following 5 Users Say Thank You to ZVNexus For This Useful Post: [ View ]
27th June 2019, 11:22 AM |#3  
Senior Member
Thanks Meter: 33
 
More
Awesome! Thank you so much!
So as of this moment, there is only the ability to boot to twrp via fastboot?
27th June 2019, 12:24 PM |#4  
ZVNexus's Avatar
OP Recognized Developer
Flag Rocky Hill
Thanks Meter: 1,517
 
Donate to Me
More
Quote:
Originally Posted by DriveEuro

Awesome! Thank you so much!
So as of this moment, there is only the ability to boot to twrp via fastboot?

Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.
The Following 7 Users Say Thank You to ZVNexus For This Useful Post: [ View ]
27th June 2019, 12:59 PM |#5  
Senior Member
Thanks Meter: 33
 
More
So does anyone know if TWRP + Magisk work on Android Q for root?
27th June 2019, 02:29 PM |#6  
Senior Member
Flag Tampa, FL
Thanks Meter: 65
 
More
Quote:
Originally Posted by ZVNexus

Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.

I don't mind, I haven't flashed TWRP to a device since Treble came out, but it's easy enough to boot an image, so at least for my usage case, this is all I need
27th June 2019, 03:51 PM |#7  
Junior Member
Thanks Meter: 5
 
More
otg mounting problem
Quote:
Originally Posted by ZVNexus

Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.

no you shouldn't have waited!! thanks a lot specially from all of us checking if twrp came out every day!

hey maybe you can give me a tip since i have a problem mounting otg:
when i boot twrp image if i go to backup/select storage i find a storage/usb partition (0MB)
when i connect otg (and go to mount) it becomes storage/usbotg 1 (12000MB)
but the problem is that if i click it doesn’t remain selected, and the log reports “Unable to find partition for the path ‘/storage’ ”
if i go to mount or backup/select storage and click usbotg 1 storage it doesn’t remain selected and the log reports “E: unable to locate partition for ‘/storage/usbotg-1’ ”
(i’ve tried also with different keys but i don't think it's the point anyway the 1st was an 256GB usb/SD and the 2nd a 16GB usbkey but logs reports same error)

any tip?
27th June 2019, 03:57 PM |#8  
Senior Member
Thanks Meter: 33
 
More
I'm on Q DP4. Anyone having luck flashing Magisk (canary)? In B slot it fails to mount system and vendor. I change to A slot. It completes. I reboot on A slot, I get stuck at Google starting logo and the phone never boots. If I attempt to boot B slot afterwards, it boots up fine, but I obviously don't have Magisk installed, verified with the Magisk APP.

Anyone have a clue?
27th June 2019, 04:14 PM |#9  
Junior Member
Thanks Meter: 12
 
More
Just to provide feedback.

Fastboot booted the image, it prompted for my pin, mounted system, and was able to backup properly, moved backup to computer.
Wiped the phone, reboot and went through setup, everything was working.
Back to twrp, adb pushed the backup to the phone, restored the backup and everything was functioning.
Also tested and was able to sideload flash Magisk.

So everything seems to be working as intended.

Thank you so much for your hard work!
The Following 7 Users Say Thank You to Antonyo13 For This Useful Post: [ View ] Gift Antonyo13 Ad-Free
27th June 2019, 04:17 PM |#10  
Senior Member
Thanks Meter: 33
 
More
My TWRP is NOT prompting for pin/pattern. That has to be part of this...
Wiped data via google recovery. The phone booted to Pie (i had previously did the OTA from Pie to Q beta 4). So now I'm back on Pie somehow (without reflashing). I booted to TWRP, installed Magisk successfully.

So overall, I'm not sure if this was related to Q beta 4 OTA occupying B slot while Pie still was on A slot.

Thanks to all for their work with TWRP!
The Following User Says Thank You to DriveEuro For This Useful Post: [ View ] Gift DriveEuro Ad-Free
27th June 2019, 04:45 PM |#11  
Quote:
Originally Posted by Antonyo13

Just to provide feedback.

Fastboot booted the image, it prompted for my pin, mounted system, and was able to backup properly, moved backup to computer.
Wiped the phone, reboot and went through setup, everything was working.
Back to twrp, adb pushed the backup to the phone, restored the backup and everything was functioning.
Also tested and was able to sideload flash Magisk.

So everything seems to be working as intended.

Thank you so much for your hard work!

On previous devices I have run into TWRP restore issues if I had a security PIN set on the device when I backed up. During your test did you have a PIN setup on the phone?
Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes