Yes but I only support the newest android version
If previous ones work it's a nice side effect
Please stay tuned In the twrp 10 thread
-
Introducing XDA Computing: Discussion zones for Hardware, Software, and more! Check it out!
If previous ones work it's a nice side effect
Please stay tuned In the twrp 10 thread
Ok, so I suppose I would have to test this on my own? If so, could it lead to damage or data loss of any kind if the TWRP version is not compatible with the Android 8 ROM you provided? Or could I just re-flash with the provided version 3.2.3?Yes but I only support the newest android version
If previous ones work it's a nice side effect
Please stay tuned In the twrp 10 thread
You don't need to flash it to test
"fastboot boot twrp.img" is enough
And if it works you can follow the instructions to install it on the phone
I tried to restore from a twrp backup and it resorted to a bootloop. What is to be wiped and what is to be restored? Dalvik, System and Data was wiped and Boot, System and Data was restored. This is Android 9 installed on H8216.
I wrote on the other thread - the duplicate is unintended.
I wrote on the other thread - the duplicate is unintended.
I unfortunately didn't read carefully enough (even though it is clearly stated on both the OP and the lineage how to page ) and unlocked the bootloader before updating it to the latest android. The phone is still on 8.0
So question is - what are the implications of that mistake? My goals were to install TWRP, LineageOS and Magisk... - can I still reach this goal?
) and unlocked the bootloader before updating it to the latest android. The phone is still on 8.0So question is - what are the implications of that mistake? My goals were to install TWRP, LineageOS and Magisk... - can I still reach this goal?
Last edited:
YesI unfortunately didn't read carefully enough (even though it is clearly stated on both the OP and the lineage how to page
So question is - what are the implications of that mistake? My goals were to install TWRP, LineageOS and Magisk... - can I still reach this goal?
You just killed the DRM for the stock Rom
But if you ignore the stock Rom, youst flash and Boot the newest stock 10 until you reach the desktop apps.
Thanks alot
- yes, I don't care about stock ROM. Anyway thanks for answering - seems I posted in the wrong thread and will aks my other questions in your maintained thread.Boot hang on Sony logo
Hello Sir
I have a question after update TWRP . I could following steps to install TWRP on my XZ2
Fastboot devices (check device ready)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (flash file without secure check)
fastboot flash boot twrp.img (flash boot img to phone)
fastboot boot twrp.img (boot to twrp)
Install recovery ramdisk twrp.img (install)
I think above all steps are right ? if so , I would want to flash lineage-17.1 or PIXEL EXPERIENCE ROM via TWRP install mode
But after I install it finish , I would stuck SONY logo (if use lineage-17.1 would present my system data is broken)
Could you do me a favor that help me to check which steps is not correct ?
Hello Sir
I have a question after update TWRP . I could following steps to install TWRP on my XZ2
Fastboot devices (check device ready)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (flash file without secure check)
fastboot flash boot twrp.img (flash boot img to phone)
fastboot boot twrp.img (boot to twrp)
Install recovery ramdisk twrp.img (install)
I think above all steps are right ? if so , I would want to flash lineage-17.1 or PIXEL EXPERIENCE ROM via TWRP install mode
But after I install it finish , I would stuck SONY logo (if use lineage-17.1 would present my system data is broken)
Could you do me a favor that help me to check which steps is not correct ?
I swiped the dust out of my xz2 and decided to start tinker with it again. I installed the latest firmware but when i flash vbmeta i get in to bootloop :/ I can start the recovery but after that nothing. I then have to restore the phone using emma and everything is fine with the phone. I just want to figure out what I am doing wrong.
This TWRP is End Of Life
Please use the working one in the TWRP 10 thread for Android 10 & 11
Please use the working one in the TWRP 10 thread for Android 10 & 11
Greetings. This is amazing work.
There's a little problem I can't wrap my head around.
(XZ2c H8314, Android 8, bootloader unlocked on Android 10)
- Bootloop occurs if I input command:
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
- Omitting it & following the rest of instructions works
- Upon first firmware boot, all's good except the camera preview (DRM keys missing)?
- XperiFix executes, however, the camera preview issues etc. remain
- (Is XperiFix not working bc. of lacking vbmeta command?)
Tried Flashing:
- permissive.zip (SELinux switch)
- [Pie]Camera_fix_by_MartinX3 & [Pie][Magisk]Camera_fix_by_Serajr
- Different Magisk versions (17.1, 18.1, 19.3)
- no-verity-opt-encrypt-6.1.zip (desperate attempt)
Device's a replacement for the broken same-model phone. It all worked there (hardware issues emerged).
Staying on Android 8/w full functionality would be a dream.
There's a little problem I can't wrap my head around.
(XZ2c H8314, Android 8, bootloader unlocked on Android 10)
- Bootloop occurs if I input command:
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
- Omitting it & following the rest of instructions works
- Upon first firmware boot, all's good except the camera preview (DRM keys missing)?
- XperiFix executes, however, the camera preview issues etc. remain
- (Is XperiFix not working bc. of lacking vbmeta command?)
Tried Flashing:
- permissive.zip (SELinux switch)
- [Pie]Camera_fix_by_MartinX3 & [Pie][Magisk]Camera_fix_by_Serajr
- Different Magisk versions (17.1, 18.1, 19.3)
- no-verity-opt-encrypt-6.1.zip (desperate attempt)
Device's a replacement for the broken same-model phone. It all worked there (hardware issues emerged).
Staying on Android 8/w full functionality would be a dream.
This TWRP is End Of Life
Please use the working one in the TWRP 10 thread for Android 10 & 11
Please use the working one in the TWRP 10 thread for Android 10 & 11
Similar threads
- Poll
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
50The 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:
- If your stock camera preview is black, please follow this issue ticket.
https://github.com/sonyxperiadev/bug_tracker/issues/261
https://github.com/MartinX3-AndroidDevelopment/bug_tracker/issues/7 - 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:-
shows you the reason.Code:
cat /dev/block/bootdevice/by-name/misc - Please replace it with an empty string.
-
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.
Bugtracker:
- TWRP Bugtracker -> If you think the problem is in TWRP
- My Bugtracker -> If you think the problem is in my implementation
Bugreport:
- A bugreport needs your device name, dmesg, the /tmp/recovery.log and a way to reproduce the issue.
- If the TWRP is stuck at the TWRP logo, the chances are high, that the decryption didn't succeed.
- The TWRP should be still usable if you just "fastboot boot twrp.img" it.
- 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
- @M-ROM for his hint activating the touch in TWRP
- @osm0sis
- @nreuge
- @FartyParty
- @pandemic
- @nasko_spasko
- @VeixES
- @Klaus N.
- @old.splatterhand
- @yanke928
- @michele2
- @niaboc79
- @j4nn for hacking the kernel to make "fastboot boot twrp.img" possible
- @shoey63 for testing @j4nn 's hack
- @oshmoun for a better "fastboot boot twrp.img" solution
- @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, oshmoun, Marijn, Sony
Source Code: https://github.com/MartinX3-AndroidDevelopment
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Matching to firmware in twrp name
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-08-10
Created 2018-07-26
Last Updated 2020-10-2312Download & Installation
Download:
- https://androidfilehost.com/?w=devices&uid=11410963190603893035
- https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
- Unzip the *.gz files with https://7-zip.org/ or Linux.
Installation Android 9.0:
- Update to newest stock firmware before unlocking!!!
- Enter fastboot via software, not hardware buttons. See "Known Bugs".
- (Optional; If you modify the system or need the camerafix.zip)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img - fastboot boot twrp.img
- Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
- Reboot into installed TWRP
- Want Root? -> Magisk
- (Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)
In case of touch issues on the XZ2 compact:
- Download (try the v10 zip first, if it doesn't work try v9 or v8)
- Do the same steps, but with the TWRP test release.
Installation Android 8.0:
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta-xz2(?).img
- fastboot flash boot twrp.img
- Install stockkernel-xz2(?)-installer.zip
- Install twrp-3.2.3-0-xz2-xz2c-xz2p-installer-xz?-installer.zip
- Install Magisk-v17.1.zip
- (Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)
12@MartinX3 @sToRm// @modpunk
I got drmfix working on enforcing selinux!
How-to:
After reboot into system (post #3 - First time installation of TWRP & after newflasher installation), open a shell window and type:
Enjoy it!Code:su mount -orw,remount /vendor magiskpolicy --load /vendor/etc/selinux/precompiled_sepolicy --save /vendor/etc/selinux/precompiled_sepolicy "allow init domain process { noatsecure }" "allow init secd process { noatsecure }" mount -oro,remount /vendor
(you may now add it in your scripts if you want to) - If your stock camera preview is black, please follow this issue ticket.
