TWRP 3.2.3-1 for Pixel Devices

Search This thread

schwem

Senior Member
Oct 15, 2014
2,215
761
35
Auburn Hills
Thanks for that post. Mine didnt ask for password first try either but 2nd time it did. Rebooting recovery took me to stock recovery, so I had to go from stock recovery back to bootloader and I just did it all over again then twrp did ask for the password then I could find the zip to flash. So anyone with this problem just flash Twrp all over again and twrp will ask for your password to decrypt then the zip is at the bottom of the list and boom twrp goodness.

Thanks Team Win Recovery Project team !!!!!!!!!!!!!!!!!!!!!!!!!

---------- Post added at 01:42 PM ---------- Previous post was at 01:39 PM ----------



I had to do all over then twrp did ask for my password to decrypt then zip showed up. Thank you for your help. I was pulling my hair out its always dumb mistakes lol.
Haha, I'm sorry but I've gotta laugh at what you've been going through. Sorry but I've done things like this going "man I must be stupid but I'm following it to a T! Haha, you can't help but laugh it off. Glad you got everything going man. :good:
 

M9guy

Senior Member
Nov 9, 2014
752
194
Glad you got there in the end!!

Sent from my Pixel XL using Tapatalk

Thank you, I did. But then It would not boot the system so I formatted data, still no go so I tried sideloading a full ota image actually 3 different ones and it wouldnt I figured maybe because its beta, then I couldnt get flash all to work on a regular factory image non ota. So I was on partician b so I tried switching to partician a and after a few minutes it decided to boot the OS. I"am guessing just my auto updates wont work now since it wont boot off the one partician oh well because rooted it wont auto update any way. Oh well at least its running I"am happy with that lol.:D
 

DaveHTC200

Senior Member
Oct 2, 2008
1,635
423
Thank you, I did. But then It would not boot the system so I formatted data, still no go so I tried sideloading a full ota image actually 3 different ones and it wouldnt I figured maybe because its beta, then I couldnt get flash all to work on a regular factory image non ota. So I was on partician b so I tried switching to partician a and after a few minutes it decided to boot the OS. I"am guessing just my auto updates wont work now since it wont boot off the one partician oh well because rooted it wont auto update any way. Oh well at least its running I"am happy with that lol.:D
I believe you have to flash SU after twrp or its doesn't work, that's my understanding anyway

Sent from my Pixel XL using Tapatalk
 

M9guy

Senior Member
Nov 9, 2014
752
194
Haha, I'm sorry but I've gotta laugh at what you've been going through. Sorry but I've done things like this going "man I must be stupid but I'm following it to a T! Haha, you can't help but laugh it off. Glad you got everything going man. :good:

Yeah its not that its bad enough to have wasted a lot of time but then people think your an idiot lol or a newbie lol which I dont have the excuse of being a newbie just being someone that read the instructions but thought I had it straight. They keep changing things lol usually after a few times doing something its like second nature but its like they keep making us go back to school lol.

---------- Post added at 04:03 PM ---------- Previous post was at 03:58 PM ----------

I believe you have to flash SU after twrp or its doesn't work, that's my understanding anyway

Sent from my Pixel XL using Tapatalk

Oh crap that makes sense, but then why did my other partician boot and I think I"am still rooted but going through a restore so once done I will know if rooted or not probably not but it did boot with twrp unless somehow the other partician had stock recovery which now I"am just guessing but who knows I sure dont lol.
 

DaveHTC200

Senior Member
Oct 2, 2008
1,635
423
Yeah its not that its bad enough to have wasted a lot of time but then people think your an idiot lol or a newbie lol which I dont have the excuse of being a newbie just being someone that read the instructions but thought I had it straight. They keep changing things lol usually after a few times doing something its like second nature but its like they keep making us go back to school lol.

---------- Post added at 04:03 PM ---------- Previous post was at 03:58 PM ----------



Oh crap that makes sense, but then why did my other partician boot and I think I"am still rooted but going through a restore so once done I will know if rooted or not probably not but it did boot with twrp unless somehow the other partician had stock recovery which now I"am just guessing but who knows I sure dont lol.
That bit I can't explain... Lol

Sent from my Pixel XL using Tapatalk
 

thewebsiteisdown

Senior Member
Mar 18, 2011
722
171
Oh crap that makes sense, but then why did my other partician boot and I think I"am still rooted but going through a restore so once done I will know if rooted or not probably not but it did boot with twrp unless somehow the other partician had stock recovery which now I"am just guessing but who knows I sure dont lol.

If you had rooted before going through the process of installing twrp it seems to skip the back up slot as far as installing twrp goes. I believe this behavior is because the system makes a backup of the current install which you rooted and then you flash stock but it doesn't backup the stock to the other slot fast enough before you go through the process of installing twrp so it hits the second slot with the back up of the old rooted rom and doesn't install twrp to that slot.

