[RECOVERY][Android 10/11][Stock/SODP][XZ2/C/P/3] TWRP 3.4.0-0 [UNofficial]

Should I continue this project?

  • Yes, for the XZ2.

    Votes: 103 39.5%
  • Yes, for the XZ2C.

    Votes: 83 31.8%
  • Yes, for the XZ2P.

    Votes: 23 8.8%
  • Yes, for the XZ3.

    Votes: 52 19.9%
  • No.

    Votes: 0 0.0%

  • Total voters
    261
Search This thread

MartinX3

Recognized Contributor
Sep 14, 2014
5,719
2,829
Mars
martinx3.github.io
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!


Code:
#include <std_disclaimer.h>
/*
 *
 * 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 ROM
 * 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.
 *
 */

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.

FAQ:
  • Just wiping your phone in TWRP lead into an encrypted & not readable userdata in the stock system.
    You need to open advanced wiping and check the entries data and internal storage.
    Of course clear the dalvik, too.
  • If you backed up system and/or vendor partitions and you want to restore them, make sure that TWRP setting "Use rm -rf instead of formatting" is set!.
  • If after the usage of NewFlasher or the OTA Updater or something else, which installs stock firmware parts you get stuck into the TWRP or SONY Logo, you need again to disable the verification with the vbmeta.img file and its parameters in fastboot.
  • fastboot & adb
  • Weird problems not easily to reproduce by other users require that you make sure, that you
    • Use the newest platform tools (adb & fastboot)
    • Downloaded the newest firmware via Xperifirm from XDA and installed the newest firmware via Newflasher from XDA
  • Newflasher from XDA
  • Xperifirm from XDA
  • Removing the stock bloat apps via titanium backup may result in a boot loop. Use a file explorer to remove them, disable them or try to use my unfinished bloat removal script at github.
  • Your phone reboots into recovery, instead of system? Maybe it crashed too often due to a wrong installation or whatever?
    In TWRP:
    • Code:
      cat /dev/block/bootdevice/by-name/misc
      shows you the reason.
    • TWRP -> [WIPE] -> [Advanced Wipe] -> Tick only the misc -> [Swipe to Wipe]

Known Bugs:
  • The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
    You can also "fastboot reboot bootloader" in the blue fastboot mode.
    This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
  • If "fastboot boot twrp.img" results into a blackscreen and reboot of the phone, take a look if you modified the DTBO partition.
    It requires a special TWRP for every modified kernel/dtbo until I find some way to unify the twrp kernel with the DTBO (if the bootloader supports it).

Bugtracker:

Bugreport:
  • A bugreport needs your device name, dmesg, the /tmp/recovery.log and a way to reproduce the issue.
    If possible use
    Code:
    logcat -b all
    instead of just a dmesg.
    • If ADB is not working to provide logs
      • VOLUP+POWER for 1 Seconds -> Forced crash to create a pstore
      • Boot the normal system.
      • Give me the files in
        Code:
        /sys/fs/pstore/
  • If the TWRP is stuck at the TWRP logo, the chances are high, that the decryption didn't succeed.
  • To rescue a not responding phone:
    • VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
    • VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
    • VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.

Thank you very much for your help, code contribution & testing! (Random order):
  • @dees_troy and his team of volunteers for the TWRP code
  • @dhacke thank your for providing a download server
  • Shame on me if I forgot someone after searching through the thread and my PM's!
  • And many thanks to the few donators! :)

A telegram group for technical SODP stuff:
https://t.me/xda_tv

XDA:DevDB Information
TWRP, ROM for the Xperia XZ2

Contributors
MartinX3, Sony
Source Code: https://github.com/MartinX3-AndroidDevelopment

ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Newest recommended
Based On: AOSP

Version Information
Status: Stable
Current Stable Version: 3.4.0-0
Stable Release Date: 2020-06-13

Created 2020-03-29
Last Updated 2020-06-20
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,719
2,829
Mars
martinx3.github.io
Download & Installation

