FORUMS
Remove All Ads from XDA

 View Poll Results: Should I continue this project?

Yes, for the XZ2.
 
99 Vote(s)
43.61%
Yes, for the XZ2C.
 
93 Vote(s)
40.97%
Yes, for the XZ2P.
 
25 Vote(s)
11.01%
Yes, for the XZ3.
 
38 Vote(s)
16.74%
No.
 
1 Vote(s)
0.44%

[RECOVERY][Android 8 / 9][Stock/Custom ROM][XZ2/c/p, XZ3] TWRP 3.3.0-0 [UNofficial]

3,184 posts
Thanks Meter: 1,676
 
Post Reply Email Thread
Announcement from MartinX3: TWRP for XZ2, XZ2C, XZ2P, XZ3 on STOCK and Custom ROM's
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)


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.

https://img.xda-cdn.com/pjYW8YL3YwHOySMffrNg1Tk75kE=/https%3A%2F%2Ftwrp.me%2Fimages%2Fhome.png
https://img.xda-cdn.com/30NlQ1VRh0t9cCco-su_hiRDfsk=/https%3A%2F%2Ftwrp.me%2Fimages%2Fbackupname.png

Quote:
Originally Posted by Camera break since december PIE patch level

Status Update & WARNING:
If unlocked with .126 or later on PIE, you don't need these fixes!
https://github.com/sonyxperiadev/bug_tracker/issues/261
I uploaded the latest OREO (XZ2, XZ2C, XZ2P) for initial camera fix with XperiFix and the PIE (XZ2, XZ2C, XZ2P, XZ3) november firmware to upgrade after fixing the camera.

Known Bugs STOCK:
  • 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.
Known Bugs AOSP/Custom ROM's:
  • 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.

Hints:
  • 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!.

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
Shame on me if I forgot someone after searching through the thread and my PM's!

And many thanks to the few donators!

XDA:DevDB Information
TWRP, ROM for the Xperia XZ2

Contributors
MartinX3, oshmoun, Marijn, Sony
Source Code: https://github.com/MartinX3sAndroidDevelopment

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: Stable
Current Stable Version: 3.3.0-0
Stable Release Date: 2019-04-06
Current Beta Version: 3.2.3-0
Beta Release Date: 2018-10-10

Created 2018-07-26
Last Updated 2019-04-24
The Following 35 Users Say Thank You to MartinX3 For This Useful Post: [ View ] Gift MartinX3 Ad-Free
 
 
26th July 2018, 09:27 PM |#2  
MartinX3's Avatar
OP Recognized Contributor
Thanks Meter: 1,676
 
Donate to Me
More
24.04.2019
Quote:

reuploaded aosp/stock twrp.
Accidentially uploaded (build environment bug) the akari xz2 twrp for every device. It boots & installs magisk, but it can't mount the other partitions.
Sorry!

22.04.2019
Quote:

aosp twrp
hello "fastboot boot twrp.img"!
Bye bye twrp installer zip file! (see installation instructions.)
reduced the download size!

17.04.2019
Quote:

stock twrp
hello "fastboot boot twrp.img"!
Bye bye twrp installer zip file! (see installation instructions.)
reduced the download size!


09.04.2019
Quote:

stock twrp firmware 52.0.a.8.25 (april security patch level)
fixed touch problems some people have.
Twrp is now at version 3.3.0-0.

07.04.2019
06.04.2019
Quote:

reuploaded april security patch level aosp twrp with a newer kernel and more upstream merged changes from sony aosp.
I hope now the wifi problem is gone.
Twrp is now at version 3.3.0-0.

02.04.2019
Quote:

reuploaded april security patch level aosp twrp.
Reverted https://gerrit.omnirom.org/#/c/andro...overy/+/33783/
now zips are installable again without the "digest" error.
Omnirom still has the bug. Just install it on top of omnirom or replace its boot.img by the twrp.img.

02.04.2019
Quote:

