• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[RECOVERY][pioneer] TWRP Touch Recovery [OFFICIAL]

Search This thread

SGS3_0

Senior Member
Mar 17, 2014
258
62
Megastructure
Consider reading the source code of the thing that outputs these errors ^.^
Thanks for the help, however I appreciate the fact that you do not always respond directly, and I have to figure it out myself ...
Well. I searched and found these commits.
I don't think anyone else wants a permanent TWRP (but I need one). You just need to include the parameter "ro.secure = 0" in "prop.default".
However, I have one more question:
Where did you get the pre-created binaries (in the “device” ./sbin ./vendor) for decryption? What firmware? And why do they work on old (based on Android 8.1 builds of TWRP 3.2.1 / 3.2.2), but do not work on 3.3.1?
I mean the integration of the recovery disk into the bootram disk. 3.2.1 / 3.2.2 has been installed and works well on LOS16. But 3.3.1 stops when decrypting "data">. <??? (I can't even get a log to understand the problem). Although "fastboot boot yourimage (3.3.1) .img" works autonomously, even with the kernel that I created from the source code of the LOS16 kernel? What is your black magic?
 

LuK1337

Recognized Developer
Jan 18, 2013
8,479
16,948
Samsung Galaxy S III I9300
Moto G 2014
Thanks for the help, however I appreciate the fact that you do not always respond directly, and I have to figure it out myself ...
Well. I searched and found these commits.
I don't think anyone else wants a permanent TWRP (but I need one). You just need to include the parameter "ro.secure = 0" in "prop.default".
However, I have one more question:
Where did you get the pre-created binaries (in the “device” ./sbin ./vendor) for decryption? What firmware? And why do they work on old (based on Android 8.1 builds of TWRP 3.2.1 / 3.2.2), but do not work on 3.3.1?
I mean the integration of the recovery disk into the bootram disk. 3.2.1 / 3.2.2 has been installed and works well on LOS16. But 3.3.1 stops when decrypting "data">. <??? (I can't even get a log to understand the problem). Although "fastboot boot yourimage (3.3.1) .img" works autonomously, even with the kernel that I created from the source code of the LOS16 kernel? What is your black magic?
Consider using a magic tool called /diff/.
 

SGS3_0

Senior Member
Mar 17, 2014
258
62
Megastructure
I don't even remember, doesn't really matter tbh.

Anyway, this is very strange ... TWRP 3.3.1 decrypts the “data” of LOS16 only if recovery was separately downloaded from outside, but not as part of the boot image. But the older versions 3.2.1 and 3.2.2 do a good job of this ... it only bothers me that they are based on the previous version of android. Hmm, don't even need to use keymaster4? They simply do not have this.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,479
16,948
Samsung Galaxy S III I9300
Moto G 2014
Anyway, this is very strange ... TWRP 3.3.1 decrypts the “data” of LOS16 only if recovery was separately downloaded from outside, but not as part of the boot image. But the older versions 3.2.1 and 3.2.2 do a good job of this ... it only bothers me that they are based on the previous version of android. Hmm, don't even need to use keymaster4? They simply do not have this.
Perhaps you need to focus on something other than replacing blobs? Have you thought about /diff/ing ramdisks...?
 

SGS3_0

Senior Member
Mar 17, 2014
258
62
Megastructure
Perhaps you need to focus on something other than replacing blobs? Have you thought about /diff/ing ramdisks...?

I really don’t know how to use this console utility, but I have some experience in porting roms. For comparison of files and folders I use "WinMerge" for Win or "Meld" for Linux.
I did not understand what exactly needs to be compared: images of ramdisk bytes with bytes or their contents - files and folders? And what kind of images: different TWRPs among themselves, or the contents of the boot image(with installed TWRP) where decryption takes place and where it does not work?
I'm not as smart and experienced as you, but I really try to understand and make it work. Please answer without banter, otherwise it only confuses me more ... ^^,
 

Marteng69

Senior Member
Sep 13, 2014
61
16
@LuK1337:
TWRP version 3.3.1.2 and 3.3.1.3 do not work with a H4113. Version 3.3.1.1 is working fine.
Everytime I try to fastboot 3.3.1.2 or 3.3.1.3 the white Sony screen appears and then the screen turns to a dark blue but nothing happens. TWRP does not start.
3.3.1.3 works with H3113 without any problems.
Any hints?
 

LuK1337

Recognized Developer
Jan 18, 2013
8,479
16,948
Samsung Galaxy S III I9300
Moto G 2014
@LuK1337:
TWRP version 3.3.1.2 and 3.3.1.3 do not work with a H4113. Version 3.3.1.1 is working fine.
Everytime I try to fastboot 3.3.1.2 or 3.3.1.3 the white Sony screen appears and then the screen turns to a dark blue but nothing happens. TWRP does not start.
3.3.1.3 works with H3113 without any problems.
Any hints?

What firmware is your H4113 on? Mind messaging me somewhere? ( preferably irc/hangouts )
 
  • Like
Reactions: Marteng69

steveglowplunk

Senior Member
Sep 15, 2015
273
100
Is it just me or the latest version (twrp-3.3.1-2-pioneer) doesn't let me enter my password for decrypting the 'internal storage'?
I have set a pin password for my phone. After booting up twrp, it doesn't prompt me to enter my password for decryption. The 'internal storage' stays encrypted.
It works fine when I'm using the version twrp-3.2.3-1-pioneer.
I'm currently running LOS 15.1 (20190227)
Is there a compatibility issue with the older LOS roms?

Any updates on this? The latest version, twrp-3.3.1-6-pioneer, still won't prompt me for password for decryption. I'm still running LOS 15.1.










...
 

MysticEnforcer

Senior Member
Oct 29, 2012
618
299
Trier
Hi,
with which android version can i use twrp 3.4.0?
Flashing .zip ends with error 1 (screen 1) &
flashing via fastboot failed too (screen 2) &
bootloop fix failed also (screen 3).
 

Attachments

  • Screenshot_2020-06-25-05-09-36.png
    Screenshot_2020-06-25-05-09-36.png
    148.8 KB · Views: 97
  • Screenshot_2020-06-25-06-36-53.png
    Screenshot_2020-06-25-06-36-53.png
    159.1 KB · Views: 96
  • Screenshot_2020-06-25-06-37-34.png
    Screenshot_2020-06-25-06-37-34.png
    175.8 KB · Views: 91
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    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.



    DOWNLOAD: https://twrp.me/sony/sonyxperiaxa2.html

    BUGS:
    If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

    SUPPORT:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.

    XDA:DevDB Information
    [RECOVERY][pioneer] TWRP Touch Recovery [OFFICIAL], ROM for the Sony XA2 Ultra

    Contributors
    LuK1337
    Source Code: https://github.com/TeamWin

    ROM OS Version: 8.x Oreo

    Version Information
    Status: Testing

    Created 2018-04-06
    Last Updated 2020-06-25
    3
    Right, so "only" fastboot boot *.img, thx
    I wonder where the inbuilt Sony recovery is stored then ?
    In /boot.
    3
    Hello. I'd like to root my Xperia XA2 Ultra, and I would like to backup TA partition (Sony DRM etc.) so I can restore it after rooting. If someone can tell me how to do it, I would appreciate it.
    Thanks.
    You can't back them up, you don't really need them though. The camera works fine without them on tue XA2

    ---------- Post added at 08:09 PM ---------- Previous post was at 08:01 PM ----------

    Wait what. I've held off on rooting until the kinks get worked out. That and I haven't ever done it with a Sony device before. My understanding is that Sony DRM can be lost forever if not done correctly. What exact functionality would I lose?

    So how would I go about keeping (saving for later) the drm if possible? I'm assuming unlocking bootloader, twrp, rooting and installing xposed is normal.

    I just don't want to mess up to the point of no return. Sony drm, tremble, a/b system and google pay are anomalies I haven't dealt with before. My device is the XA2 Ultra H3223 on build 50.1.A.5.59 (latest), which means I should hold off on xposed :(. It automatically updated on me.
    Google Pay works as long as Xposed isn't installed which would be the case given the firmware you've updated to.

    Basically, you lose absolutely no functionality... Camera, Google Pay are working.

    On older Sony devices the Camera functionality was lost with the DRM info, but not on this device.
    3
    How do I install 3.2.1-1 if there is only 3.2.1-0 install zip available?
    I'm in process of getting new installer package so you just got to wait.
    2
    @LuK1337
    How does it work then, since it's an a/b device (first for Sony) i mean will twrp be booted in slot _b or how? And the Same fastboot flash, will it also flash to slot _b, meaning the inbuilt Sony recovery won't be touched (vol- + power on bootup)
    Anyway interesting, I will try it on my spare H4313
    BTW the xposed issue is related to March sec patch https://github.com/rovo89/Xposed/issues/339
    1. Fastboot boot boots as your current slot
    2. You can't fastboot flash it as there is no recovery partition.