Download:

Installation:
  1. Update to newest stock firmware before unlocking!!!
  2. Unzip the *.gz files with https://7-zip.org/ or Linux.
  3. Enter fastboot via software, not hardware buttons. See "Known Bugs".
  4. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
  5. fastboot boot twrp.img
  6. Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
  7. Reboot into installed TWRP
  8. Want Root? -> Magisk
  9. (Only if your phone doesn't boot to system anymore) Advanced menu -> "Fix recovery bootloop"
  10. (Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)
 
Last edited:

MartinX3

Recognized Contributor
Sep 14, 2014
5,719
2,829
Mars
martinx3.github.io
News

02.03.2021

Reuploaded the SODP TWRP with a workaround for Android 11 compatibility.

15.06.2020
reuploaded the stock twrp for the xz2 premium with a completely fixed touch.

14.06.2020
reuploaded the stock twrp with a later touch kernel modules initialization.
Hopefully fixing the randomly happening not working touch.

13.06.2020
thanks to the fixes in 3.4.0 we got now a twrp with the following enhancements for stock and sodp:

- this twrp will work with future 10.0 roms, you don't need a new build matching the security patch level of your rom.
- you can install this twrp again with the buildin ramdisk patcher. Please follow the installation instructions.

11.06.2020
switch to twrp 3.4.0
sodp twrp 2020-06 security patch level
stock twrp 2020-05 security patch level for firmware 52.1.a.2.1

now both twrp should work without a rom being installed (empty system/vendor/oem partitions) and still be able to decrypt your userdata.
Also the stock twrp touch should now always work instead of playing russian roulette.

11.05.2020
reuploaded sodp twrp for 2020-05 security patch level.
It didn't boot with the newest aosp.

07.05.2020
sodp twrp for 2020-05 security patch level.

14.04.2020
removed stock twrp for firmware 52.1.a.0.672 until sony releases the kernel sources of the new security patch level.
Otherwise the keymaster won't decrypt the userdata for twrp and twrp gets stuck on the twrp logo.

13.04.2020
stock twrp for firmware 52.1.a.0.672
sodp twrp for 2020-04 security patch level

hopefully fixed the touch problems of the stock twrp

fixed the forced read only partition mountings of system, vendor, odm

31.03.2020
stock twrp for firmware 52.1.a.0.618

30.03.2020
sodp twrp for 2020-03 security patch level
installing in ramdisk (to make it persistent) is impossible at the moment, because it is a 9.0 twrp which makes its ramdisk incompatible to the rom.

Of course monthly twrp releases in sync with the current patch level need to be released or i would need to remove the userdata decryption completely.


The stock twrp will follow, after it became ready.
 
Last edited:

MartinX3

Recognized Contributor
Sep 14, 2014
5,719
2,829
Mars
martinx3.github.io
30.03.2020
SODP TWRP for 2020-03 security patch level
Installing in Ramdisk (to make it persistent) is impossible at the moment, because it is a 9.0 TWRP which makes its ramdisk incompatible to the ROM.

Of course monthly TWRP releases in sync with the current patch level need to be released or I would need to remove the userdata decryption completely.


The Stock TWRP will follow, after it became ready.

PS: AndroidFileHost blocked me for doing too many actions at the same time.
Maybe I can upload it there tomorrow.

Done
 
Last edited:

MartinX3

Recognized Contributor
Sep 14, 2014
5,719
2,829
Mars
martinx3.github.io
xz3 twrp won't boot, sodp version is good but there's no install on ramdisk?:confused::confused:

You mean SODP TWRP works, but not the stock TWRP on your XZ3?

You are stuck on sony logo?
Or on TWRP logo?

I need a bugreport with "logcat -b all" via adb.

Install ramdisk doesn't work at the moment, because it is a TWRP 9.0 hack, since TWRP 10.0 is ready.
But I wrote it in the news :p

Edit:
Reworked the thread a bit for more clarification :)
 
Last edited:

MartinX3