aosp twrp released for aosp / custom roms with april 2019 security patchlevel.

01.04.2019
Quote:

aosp twrp released for aosp / custom roms with march 2019 security patchlevel.

May contain the stock twrp mtp bug.

A zip installer is not needed anymore.
Just flash the boot.img, the dtbo.img and the vbmeta.img with the parameters.

31.03.2019
Quote:

reuploading twrp.
Removed the old build, which stopped at twrp logo.
Now the mtp and touchscreen problems should mostly be fixed.

30.03.2019
Quote:

reuploading twrp.
Removed the old build.
Now the mtp and touchscreen problems should be fixed.

I tried to automate the upload with my new android file host access.
It is unstable.
Sadly android file host is the only hoster with unlimited quota.

25.03.2019
Quote:

stock twrp released for stock firmware 52.0.a.8.14.
Many new fixes and features and sadly a new bug:
Wait until the password entry appears, before you connect the phone with your computer or the touch won't work.

But i hope that the touch bug on the xz3 is now fixed.

14.03.2019
Quote:

dear people, sadly no new twrp for the new stock march firmware with shiny new twrp bugfixes and so on until i finished my next exam (of many) at the 20.03.2019.
But after that i'll release a new release.
Maybe with working "fastboot boot twrp.img"

i hope
https://gerrit.omnirom.org/#/c/andro...overy/+/33287/
will got merged then, too, so i can hopefully remove the twrp installer zip file.

Ps:
The good thing is, if you rely on the twrp and won't update the firmware before i release it, you can see others complaining about march firmware bugs without having them on your phone.

19.02.2019
Quote:

bundling now .202 touch drivers.
The difference to the first version is, that i don't try to get them from the vendor partition.
Instead i bundled them into my ramdisk file.
I hope the touch problems are now fixed for everyone, which i sadly can't reproduce.

17.02.2019
Quote:

since some users still get no working touch, i switched back from .202 touch drivers to .163 touch drivers.

16.02.2019
Quote:

hotfix for stock xz2 twrp. I introduced a bug with the last update.

16.02.2019
Quote:

hopefully fixed touch bugs some where having (even with the exact same hardware/firmware combination like me)

13.02.2019
Quote:

twrp firmware 2019 february 52.0.a.3.202
including a camera fix, which is compatible with the latest twrp release. (fixes only the black preview)
reduced the twrp download size by around 6mb. If the touch doesn't work, pelase report it asap.

10.02.2019
Quote:

in combination with my sonyaosp _r31 release i uploaded the twrp for custom rom's / aosp (february patch level)
it is importand to use the same twrp security patch level as the rom or avb 2.0 will lead into bootloops in twrp and the system.

08.02.2019
Quote:

i found the broken twrp solution together with the sony developers.

It's the cause of the omni 9.0.0_r31 ramdisk (february security level)
i need to wait for the february security patch stock update.
The rollback security is preventing me to use an january kernel with the february firmware, resulting in a blinking bootlooping black/logo/black/logo twrp animation.
Will release the next working twrp with twrp camerafix & magisk camerafix included and maybe my touch driver approch will work then, ( now i know it should work, it was only the cause of this security behaviour)

07.02.2019
Quote:

i̶n̶c̶l̶u̶d̶i̶n̶g̶ ̶a̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶c̶a̶m̶e̶r̶a̶ ̶f̶i̶x̶ ̶c̶o̶m̶p̶a̶t̶i̶b̶l̶e̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶l̶a̶t̶e̶s̶t̶ ̶t̶w̶r̶p̶ ̶u̶p̶d̶a̶t̶e̶.̶ ̶(̶o̶n̶l̶y̶ ̶f̶i̶x̶e̶s̶ ̶b̶l̶a̶c̶k̶ ̶c̶a̶m̶e̶r̶a̶ ̶p̶r̶e̶v̶i̶e̶w̶.̶)̶

06.02.2019
Quote:

