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

Status
Not open for further replies.
Search This thread

gjtjbl

Member
Mar 23, 2020
5
1
Question about using TWRP to switch between slots A/B: I used the flash-all.sh script to flash the factory image to my phone, installed TWRP following the guide and it works fine, except when I try to boot into the opposite slot. For example, if my current active slot is A, I can use TWRP to change to slot B, and reboot system, but it never gets past the Google splash screen before restarting a few times, and eventually booting successfully back into slot A. I tried setting the active slot to B, and reflashing factory/installing TWRP and then the B slot can boot up fine, but not slot A. Anyone know what might be the issue? Seems like the flash-all script is only flashing to one side?? Just want to ensure both slots are able to boot fine before installing a custom ROM. Thanks!
 
  • Like
Reactions: davekaz

jessejamesd2i

Senior Member
Oct 2, 2019
59
4
How can i downgrade from android 10 to get this to work? there arnt really any guides and i seem to be stuck & confused. I tried flashing havoc os, followed all the steps everything seemed to have flashed okay but after reboot it goes straight to fastboot with an "error boot prepare" message. I appreciate any help!
 

s8m

Senior Member
Oct 9, 2010
310
113
How can i downgrade from android 10 to get this to work? there arnt really any guides and i seem to be stuck & confused. I tried flashing havoc os, followed all the steps everything seemed to have flashed okay but after reboot it goes straight to fastboot with an "error boot prepare" message. I appreciate any help!

This may not be advice you expect to hear in a TWRP thread, but to avoid headaches, I'd recommend not using TWRP for bonito at all and just re-flash a Google factory image, then through stock recovery flash a ROM like Dirty Unicorns or Bliss. It's a different flashing procedure for someone used to TWRP (as I was) but its dead simple and those are the best ROMs at the moment for our device anyway IMO.
 

FrankRr

Senior Member
Jun 14, 2010
163
39
Google Pixel 3a XL
This may not be advice you expect to hear in a TWRP thread, but to avoid headaches, I'd recommend not using TWRP for bonito at all and just re-flash a Google factory image, then through stock recovery flash a ROM like Dirty Unicorns or Bliss. It's a different flashing procedure for someone used to TWRP (as I was) but its dead simple and those are the best ROMs at the moment for our device anyway IMO.

I searched on the Bliss and DU Websites to find instructions how to flash "through the stock recovery", but found nothing.
Can you share your information about this?
 

s8m

Senior Member
Oct 9, 2010
310
113
For DU, first download the latest bootloader, radio, and ROM from their site. Bootloader and radio are under the IMAGES tab, ROM is under the OFFICIAL tab (or WEEKLIES if you're OK with potential bugs). If you are going to use Magisk, grab the boot image (under IMAGES tab) that corresponds to your ROM version -- you'll have to manually patch the boot image with Magisk Manager and then flash it through fastboot.

DU has a support group on Telegram where you can type #flash-radio-bootloader and follow the instructions to update your radio and bootloader first. I tried flashing the ROM without first updating the radio and bootloader and it would not work. You won't need to do that every time you flash though, only once (unless they update the images). Then type #flashing-pixel-du and follow those instructions to flash the ROM.

https://web.telegram.org/#/[email protected]

If you don't have Telegram, here are the latest instructions:

#flash-radio-bootloader
How to update your radio and bootloader on a Pixel
Radio:
Code:
fastboot flash --slot all radio radio.img
Bootloader:
Code:
fastboot flash --slot all bootloader bootloader.img
Make sure that you reboot to the bootloader after flashing either the radio or the bootloader:
Code:
fastboot reboot bootloader

#flashing-pixel-du
Pixel flashing instructions
If this is your first time flashing DU on your Pixel:
  1. Download boot.img and ROM zip from DU server
  2. Reboot into bootloader and flash the boot.img
    Code:
    fastboot flash --slot all boot boot.img
  3. Reboot to recovery
  4. Go to recovery select factory reset
  5. Select Apply update from ADB to flash the zip
    Code:
    adb sideload nameofbuild.zip
  6. Reboot and enjoy
Updating DU for your Pixel
  1. Download ROM zip from DU server
  2. Reboot into recovery and select Apply update from ADB to flash the zip
  3. Reboot system now and enjoy
 
Last edited:

zfk110

Senior Member
Jan 11, 2014
1,081
218
Atlanta
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 downloaded stock Pie firmware from Google and after flashing I fastboot boot TWRP.img and then I flashed the Magisk it was working fine, this morning I thought let me flash TWRP.Zip within TWRP which went smooth , but I lost the root, so I went back in TWRP and installed the Magisk, now phone stuck in bootloop. I don't know if there is any Kernel for Pie to fix this issue??
 

vandyman

Senior Member
Jul 30, 2012
848
467
S.Jersey
Google Pixel 5
Google Pixel 6
What's the replacement for a twrp aka nandroid full backup... Some elaborate dd command?
I have not done a nandroid backup in years. If I have an issue I either flash a boot. img or flash the factory rom without wiping data. Now, I depend on Titanium Backup. So without root things can be a little different.

Sent from my Pixel 3a XL using Tapatalk
 

adm1jtg

Senior Member
Jul 26, 2010
2,807
873
Georgia
Google Pixel 3a XL
I have not done a nandroid backup in years. If I have an issue I either flash a boot. img or flash the factory rom without wiping data. Now, I depend on Titanium Backup. So without root things can be a little different.

Assuming i want to root and use titanium or even swift backup i have found it doesn't backup everything. Things like login info for specific apps (dropbox for example) don't get backed up, Ajay since specific things in settings, So it's not the same as a full restore from nandroid where you are exactly where you left off. A titanium restore always requires some additional reconfiguring.
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    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:
    [I]#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.
     *
     */[/I]

    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
    12
    Just reuploaded 3.3.1-6 with one key fix, didn't feel like making a whole new version.

    USB OTG now works :)
    10
    Alright, reuploaded 3.3.1-1 with that oopsie fixed.
    9
    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."
    8
    When twrp creators update their code to work on q with the new partition setup then we should get official q support, until then it's a waiting game.

    Yep, I'm ready any time on my end.