I had to set mine to boot to the other slot via twrp either temp twrp or the working twrp then install onto that slot the stock rom which wipes your data on the other slot by the way. Then I installed twrp on the slot which I had just installed the stock image on to and then bam both of my slots now have twrp.
 
Last edited:

M9guy

Senior Member
Nov 9, 2014
752
194
If you had rooted before going through the process of installing twrp it seems to skip the back up slot as far as installing twrp goes. I believe this behavior is because the system makes a backup of the current install which you rooted and then you flash stock but it doesn't backup the stock to the other slot fast enough before you go through the process of installing twrp so it hits the second slot with the back up of the old rooted rom and doesn't install twrp to that slot.

I had to set mine to boot to the other slot via twrp either temp twrp or the working twrp then install onto that slot the stock rom which wipes your data on the other slot by the way. Then I installed twrp on the slot which I had just installed the stock image on to and then bam both of my slots now have twrp.

Makes me miss Htc 10 running an RUU was always so much easier. If Htc had made a bigger screen 10 plus I would have bought it. I do like the quick updates though from google but if I could install a google play rom on an htc phone and have the best of both worlds. I guess I will just always be a Htc guy. Just hope they never go belly up.

I just know I always had an easier time with Htc software as I never had an RUU not work pop it on an sd card and pop it in the phone and go to fastboot and the phone picks it up and asks if you want to run the RUU nothing easier than that. I might just keep this phone until the next htc phone comes out if the screen is 5.5, 5.7 or 5.9/6 but not expecting them to as they never do since the htc max flop well when the idiots put the same processor in the max that was in the older smaller m7 well can you say stupid move ? 1.7 was too slow for the bigger screen max.
 

thewebsiteisdown

Senior Member
Mar 18, 2011
722
171
If you had rooted before going through the process of installing twrp it seems to skip the back up slot as far as installing twrp goes. I believe this behavior is because the system makes a backup of the current install which you rooted and then you flash stock but it doesn't backup the stock to the other slot fast enough before you go through the process of installing twrp so it hits the second slot with the back up of the old rooted rom and doesn't install twrp to that slot.

I had to set mine to boot to the other slot via twrp either temp twrp or the working twrp then install onto that slot the stock rom which wipes your data on the other slot by the way. Then I installed twrp on the slot which I had just installed the stock image on to and then bam both of my slots now have twrp.

I had an HTC Thunderbolt once. :)
 

schwem

Senior Member
Oct 15, 2014
2,215
761
35
Auburn Hills
Makes me miss Htc 10 running an RUU was always so much easier. If Htc had made a bigger screen 10 plus I would have bought it. I do like the quick updates though from google but if I could install a google play rom on an htc phone and have the best of both worlds. I guess I will just always be a Htc guy. Just hope they never go belly up.

I just know I always had an easier time with Htc software as I never had an RUU not work pop it on an sd card and pop it in the phone and go to fastboot and the phone picks it up and asks if you want to run the RUU nothing easier than that. I might just keep this phone until the next htc phone comes out if the screen is 5.5, 5.7 or 5.9/6 but not expecting them to as they never do since the htc max flop well when the idiots put the same processor in the max that was in the older smaller m7 well can you say stupid move ? 1.7 was too slow for the bigger screen max.
Skim through some Google news posts and you'll see that HTC plans to make the last of it's smartphone line spring of 2017. Looks like their setting their sight's on different ventures. I've read 3 articles now claiming HTC is dropping out of the smartphone race. Sad news and I hope it's purely speculation.
 

gone_bush

Member
Sep 4, 2014
44
0
A couple of questions:

1) I'm rooted with ElementalX so I've got to reflash the stock boot image. Will this erase my data? (I've seen some confusing posts on this matter.)

2) When booting into TWRP it appears it should ask for a password. Which password is that?
 

jaythenut

Senior Member
Sep 6, 2012
7,300
2,362
A couple of questions:

1) I'm rooted with ElementalX so I've got to reflash the stock boot image. Will this erase my data? (I've seen some confusing posts on this matter.)

2) When booting into TWRP it appears it should ask for a password. Which password is that?

Password is the the one to unlock the phone
If you flash ota should be good to keep your data
 

superchilpil

Senior Member
Sep 26, 2009
4,276
1,426
Texas
OnePlus 8 Pro
More of a correction of their own idiocy...

https://plus.google.com/+NathanBenis/posts/2hYjfsw6Koi

#WhiteUIsMustDie, #EndDarkAppOppression

@Dees_Troy

Heads up new build from a different development branch is starting to be pushed. No info yet.

https://www.reddit.com/r/GooglePixel/comments/5ebddo/pixel_update_build_npf26j/
Not sure how either of these relate to a custom recovery?
A new build doesn't put us any closer to stable, and an opinion about android and Google itself sure isn't going to either.

Sent from my Pixel XL using Tapatalk
 
  • Like
Reactions: cwalker0906

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