r̶e̶d̶u̶c̶e̶d̶ ̶t̶h̶e̶ ̶t̶w̶r̶p̶ ̶d̶o̶w̶n̶l̶o̶a̶d̶ ̶s̶i̶z̶e̶ ̶b̶y̶ ̶a̶r̶o̶u̶n̶d̶ ̶6̶m̶b̶.̶ ̶i̶f̶ ̶t̶h̶e̶ ̶t̶o̶u̶c̶h̶ ̶d̶o̶e̶s̶n̶'̶t̶ ̶w̶o̶r̶k̶,̶ ̶p̶l̶e̶a̶s̶e̶ ̶p̶r̶o̶v̶i̶d̶e̶ ̶m̶e̶ ̶t̶h̶e̶ ̶i̶n̶f̶o̶r̶m̶a̶t̶i̶o̶n̶s̶ ̶l̶i̶n̶k̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶f̶a̶q̶.̶

03.02.2019
Quote:

a mysterious bugfix for the stock twrp appeared. It is super effective for stock decryption.

01.02.2019
Quote:

added the aosp/customrom support. I tested it on my xz2 with omnirom, aosp and resurrection remix.

19.01.2019
Quote:

updated to stock firmware 52.0.a.3.163 (jan 2019)

19.01.2019
Quote:

created buildenvironment for twrp.
Twrp is now based on tama omnirom builds.
That means we now get the latest twrp code commits.
This are the twrp code changes:
https://github.com/omnirom/android_b...0&type=commits

15.01.2019
Quote:

hopefully activated the xz3 twrp touch.

10.12.2018
Quote:

twrp android 9.0 pie december update.
Synced my stuff with the 52.0.a.3.126 stock firmware (drivers, kernel, etc.).
Added the xz3.
uploaded the last pie firmware with a working camera on unlocked devices.

16.11.2018
Quote:

the xz2p has a different kernel.
I fixed the xz2p twrp by splitting it in its own twrp boot.img file.

16.11.2018
Quote:

twrp android 9.0 pie november update.
Synced my stuff with the 52.0.a.3.84 stock firmware (drivers, kernel, etc.)

13.10.2018
Quote:

android 9.0 pie update.
Cleaned unused stuff.
Fixed mtp.
Only for xz2 and xz2c as universal installer.
Encryption still not supported, but my device config files are now usable to compile your own twrp.
Of course, the configsettings still are not fully optimal for this device.

13.10.2018
Quote:

android 9.0 pie twrp for xz2 and xz2c got released!
Xz2p will follow, after it gets the same update.
Mtp is still deactivated.
Encrpytion of the userdata doesn't work (password always wrong), because of the new android 9.0 pie encryption.
I think the next release will fix this.
Btw. In the first post is now a know bugs section.
And thanks to @m-rom, @michele2 and @niaboc79, who tried to helped me in this emergency situtation that pie got released and needed a new twrp while i was at work.

11.10.2018
Quote:

i seperated the twrp builds again, because of touch bugs in the xz2c.
The xz2, xz2c and the xz2p got seperated twrp.img files and stock kernel installer for twrp.

10.10.2018
Quote:

i seperated the xz2_xz2c build from the xz2_premium build.
It seems that i made a mistake.
The xz2 and xz2c are sharing the same kernel, but the xz2premium kernel has little differents.
I also optimized the folder structure behind the downloadlink.

10.10.2018
Quote:

working together with @storm// to achieve a working xperifix drmfix.
After we got success, i will highly recommend removing the old drmfix and installing his one.
The old one may brick the device forever during a longer time period. (2 weeks or longer)

old drmfix uninstall routine:
Flash with newflasher (v13+) only the file:
Vendor_x-flash-all-b6b5.sin

but remember to flash both slots.
Not only a or b.


twrp is your friend.
Or
fastboot set_active other

10.10.2018
Quote:

i am happy to announce the twrp for the xz2, xz2c and xz2p!
I need test results for the xz2c and the xz2p which i don't own.
Installation instructions got updated.
The last file got uploaded a few minutes ago.