Recognized Contributor
Sep 14, 2014
5,719
2,829
Mars
martinx3.github.io
@MartinX3 Great job as always bro! :good:

I ran it on my XZ2 (stock 52.1.A.0.618).
Phone has booted to the twrp screen (till the unlock pattern), but the touch is not working (log).
I didn't start from scratch (fresh install), for the record.

Tia!

Thank you :)

Are you sure the touch doesn't work?
I tested this release on the same firmware on my XZ2 in stock.
This confuses me now.

You booted stock .618 before and you tried to deactivate & activate the display?

Here it worked right out of the box.





And if it happens again, could you execute "start preptouch"
And if that not works, could you execute "/sbin/preptouch.sh"?
 
Last edited:
  • Like
Reactions: serajr

serajr

Recognized Developer / Recognized Themer
Apr 21, 2011
5,021
18,614
São Paulo - SP
[...] Are you sure the touch doesn't work?
And if it happens again, could you execute "start preptouch"
And if that not works, could you execute "/sbin/preptouch.sh"?

I am. I have tried at least three times so far. Tried turning off and on the screen, but the slide to unlock didn't work, too.
"start preptouch", no response, no working touch
"/sbin/preptouch.sh"...
Code:
insmod: failed to load /sbin/clearpad_rmi_dev.ko: File exists
insmod: failed to load /sbin/clearpad_core.ko: File exists
insmod: failed to load /sbin/clearpad_i2c.ko: File exists
akari:/sbin # ls -l

Tia again
 
Last edited:
  • Like
Reactions: MartinX3

MartinX3

Recognized Contributor
Sep 14, 2014
5,719
2,829
Mars
martinx3.github.io
I am. I have tried at least three times so far. Tried turning off and on the screen, but the slide to unlock didn't work, too.
"start preptouch", no response, no working touch
"/sbin/preptouch.sh"...
Code:
insmod: failed to load /sbin/clearpad_rmi_dev.ko: File exists
insmod: failed to load /sbin/clearpad_core.ko: File exists
insmod: failed to load /sbin/clearpad_i2c.ko: File exists
akari:/sbin # ls -l

Tia again
And the service menu of android should also say that you use the clearpad driver.

And I assume the 9.0 stock twrp did always touch fine?

The script say that the kernel modules for the touch driver got loaded and I assume the sys path in the script file got executed too, after loading the .ko files.

And you have a normal European firmware?

That's now a mystery for me why it works for me and others, but not in your phone
Especially if you have the clearpad touch hardware
 
  • Like
Reactions: serajr

serajr

Recognized Developer / Recognized Themer
Apr 21, 2011
5,021
18,614
São Paulo - SP
And the service menu of android should also say that you use the clearpad driver.

And I assume the 9.0 stock twrp did always touch fine?

The script say that the kernel modules for the touch driver got loaded and I assume the sys path in the script file got executed too, after loading the .ko files.

And you have a normal European firmware?


That's now a mystery for me why it works for me and others, but not in your phone
Especially if you have the clearpad touch hardware
I got the touch working after copying the three .ko libs to the ramdisk /sbin folder, and a small editing (below) in the permissive.sh (also removed "$touch_id" == "3" from preptouch.sh).
Code:
setenforce 0

insmod /sbin/clearpad_rmi_dev.ko
insmod /sbin/clearpad_core.ko
insmod /sbin/clearpad_i2c.ko
echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start
I know this is an awful workaround, but maybe this give you some hint (or sets you more confusing yet :p )
I'm with the sony stock customized_br fw, as always!
 
Last edited:

MartinX3

Recognized Contributor
Sep 14, 2014
5,719
2,829
Mars
martinx3.github.io
I got the touch working after copying the three .ko libs to the ramdisk /sbin folder, and a small editing (below) in the permissive.sh (also removed "$touch_id" == "3" from preptouch.sh).
Code:
setenforce 0

