[RECOVERY] TWRP 3.2.3-0 (poplar) [UPDATE: 2018-07-30]

Search This thread

hungvip2001

Senior Member
Jul 12, 2016
531
145
Hoa Binh
Hello, guys. I just in installed this TWRP
I see system is not mount, and when install some mod with TWRP, it say error
Do I need to mount system, oem, vendor,... to use ?
 

Miustone

Senior Member
Jul 23, 2012
3,355
6,184
30
Google Pixel 7 Pro
Hey @modpunk, thanks for Your work for our Xperias! I was wondering about AROMA on the XZ1 Devices since TWRP on the XZ Premium has Issues with it. I would really like to provide My Work with AROMA again but unfortunately is AROMA not functional on our Devices. Is there any Chance You could fix it for us? I tried every possible configuration and i'm 99% sure it is TWRP. I'm glad it works that good besides that, but AROMA is really a great Thing for all Users and it would mean a lot to Me to have that Option again...

Maybe are You willed and aware how to make it work!? Anyways, thanks again! :)
 

hungvip2001

Senior Member
Jul 12, 2016
531
145
Hoa Binh
Hey @modpunk, thanks for Your work for our Xperias! I was wondering about AROMA on the XZ1 Devices since TWRP on the XZ Premium has Issues with it. I would really like to provide My Work with AROMA again but unfortunately is AROMA not functional on our Devices. Is there any Chance You could fix it for us? I tried every possible configuration and i'm 99% sure it is TWRP. I'm glad it works that good besides that, but AROMA is really a great Thing for all Users and it would mean a lot to Me to have that Option again...

Maybe are You willed and aware how to make it work!? Anyways, thanks again! :)
+1
Aroma is a good feature
 

Miustone

Senior Member
Jul 23, 2012
3,355
6,184
30
Google Pixel 7 Pro
+1
Aroma is a good feature