08.10.2018
Quote:

fixed sdcard
in the 2018-10-08_01:36+2:00 folder.

Code:
1 fastboot format userdata
2. Fastboot flash twrp-xz2-2c-fixed-fstab-fixed-security.img
3. Reboot into recovery
4. Twrp flash stock kernel xz2_51boot.zip
5. Twrp flash twrp-installer-xz2-2c-3.2.3.zip
6. Install drmfix by storm// or m-rom
7. Twrp flash magisk-v17.1.zip
8. Twrp flash permissive.zip
9. Reboot into system

06.10.2018
Quote:

new try, thanks to everyone who helps me, tests for me and are a part of this nice little project.
in the 2018-10-06_14:53+2:00 folder.

Code:
1. Clean flash
or
1.1 fastboot format cache
1.2 fastboot format userdata

2. Fastboot flash twrp-xz2-2c-fixed-fstab-fixed-security.img
3. Fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4. Reboot into recovery
5. Twrp flash stock kernel xz2_51boot.zip
6. Twrp flash twrp-installer-xz2-2c-3.2.3.zip
7. Install drmfix by storm// or m-rom
8. Twrp flash magisk-v17.1.zip
9. Twrp flash permissive.zip
10. Reboot into system

05.10.2018
Quote:

new try, thanks to everyone who helps me, tests for me and are a part of this nice little project.
in the 2018-10-05_16:10+2:00 folder.

Code:
1. Clean flash
2. Fastboot flash twrp-xz2-2c-fixed-fstab-fixed-security.img
3. Fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4. Reboot into recovery
5. Install drmfix by storm
6. Twrp flash stock kernel xz2_51boot.zip
7. Twrp flash twrp-installer-xz2-2c-3.2.3.zip
8. Twrp flash magisk-v17.1.zip
9. Twrp flash permissive.zip
10. Reboot into system

05.10.2018
Quote:

modified the twrp recovery hack by @m-rom again.
Now i fixed the security settings for adb.
Twrp-xz2-2c-fixed-fstab-fixed-security.img
in the 2018-10-05_10:22+2:00 folder.

04.10.2018
Quote:

modified the twrp recovery hack by @m-rom again.
Now unpacked and repacked by android image kitchen.
Twrp-xz2-2c-fixed-fstab.img
in the 2018-10-04_21:00+2:00 folder.
I exchanged the twrp.fstab and the recovery.fstab. I hope this fixed the shell problem.

04.10.2018
Quote:

modified the twrp recovery hack by @m-rom.
Twrp-xz2-2c.img
in the 2018-10-04_11:30+2:00 folder.
I exchanged the twrp.fstab and the recovery.fstab. I hope this fixed the shell problem.

02.10.2018
Quote:

a new build.
Twrp__more_oem_drivers__oem_firmware__omni_8.1__ao sp_8.1_kernel__oem_8.1_libs.img
in the 2018-09-27_22:20+2:00 folder.
I added the entire firmware, bin, and radio folder and some more lib64 drivers from the aosp oem 8.1.6.3_r1_v15 binaries, so we can test, if the touch works now.

28.09.2018
Quote:

a new build.
Twrp__more_oem_drivers__omni_8.1__aosp_8.1_kernel_ _oem_8.1_libs.img
in the 2018-09-27_22:20+2:00 folder.
I added every lib64 driver, so we can test, if the touch works now.

27.09.2018
Quote:

a new build.
Twrp__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img
i tweaked some configs.
Switched back to oem 8.1 v15 drivers.
I did not upgrade the kernel, because the current code could damage the display.
Kernel bugs are listed in my aosp rom thread.

20.09.2018
Quote:

new builds.
Feel free to test.

boot__omni_8.0__stock_8.0_kernel__stock_51.1.a.11. 51_libs.img.gz
boot__omni_8.0__aosp_8.1_kernel__stock_51.1.a.11.5 1_libs.img.gz
twrp__omni_8.0__aosp_8.1_kernel__stock_51.1.a.11.5 1_libs.img.gz