insmod /sbin/clearpad_rmi_dev.ko
insmod /sbin/clearpad_core.ko
insmod /sbin/clearpad_i2c.ko
echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start
I know this is an awful workaround, but maybe this give you some hint (or sets you more confusing yet :p )
I'm with the sony stock customized_br fw, as always!

Ah you have a XZ2C, not a XZ2?
Because the removed ID 3 is for the XZ2 with clearpad touch.



But the script did already copy the .ko files into your /sbin before and executed the same code, you did now manually.
And according to your logs the setenforce 0 was already executed earlier.

So you just did the same the script did.

Well, yes you confuse me more :p


Could you try to just execute "echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start" if the touch doesn't work again?
I wonder if the initialization is too early on your device.
Then I could try to delay the preptouch service to a later stage of the device boot.
 
  • Like
Reactions: serajr

serajr

Recognized Developer / Recognized Themer
Apr 21, 2011
5,021
18,614
São Paulo - SP
Ah you have a XZ2C, not a XZ2?
Because the removed ID 3 is for the XZ2 with clearpad touch.

But the script did already copy the .ko files into your /sbin before and executed the same code, you did now manually.
And according to your logs the setenforce 0 was already executed earlier.

So you just did the same the script did.

Well, yes you confuse me more :p


Could you try to just execute "echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start" if the touch doesn't work again?
I wonder if the initialization is too early on your device.
Then I could try to delay the preptouch service to a later stage of the device boot.
I have a regular XZ2 (H8216), and its touch_id is 3 (customized_br fw), so I removed the Id 3.
"Could you try to just execute..." I've already tried that, with no success.
"Then I could try to delay the preptouch..." Cool... As you could notice, it worked here with that awful way I did it, so why not?
:good:
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,719
2,829
Mars
martinx3.github.io
I have a regular XZ2 (H8216), and its touch_id is 3 (customized_br fw), so I removed the Id 3.
"Could you try to just execute..." I've already tried that, with no success.
"Then I could try to delay the preptouch..." Cool... As you could notice, it worked here with that awful way I did it, so why not?
:good:

But you tried it also yourself later.
You executed the script again without success at a later stage.

And adding it to the permissive.sh is like executing the script, just earlier.

I assume `cat /sys/devices/dsi_panel_driver/panel_id` gives you the "3" as result?
 
  • Like
Reactions: serajr

serajr

Recognized Developer / Recognized Themer
Apr 21, 2011
5,021
18,614
São Paulo - SP
But you tried it also yourself later.
You executed the script again without success at a later stage.

And adding it to the permissive.sh is like executing the script, just earlier.

