[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: 141 35.3%
  • Yes, for the XZ2C.

    Votes: 134 33.5%
  • Yes, for the XZ2P.

    Votes: 33 8.3%
  • Yes, for the XZ3.

    Votes: 92 23.0%
  • No.

    Votes: 0 0.0%

  • Total voters
    400
Search This thread

Ermann123

Senior Member
Apr 30, 2020
104
17
First, thank you for taking the time to write up these instructions!
Background I am using a XZ2c android 10 with TWRP recovery installed

per the instructions I installed Magisk v23.0 successfully using TWRP but as soon as I open the app it says "upgrade to finish the install" and it does an update to V24.3
On the home screen under Magisk Installed it says N/A. Zygisk: No Ramdisk: Yes.
Under App it says Latest 24.3 Installed 24.3
Do I have to keep the app from updating somehow?

Any help would be really appreciated, thanks
You could try to flash v24.1 and then upgrade to latest via app after reboot
 

typ44q

Senior Member
Aug 3, 2010
130
6
You could try to flash v24.1 and then upgrade to latest via app after reboot
Is the problem with 24.3 just in the initial install? So is it ok to install 23.0 or 24.1 and then let it update itself to 24.3? Also why does it say NA for installed when I used 23.0 and let it update itself
 

Ermann123

Senior Member
Apr 30, 2020
104
17
Is the problem with 24.3 just in the initial install? So is it ok to install 23.0 or 24.1 and then let it update itself to 24.3? Also why does it say NA for installed when I used 23.0 and let it update itself
No clue, why!
Updating from 23 to 24.3 for me didnt work. For incremental updates via app, you need to install the corresponding apk which the version to which you want to update. You could try, but without garantee, that you are going to make it to 24.3
 

toto4c19

Member
Oct 15, 2020
6
1
Hi typ44q,

I am still using V23.0 for my Xperia XZ3. Not sure why it auto upgrades to V24.3 in your case. I am guessing maybe you connected to internet before reboot. Try not connecting to internet before you finish the whole install and see whether it helps.

Thanks and regards,
Toto
 

way1212

Member
Apr 1, 2022
12
0
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:
  • 错误报告需要您的设备名称、dmesg、/tmp/recovery.log 和重现问题的方法。
    如果可能,请使用
    Code:
    logcat -b all
    而不仅仅是 dmesg。
    • 如果 ADB 无法提供日志
      • VOLUP+POWER 1 秒 -> 强制崩溃创建 pstore
      • 引导正常系统。
      • Code:
        /sys/fs/pstore/
        中的文件给我
  • 如果 TWRP 卡在 TWRP 标志上,则很有可能解密失败。
  • 要抢救没有响应的电话:
    • VOLUP+POWER 3 秒 -> 通过一次振动重新启动。
    • VOLUP+POWER 20 秒 -> 关闭 3 次振动。
    • VOLUP+POWER+CAMERA 30 秒 -> 通过对电容器放电来关闭硬件。

非常感谢您的帮助、代码贡献和测试!(随机顺序):
  • @dees_troy 和他的 TWRP 代码志愿者团队
  • @dhacke 感谢您提供下载服务器
  • 如果我在搜索线程和我的 PM 后忘记了某人,我会感到羞耻!
  • 非常感谢少数捐赠者!:)

技术 SODP 的电报组:

XDA:DevDB 信息
TWRP,用于 Xperia XZ2 的 ROM

贡献者
马丁X3,索尼
源代码: https ://github.com/MartinX3-AndroidDevelopment

ROM 操作系统版本: Android 10
ROM内核: Linux 4.x
所需的 ROM 固件:推荐的最新版本
基于: AOSP

版本信息
状态:
稳定
当前稳定版本: 3.4.0-0
稳定版发布日期: 2020-06-13

创建于2020-03-29
最后更新时间2020-06-20
请问,能不能做一个安卓11和安卓12通用的TWRP
 

SerdarAD

New member
Apr 22, 2022
1
0
hello, sorry if there is the same question. Is there TWRP for linage os 18.1 xz2c?AOSP not working, or i am doing something wrong?
Or i need to use this TWRP?
 
Last edited:

gerstavros

Senior Member
May 30, 2012
768
117
Athens
When installing this TWRP, touch on recovery works only if the phone is on charging. What am i doing wrong?
 
Last edited:

sinommo

Member
Nov 9, 2018
29
4
Stock, SODP, device, os version, oem version, logs?
Hi Martin! So happy when u still supporting your theard :)

I'm using SOV37 (Au) and used a code with 22$ fee to put my phone to unlock allowed Yes.

Now i'm running H8216 stock build number : 52.1.A.0.618
Unlocked bootloader

After try to install TWRP of you at the first time boot to TWRP by twrp.img , all good , but after install recovery ramdisk image and reboot to TWRP again touch screen isn't work.
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,958
3,016
Mars
martinx3.github.io
Hi Martin! So happy when u still supporting your theard :)

I'm using SOV37 (Au) and used a code with 22$ fee to put my phone to unlock allowed Yes.

Now i'm running H8216 stock build number : 52.1.A.0.618
Unlocked bootloader

After try to install TWRP of you at the first time boot to TWRP by twrp.img , all good , but after install recovery ramdisk image and reboot to TWRP again touch screen isn't work.
You're welcome

Maybe your stock touch drivers aren't compatible
At least the booting works

It worked on my h8296 with German firmware 52.1.A.3.49
 
  • Like
Reactions: sinommo

Top Liked Posts

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