boot__omni_8.1__stock_8.0_kernel__stock_51.1.a.11. 51_libs.img.gz
boot__omni_8.1__aosp_8.1_kernel__stock_51.1.a.11.5 1_libs.img.gz
twrp__omni_8.1__aosp_8.1_kernel__stock_51.1.a.11.5 1_libs.img.gz


boot__omni_8.0__stock_8.0_kernel__oem_8.1_libs.img .gz
boot__omni_8.0__aosp_8.1_kernel__oem_8.1_libs.img. gz
twrp__omni_8.0__aosp_8.1_kernel__oem_8.1_libs.img. gz

boot__omni_8.1__stock_8.0_kernel__oem_8.1_libs.img .gz
boot__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img. gz
twrp__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img. gz


boot__omni_8.0__stock_8.0_kernel__oem_9.0_libs.img .gz
boot__omni_8.0__aosp_8.1_kernel__oem_9.0_libs.img. gz
twrp__omni_8.0__aosp_8.1_kernel__oem_9.0_libs.img. gz

boot__omni_8.1__stock_8.0_kernel__oem_9.0_libs.img .gz
boot__omni_8.1__aosp_8.1_kernel__oem_9.0_libs.img. gz
twrp__omni_8.1__aosp_8.1_kernel__oem_9.0_libs.img. gz

18.09.2018
Quote:

a new build.
Twrp_8.0_oldconfig.img.gz
twrp_8.0_newconfig.img.gz
now i used the source code of the stock kernel to create a prebuild kernel image.
And i updated the device config.
And it looks like, that i can't put the stock source into the kernel folder of omni build environment.
It stops with the error, that it can't find a rule to make the zimage.
It is much more easier to build the aosp kernel, than the stock kernel.

17.09.2018
Quote:

i downloaded the 51.1.a.11.51 firmware and extracted all the needed stuff, including the new kernel to update the twrp device sources. Hehe.
One is got built with omni 8.0 and the other one with omni 8.1.
Feel free to test them.

16.09.2018
Quote:

split the aosp rom part into its own project.
https://forum.xda-developers.com/xpe...h8266-t3843269

15.09.2018
Quote:

i uploaded the aosp rom.
Feel free to test it.
Its kernel will be the one with my twrp build.
So i need to know if the kernel work or has bugs and broken functions.
If the kernel and the aosp image is fine, i will update the twrp build.

14.09.2018
Quote:

the bootloader v60 got released with the september patch.
i will now build aosp with the latest sources and if it will boot and work, i will use its kernel and the updated device sources to build twrp.

27.08.2018
Quote:

don't use this twrp builds.
We need to wait for the bootloader update from sony.
The device will be announced as part of the sony open devices project at the same time and the following issue will be closed:
https://github.com/sonyxperiadev/bug_tracker/issues/149.
The leading developer jerpelea told us, that it would be released with the september stock update.

18.08.2018
Quote:

i compiled the xperia aosp 8.1 image for the xz2 (h8266).
Feel free to test it.
I don't know, if we need the bootloader patch to run it.
Please follow the installing instructions in the third post.
https://drive.google.com/open?id=1-p...jpkvcltuwlgnri

04.08.2018 #3
Quote:

i compiled the sony 51.1.a.4.265 stock kernel.
I compiled the normal bootimage with the sony stock kernel and the sony aosp build sources, to test if it is bootable.
I did the same with the omni 8.0 sources and the sony stock kernel.
I uploaded them with the file ending "-with-stockkernel.img"

i don't know, if the stock kernel is compatible with the sony aosp or the omni sources.

04.08.2018 #2
Quote:

i compiled the normal bootimage with the sony aosp kernel and the sony aosp build sources, to test if it is bootable.
sony-aosp-8.1-04-08-2018-bootimage.img