I assume `cat /sys/devices/dsi_panel_driver/panel_id` gives you the "3" as result?
I ran the scripts/codes manually in the trwp root shell (with the no working touch screen).
Yep, running the script earlier (permissive.sh) did the trick (*.ko files in the ramdisk).
And 3 is the output of the panel_id (that's why I removed the 3 from the preptouch.sh).

Edit: I've noticed this...
The permissions of the libs copied from vendor to sbin (preptouch), as you could see here
Code:
-rw------- 1 root root 1070630 1972-01-22 17:46 clearpad_core.ko
-rw------- 1 root root  251702 1972-01-22 17:46 clearpad_i2c.ko
-rw------- 1 root root  296934 1972-01-22 17:46 clearpad_rmi_dev.ko

Patched twrp
Code:
-rwxrwxrwx 1 root root 1070902 2020-04-02 21:48 clearpad_core.ko
-rwxrwxrwx 1 root root  251830 2020-04-02 21:48 clearpad_i2c.ko
-rwxrwxrwx 1 root root  297054 2020-04-02 21:48 clearpad_rmi_dev.ko

Edit 2: chmod on copied files did the trick (preptouch.sh) - but sometimes still not working (need to boot twice, three times...):
Code:
#XZ2 "3" XZ2C "4" Clearpad
if [[ "$touch_id" == "3" ]] || [[ "$touch_id" == "4" ]]; then
    cp /v/lib/modules/clearpad_rmi_dev.ko /sbin/
    cp /v/lib/modules/clearpad_core.ko /sbin/
    cp /v/lib/modules/clearpad_i2c.ko /sbin/

    [B]chmod 777 /sbin/clearpad_rmi_dev.ko
    chmod 777 /sbin/clearpad_core.ko
    chmod 777 /sbin/clearpad_i2c.ko[/B]

    insmod /sbin/clearpad_rmi_dev.ko
    insmod /sbin/clearpad_core.ko
    insmod /sbin/clearpad_i2c.ko
    echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start
fi
Maybe you find out a more elegant way to handle with that!


Edit 3:
I also got it permanently installed on kernel (combo keys does work, too), it's a bit tricky I gotta say, but it works.
You know, twrp's ramdisk.cpio kernel hack (old install procedure).
 
Last edited:
  • Like
Reactions: Beetle84

Klaus N.

Senior Member
Oct 14, 2012
1,289
689
Nuremberg
Hi Martin,
just wanted to let you know that your latest version for Sony stock (0.618 fw) does also not work for me (touch does not respond). Even 'fastboot reboot bootloader' before 'fastboot boot twrp-xz2.img' doesn't change anything.

Device:
Xperia XZ2 (H8216) running Android 10 stock (52.1.A.0.618)
Customized CH
Clearpad Touch version: 3
 
  • Like
Reactions: serajr

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :)
    Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!


    Code:
    #include <std_disclaimer.h>
    /*
     *
     * 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 ROM
     * 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.
     *
     */

    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.

    FAQ:
    • Just wiping your phone in TWRP lead into an encrypted & not readable userdata in the stock system.
      You need to open advanced wiping and check the entries data and internal storage.
      Of course clear the dalvik, too.
    • If you backed up system and/or vendor partitions and you want to restore them, make sure that TWRP setting "Use rm -rf instead of formatting" is set!.
    • If after the usage of NewFlasher or the OTA Updater or something else, which installs stock firmware parts you get stuck into the TWRP or SONY Logo, you need again to disable the verification with the vbmeta.img file and its parameters in fastboot.
    • fastboot & adb
    • Weird problems not easily to reproduce by other users require that you make sure, that you
      • Use the newest platform tools (adb & fastboot)
      • Downloaded the newest firmware via Xperifirm from XDA and installed the newest firmware via Newflasher from XDA
    • Newflasher from XDA
    • Xperifirm from XDA
    • Removing the stock bloat apps via titanium backup may result in a boot loop. Use a file explorer to remove them, disable them or try to use my unfinished bloat removal script at github.
    • Your phone reboots into recovery, instead of system? Maybe it crashed too often due to a wrong installation or whatever?
      In TWRP:
      • Code:
        cat /dev/block/bootdevice/by-name/misc
        shows you the reason.
      • TWRP -> [WIPE] -> [Advanced Wipe] -> Tick only the misc -> [Swipe to Wipe]

    Known Bugs:
    • The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
      You can also "fastboot reboot bootloader" in the blue fastboot mode.
      This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
    • If "fastboot boot twrp.img" results into a blackscreen and reboot of the phone, take a look if you modified the DTBO partition.
      It requires a special TWRP for every modified kernel/dtbo until I find some way to unify the twrp kernel with the DTBO (if the bootloader supports it).

    Bugtracker:

    Bugreport:
    • A bugreport needs your device name, dmesg, the /tmp/recovery.log and a way to reproduce the issue.
      If possible use
      Code:
      logcat -b all
      instead of just a dmesg.
      • If ADB is not working to provide logs
        • VOLUP+POWER for 1 Seconds -> Forced crash to create a pstore
        • Boot the normal system.
        • Give me the files in
          Code:
          /sys/fs/pstore/
    • If the TWRP is stuck at the TWRP logo, the chances are high, that the decryption didn't succeed.
    • To rescue a not responding phone:
      • VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
      • VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
      • VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.

    Thank you very much for your help, code contribution & testing! (Random order):
    • @dees_troy and his team of volunteers for the TWRP code
    • @dhacke thank your for providing a download server
    • Shame on me if I forgot someone after searching through the thread and my PM's!
    • And many thanks to the few donators! :)

    A telegram group for technical SODP stuff:
    https://t.me/xda_tv

    XDA:DevDB Information
    TWRP, ROM for the Xperia XZ2

    Contributors
    MartinX3, Sony
    Source Code: https://github.com/MartinX3-AndroidDevelopment

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Newest recommended
    Based On: AOSP

    Version Information
    Status: Stable
    Current Stable Version: 3.4.0-0
    Stable Release Date: 2020-06-13

    Created 2020-03-29
    Last Updated 2020-06-20
    10
    Download & Installation

    Download:

    Installation:
    1. Update to newest stock firmware before unlocking!!!
    2. Unzip the *.gz files with https://7-zip.org/ or Linux.
    3. Enter fastboot via software, not hardware buttons. See "Known Bugs".
    4. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    5. fastboot boot twrp.img
    6. Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
    7. Reboot into installed TWRP
    8. Want Root? -> Magisk
    9. (Only if your phone doesn't boot to system anymore) Advanced menu -> "Fix recovery bootloop"
    10. (Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)
    10
    This means TWRP for 52.1.A.2.1?
    Yes
    I'm working on it this week plus a refactoring of the twrp device tree
    8
    The refactoring for the SODP twrp is now completed.
    It'll work without a flashed ROM (vendor/system/oem partition)
    Here runs now a nice 3.4.0 TWRP (new version since today)

    Now what's left
    - the STOCK TWRP touch driver refactoring, since the touch drivers aren't in the stock kernel, but external kernel modules which get started by bash scripts in stock.....
    - stock twrp without decryption to always work
    - sodp twrp without decryption to always work
    6
    News

    02.03.2021

    Reuploaded the SODP TWRP with a workaround for Android 11 compatibility.

    15.06.2020
    reuploaded the stock twrp for the xz2 premium with a completely fixed touch.

    14.06.2020
    reuploaded the stock twrp with a later touch kernel modules initialization.
    Hopefully fixing the randomly happening not working touch.

    13.06.2020
    thanks to the fixes in 3.4.0 we got now a twrp with the following enhancements for stock and sodp:

    - this twrp will work with future 10.0 roms, you don't need a new build matching the security patch level of your rom.
    - you can install this twrp again with the buildin ramdisk patcher. Please follow the installation instructions.

    11.06.2020
    switch to twrp 3.4.0
    sodp twrp 2020-06 security patch level
    stock twrp 2020-05 security patch level for firmware 52.1.a.2.1

    now both twrp should work without a rom being installed (empty system/vendor/oem partitions) and still be able to decrypt your userdata.
    Also the stock twrp touch should now always work instead of playing russian roulette.

    11.05.2020
    reuploaded sodp twrp for 2020-05 security patch level.
    It didn't boot with the newest aosp.

    07.05.2020
    sodp twrp for 2020-05 security patch level.

    14.04.2020
    removed stock twrp for firmware 52.1.a.0.672 until sony releases the kernel sources of the new security patch level.
    Otherwise the keymaster won't decrypt the userdata for twrp and twrp gets stuck on the twrp logo.

    13.04.2020
    stock twrp for firmware 52.1.a.0.672
    sodp twrp for 2020-04 security patch level

    hopefully fixed the touch problems of the stock twrp

    fixed the forced read only partition mountings of system, vendor, odm

    31.03.2020
    stock twrp for firmware 52.1.a.0.618

    30.03.2020
    sodp twrp for 2020-03 security patch level
    installing in ramdisk (to make it persistent) is impossible at the moment, because it is a 9.0 twrp which makes its ramdisk incompatible to the rom.

    Of course monthly twrp releases in sync with the current patch level need to be released or i would need to remove the userdata decryption completely.


    The stock twrp will follow, after it became ready.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone