TWRP 3.2.3-1 for Pixel Devices

Search This thread

petiolarissean

Senior Member
Oct 19, 2013
421
99
If you delete per_boot file backup will work.
systems
data
per_boot
It rewrites after boot and you have delete it every time want to backup
 

DirtyAngelicaSecured

Senior Member
Mar 30, 2020
96
13
Paris
I can't figure out how to properly flash ROM's on my Pixel sailfish... Here's the flow:
- Use the latest stock ROM "flash-all.bat" 2 times - for Bootslot A and then for Bootslot B
- Fastboot TWRP.img - Internal Storage is readable is not encrypted, files can be copied via MTP
- Follow custom ROM instructions to wipe Cache, System, and Data, reboot
- Fastboot TWRP again and BLAH - Internal Storage is not readable and I am back to "flash-all.bat"

I can dirty-flash custom ROM's if I do not perform the WIPE stage, I want a clean install of custom ROM's...
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,939
7,188
I can't figure out how to properly flash ROM's on my Pixel sailfish... Here's the flow:
- Use the latest stock ROM "flash-all.bat" 2 times - for Bootslot A and then for Bootslot B
- Fastboot TWRP.img - Internal Storage is readable is not encrypted, files can be copied via MTP
- Follow custom ROM instructions to wipe Cache, System, and Data, reboot
- Fastboot TWRP again and BLAH - Internal Storage is not readable and I am back to "flash-all.bat"

I can dirty-flash custom ROM's if I do not perform the WIPE stage, I want a clean install of custom ROM's...

I would make sure to format data so the new ROM can create a new FBE policy, rather than just wiping.
 

rodken

Senior Member
Jan 11, 2010
1,004
392
I can't figure out how to properly flash ROM's on my Pixel sailfish... Here's the flow:
- Use the latest stock ROM "flash-all.bat" 2 times - for Bootslot A and then for Bootslot B
- Fastboot TWRP.img - Internal Storage is readable is not encrypted, files can be copied via MTP
- Follow custom ROM instructions to wipe Cache, System, and Data, reboot
- Fastboot TWRP again and BLAH - Internal Storage is not readable and I am back to "flash-all.bat"

I can dirty-flash custom ROM's if I do not perform the WIPE stage, I want a clean install of custom ROM's...

Be certain to select all of the entries within TWRP, granted that you have already backed up your internal.
 

Attachments

  • images.png
    images.png
    5 KB · Views: 321

DirtyAngelicaSecured

Senior Member
Mar 30, 2020
96
13
Paris
Don't you need to flash Magisk again after each TWRP flash? That could be the issue...

---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------

Be certain to select all of the entries within TWRP, granted that you have already backed up your internal.

I figured it out. I had to format internal memory and then it worked. TWRP backup failed for me with 255 error and I already checked for the "User 999" possibility, which did not exist. Multiple Users feature was turned off. So far I was only able to backup using Migrate-GPE App without errors.
 

DirtyAngelicaSecured

Senior Member
Mar 30, 2020
96
13
Paris
Yeah, it appears you have to wipe internal storage for it not get encrypted, but then MTP in Recovery does not work... Basically, you have to sideload whatever ZIP files you want. Copy/paste does not work due to dead MTP, which causes copy/paste process in Windows to freeze.
 
Last edited:
  • Like
Reactions: beeewell

Top Liked Posts

  • There are no posts matching your filters.
  • 200
    TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!

    Pixel XL

    Pixel

    DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.

    Note: Do not use if you have multiple users (including a guest user)

    File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.

    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.

    The zip install method installs TWRP to both slots.

    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. Copy the zip to your device. 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. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.

    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.

    NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.

    3.2.1-1 has working decrypt with the February security patch!
    3.2.1-2 fixes some zip install errors
    3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
    61
    How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
    23
    How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
    18
    SuperSU v2.79-SR1 was just released.

    It works for me on my Pixel XL running 7.1 with TWRP RC1, but I have not updated my device to 7.1.1 yet. I suggest you try again and let me know.

    Note that I don't really follow this thread, so either specifically mention me ( @Chainfire ) or post your results in the SuperSU BETA thread ( http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 ).