04.08.2018
Quote:

i recompiled the sony aosp 4.9 after its change to 'beta'.
I recompiled omni 8.0 twrp bootimage and recoveryimage with it.
Please test it and provide a feedback.

Ps: Omni 8.0 because since the last 'repo sync' i am not able to compile 8.1 anymore because of missing framework lib dependencies.

01.08.2018
Quote:

i was able to compile the standard recovery with the sony 4.9 aosp kernel for the xz2.
I also compiled a bootimage and a recoveryimage with twrp with the sony 4.9 kernel and the omni sources.
Please test it and provide a feedback.

30.07.2018
Quote:

the build is not working.
It seems, that we need to wait for sony to stable their asop kernel on github (e.g. To announce, that the xz2 is now a part of the open source project.)

The Following 8 Users Say Thank You to MartinX3 For This Useful Post: [ View ] Gift MartinX3 Ad-Free
26th July 2018, 09:27 PM |#3  
MartinX3's Avatar
OP Recognized Contributor
Thanks Meter: 1,676
 
Donate to Me
More
Bug & feature tracker
https://github.com/MartinX3sAndroidD...nt/bug_tracker

Please keep in mind, that there may still be issues or missing features:
Open Issues

How to enter flash, fastboot and recovery mode:
https://developer.sony.com/develop/o...-combinations/

How to use fastboot and adb:
https://wiki.lineageos.org/adb_fastboot_guide.html

Download:
https://androidfilehost.com/?w=devic...63190603893035
Unzip the *.gz files with 7-zip or Linux.
Please use only the TWRP version which match your Android version (8.0/9.0).
And take a look into the "Universal" folder, too.

Installation Hint:
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.

Installation of TWRP
  1. [FASTBOOT] fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img <- IMPORTANT OR THE SYSTEM WON'T BOOT!
  2. [FASTBOOT] fastboot boot twrp.img (Enter fastboot via adb, twrp, system, NOT via hardware buttons!)
  3. [TWRP] Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
  4. Reboot into installed TWRP
  5. [TWRP] flash Magisk <- IMPORTANT OR THE SYSTEM WON'T BOOT!
  6. Reboot into SYSTEM
  7. (Optional) Switch SELinux to permissive <- Only if you really need it!
    1. Reboot into installed TWRP
    2. [TWRP] flash permissive.zip
    3. Reboot into SYSTEM
  8. Install the official Magisk App to gain root.
Stock Firmware additions
  • DRMfix (Only OREO at the moment) or my included camera fix (only if your camera preview is black) which uses some files with security patchlevel november 2018[/URL] (Both optional)

Usefull Tools:
FAQ:
Weird problems not easily to reproduce by other users:
Reflash the device with XPERIFIRM & NEWFLASHER.
Use the LASTEST plattform tools (fastboot & adb).

Not Working Touch:
I need the following information from you:

Device: XZ2 or XZ2C or XZ2P

The Terminal Output of
Code:
cat /sys/devices/dsi_panel_driver/panel_id
Code:
ls -lha /vendor/lib/modules/
In TWRP and the android system
(You can use
Code:
adb shell
or your terminal. In both cases you need to get root with the command
Code:
su
first. And you need Magisk Root)

Touchpadhardware ("dial it"):
Code:
*#*#SERVICE#*#*
Information Pattern:
Code:
Device: ""
Output TWRP img file: ""
Output TWRP Installer Zip: ""
Output Android System: ""
Hardware: ""
The Following 7 Users Say Thank You to MartinX3 For This Useful Post: [ View ] Gift MartinX3 Ad-Free
27th July 2018, 05:31 PM |#4  
mitpio's Avatar
Member
Flag Łódź
Thanks Meter: 11
 
More
Unfortunately, trying to run but the command does not enter you can write exactly step by step how to do it
27th July 2018, 08:49 PM |#5  
MartinX3's Avatar
OP Recognized Contributor
Thanks Meter: 1,676
 