Still working and provided on many Devices. I used the 3.0 Beta as Base for Years and made pretty nice Installers with it. Could be also attractive for other Devs to create ROMs and Stuff with AROMA again (Looks like many are aware of this Problem). I'm really wondering why this wasn't communicated before and why no One has fixed it already. Looks like a lack of testing for Me... (Don't blame anyone, it just can happen)
 

hungvip2001

Senior Member
Jul 12, 2016
531
145
Hoa Binh
Hello, guys.
I have some performance problems and I want to repair my phone. But I can't use Sony companion.:(
So I think I can wipe partions with TWRP then use newflasher to reflash stock firmware.
Can I do that?:confused:
 

oF2pks

Senior Member
May 22, 2016
819
1,116
Magisk & DRM fix

179 new May Xperia build is up : as always encryption scramble sdcard with April twrp, BUT you can strike 1 chance only to upgrade patched/Magisk from a 145 or previous :
Code:
-WITHOUT userdata.. & fotakernel.. sin, use newflasher + 179 (XperiFirm.exe) 
-DON'T REBOOT Xperia [SIZE="1"](<-- scramble otherwise !)[/SIZE]
-reboot FIRST to April twrp
-flash 3 janjan's zip: 2patching +3Magisk +4kernel_permissive (wipe dalvik/cache)
-reboot Xperia
-(upgrade Magisk app to pass SafetyNet)
Now if you reboot twrp, you will notice scramble sdcard again, and thus no more possibility of patched upgrade, until a twrp with working decryption (except if you restore a patched 145 backup and skip 179 straight to next iteration...)

btw @modpunk , 1000Thx for your twrp github source , I was able to build April's with busybox, and for aosp-ota.zip use, I have added /vendor for Wipe + /oem for Flash image.
EDIT : just spoof Los to 2018-05-05 and now, my May twrp build finally decrypts 179 as well !!
 

Attachments

  • twrp.fstab.txt
    1.9 KB · Views: 51
Last edited:

snake218

Senior Member
Nov 1, 2012
591
154
179 new May Xperia build is up : as always encryption scramble sdcard with April twrp, BUT you can strike 1 chance only to upgrade patched/Magisk from a 145 or previous :
Code:
-WITHOUT userdata.. & fotakernel.. sin, use newflasher + 179 (XperiFirm.exe) 
-DON'T REBOOT Xperia [SIZE="1"](<-- scramble otherwise !)[/SIZE]
-reboot FIRST to April twrp
-flash 3 janjan's zip: 2patching +3Magisk +4kernel_permissive (wipe dalvik/cache)
-reboot Xperia
-(upgrade Magisk app to pass SafetyNet)
Now if you reboot twrp, you will notice scramble sdcard again, and thus no more possibility of patched upgrade, until a twrp with working decryption (except if you restore a patched 145 backup and skip 179 straight to next iteration...)

btw @modpunk , 1000Thx for your twrp github source , I was able to build April's with busybox, and for aosp-ota.zip use, I have added /vendor for Wipe + /oem for Flash image.
EDIT : just spoof Los to 2018-05-05 and now, my May twrp build finally decrypts 179 as well !!

May i ask, so the version you posted works with latest 179 (decrypt) and we don't have to install busybox on it?
 

.LEONARDO.

Senior Member
Aug 24, 2011
72
4
Manaus
I may be doing something wrong... I downloaded the following files to the same directory:

"gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D"
"twrp-3.2.1-0-poplar-7.img.asc.txt" (833b) and renamed it to "recovery.img.asc"
"twrp-3.2.1-0-poplar-7.img" (29mb) and renamed it to "recovery.img"

Then I tried the command "gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc" at the directory but got the message "command" is not recognized as an internal or external command, operable program or batch file.

Can I flash "recovery.img" without verifying it?

Thanks!
 
  • Like
Reactions: hungvip2001

.LEONARDO.

Senior Member
Aug 24, 2011
72
4
Manaus
"your device has been unlocked and can't be trusted" message just turned to
"Your device has failed verification and will not work properly" and powers off in 5 seconds.

I flashed TWRP and managed to boot from it, but no passwords were asked again.
Alternatively, can I flash boot.img by twrp?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    TWRP

    This project provides the TWRP recovery for for the Sony Xperia XZ1 (poplar).

    FEATURES

    • File-Based Encryption (FBE) support
    • EXT4 support
    • F2FS support
    • EXFAT support
    • Provides unzip
    • Additional languages

    FBE encryption should be related to the security patch level anymore. The android version and patch level is extracted from the system partition and set in the recovery.

    DOWNLOAD

    Make sure you download the .img and corresponding .asc.txt file (see INTEGRITY)!

    You can always find the latest version of the recovery HERE.

    INTEGRETY

    The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.

    How do you do that?

    1. Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
    2. Download the recovery.img and recovery.img.asc.txt file
    3. Rename the recovery.img.asc.txt file to recovery.img.asc
    4. Verfiy the signature using the following command:
      Code:
      gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc

    A good tutorial is: How to verify signatures for packages from the Tor Project.

    XDA:DevDB Information
    recovery_twrp_sony_poplar, Tool/Utility for the Sony Xperia XZ1

    Contributors
    modpunk, Dees_Troy
    Source Code: https://github.com/cryptomilk/android_device_sony_poplar


    Version Information
    Status: Stable
    Current Stable Version: 3.2.3-0
    Stable Release Date: 2018-07-30

    Created 2017-12-30
    Last Updated 2018-07-30
    9
    I've uploaded a new TWRP recovery version 3.2.3-0

    • enable md5sum digest verification
    • adb backup fixes
    • OTA style update zips will now install automatically without prompting for decrypt
    • minor tweaks to handling date/time on Qualcomm devices
    • updates to some language translations
    8
    I've uploaded a new recovery which should fix FBE decryption till the year 2025. :)
    8
    New version up. Will build April soon too.
    7
    I've released a new recovery. This should not be tied to the security patch level anymore. The recovery now reads the required values from the system partition.