Donate to Me
More
Quote:
Originally Posted by mitpio

Unfortunately, trying to run but the command does not enter you can write exactly step by step how to do it

Could you tell me, which error message you get?
Or does nothing happen?

Did you unlock your bootloader?

Do the command

"fastboot devices"

(Without "")

Will it ahow your device with a number?

_______________________________________

Or if you need to get into the Fastboot Mode

Connect your device to your PC and write

"adb devices"

This should show you your device and a number.

Then you can do

adb reboot bootloader

And choose the fastboot mode.
28th July 2018, 08:37 AM |#6  
paulle's Avatar
Senior Member
Thanks Meter: 274
 
More
entering fastboot mode xperia xz2
Quote:
Originally Posted by mitpio

Unfortunately, trying to run but the command does not enter you can write exactly step by step how to do it

Switch off the phone. Press and hold the Volume Up button
Connect to your PC using a USB Cable while holding down the Volume Up button on your Xperia XZ2
Before plugging in the USB cable on your Xperia XZ2 make sure that the other end of USB cable is already connected to the PC.
Wait till the LED turns into blue (the volume up button has to be pressed all the time till you see the blue led). Blue LED -> no more need to press the volume up button. Now you are in fastboot mode.

Using Linux do the following: open a terminal, type 'sudo fastboot devices' (without the quotes) (make sure before that you have fastboot installed on your linux box).
The output should be something like: QV7016A31E fastboot

The procedure should be very similar using windows (without using the sudo command), but I never tried it.
The Following User Says Thank You to paulle For This Useful Post: [ View ] Gift paulle Ad-Free
28th July 2018, 09:32 AM |#7  
mitpio's Avatar
Member
Flag Łódź
Thanks Meter: 11
 
More
Ok, thanks, I'll try

Wysłane z mojego H8266 przy użyciu Tapatalka
28th July 2018, 12:05 PM |#8  
paulle's Avatar
Senior Member
Thanks Meter: 274
 
More
Quote:
Originally Posted by mitpio

Ok, thanks, I'll try

Wysłane z mojego H8266 przy użyciu Tapatalka

Are you using linux or windows?
28th July 2018, 12:35 PM |#9  
mitpio's Avatar
Member
Flag Łódź
Thanks Meter: 11
 
More
windows
28th July 2018, 01:36 PM |#10  
paulle's Avatar
Senior Member
Thanks Meter: 274
 
More
Quote:
Originally Posted by mitpio

windows

https://lifehacker.com/google-finall...-st-1790840830
https://www.desinerd.co.in/how-to-ad...ows-mac-linux/
https://thedroidarena.com/best-adb-f...-list-android/
https://wiki.lineageos.org/adb_fastboot_guide.html
The Following User Says Thank You to paulle For This Useful Post: [ View ] Gift paulle Ad-Free
28th July 2018, 03:44 PM |#11  
Member
Thanks Meter: 52
 
More
Unfortunately this build seems not working, it did something out of an ordinary boot though.

Here's what exactly what I did:
1. The phone is unlocked, model H8266.
2. Shut down and get into fastboot mode, with blue LED on.
3."fastboot boot xz2_twrp.img" and get it booting.

and this is what I observed:
1. Screen turns on with Blue LED on, diaplaying "Your device software cannot... Blablablah".
2. After 5 seconds the screen turns off, but the blue LED is still on.
3. After around 20 seconds the screen turns on again with "SONY" logo, blue LED is still on.
4.About 5 seconds later, Blue LED turns off.
5.Again about 10 seconds later, screen turns off.
6.The red LED blinked a few times, with two times of vibration.
7.Screen turns on with "SONY" logo, then it's totally an ordinary boot into Android.

Hope the feedback will help.
The Following 2 Users Say Thank You to yanke928 For This Useful Post: [ View ] Gift yanke928 Ad-Free
Post Reply Subscribe to Thread

Tags
akari, akatsuki, apollo, aurora, twrp

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes