[Xperia Z2 General] _Leviathan:
Successfully flashed... I think

Hey there,

So I think I've figured out the flash. When I first downloaded Flashtool it failed. It took me a few attempted to get that working.

When it did I downloaded the kernal file, renamed it extention from .zip to .tft and continued with the flash. The log as below;

09/021/2016 13:21:19 - INFO - Device connected in flash mode

09/021/2016 13:21:37 - INFO - Selected Bundle for Sony Xperia Z2(D6503). FW release : 23.5.A.0.575. Customization : Customized MEA

09/021/2016 13:21:37 - INFO - Preparing files for flashing

09/021/2016 13:21:37 - INFO - Please connect your device into flashmode.

09/021/2016 13:21:38 - INFO - Opening device for R/W

09/021/2016 13:21:38 - INFO - Reading device information

09/021/2016 13:21:38 - INFO - Phone ready for flashmode operations.

09/021/2016 13:21:38 - INFO - Opening TA partition 2

09/021/2016 13:21:38 - INFO - Current device : D6503 - BH91KQD416 - 1281-2574_R9D - 1278-4770_23.5.A.1.291 - GLOBAL-LTE_23.5.A.1.291

09/021/2016 13:21:38 - INFO - Closing TA partition

09/021/2016 13:21:38 - INFO - Start Flashing

09/021/2016 13:21:38 - INFO - Processing loader.sin

09/021/2016 13:21:38 - INFO - Checking header

09/021/2016 13:21:38 - INFO - Flashing data

09/021/2016 13:21:39 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AB_LA3.0_M_3 / Bootloader status : ROOTABLE

09/021/2016 13:21:39 - INFO - Max packet size set to 512K

09/021/2016 13:21:39 - INFO - USB buffer size set to 512K

09/021/2016 13:21:45 - INFO - Found a template session. Using it : C:\Users\****\.flashTool\devices\D65XX\default.fsc

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - INFO - Writing TA unit 00002774. Value : 01

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - WARN - partition is excluded from bundle

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - WARN - dbi is excluded from bundle

09/021/2016 13:21:45 - WARN - emmc_appsboot is excluded from bundle

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - WARN - Unit 2127 not found in bundle

09/021/2016 13:21:45 - WARN - Unit 2301 not found in bundle

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - WARN - rpm is excluded from bundle

09/021/2016 13:21:45 - WARN - s1sbl is excluded from bundle

09/021/2016 13:21:45 - WARN - sbl1 is excluded from bundle

09/021/2016 13:21:45 - WARN - tz is excluded from bundle

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - WARN - cache is excluded from bundle

09/021/2016 13:21:45 - WARN - apps_log is excluded from bundle

09/021/2016 13:21:45 - WARN - kernel is excluded from bundle

09/021/2016 13:21:45 - WARN - fotakernel is excluded from bundle

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - WARN - userdata is excluded from bundle

09/021/2016 13:21:45 - WARN - system is excluded from bundle

09/021/2016 13:21:45 - WARN - amss_fs_1 is excluded from bundle

09/021/2016 13:21:45 - WARN - amss_fs_2 is excluded from bundle

09/021/2016 13:21:45 - WARN - amss_fsg is excluded from bundle

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - WARN - Unit 2212 not found in bundle

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - WARN - Unit 2404 not found in bundle

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:45 - WARN - elabel is excluded from bundle

09/021/2016 13:21:45 - INFO - Closing TA partition

09/021/2016 13:21:45 - INFO - Opening TA partition 2

09/021/2016 13:21:46 - INFO - Writing TA unit 00002725. Value : 32 30 31 36 2D 31 31 2D 30 39 20 31 33 3A 32 31 3A 34 36 00

09/021/2016 13:21:46 - INFO - Writing TA unit 00002774. Value : 00

09/021/2016 13:21:46 - INFO - Closing TA partition

09/021/2016 13:21:46 - INFO - Ending flash session

09/021/2016 13:21:46 - INFO - Flashing finished.

09/021/2016 13:21:46 - INFO - Please unplug and start your phone

09/021/2016 13:21:46 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings"

I can't quite tell if the flash succeeded or not from that log. I think so. in the about phone section it says it's still .291 but I read in this thread that is to be expected?

---------- Post added at 03:44 PM ---------- Previous post was at 03:29 PM ----------

After this I followed the other set of instructions and opened a CMD prompt as administrator, unzipped the recovery and then ran the install.bat as below;

"c:\a>install.bat

* daemon not running. starting it now on port 5037 *

error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:

Only one usage of each socket address (protocol/network address/port) is normall

y permitted. (10048)

could not read ok from ADB Server

* failed to start daemon *

error: cannot connect to daemon

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

Device Detected!

List of devices attached

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

BH91KQD416 unauthorized

Cleaning up for fresh install ...

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

error: unknown host service

Installing ...

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

error: unknown host service

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

error: unknown host service

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

[100%] /data/local/tmp/mm_twrp_recovery_install

adb server version (32) doesn't match this client (36); killing...

error: protocol fault (couldn't read status): Connection reset by peer

* daemon started successfully *

[100%] /data/local/tmp/mm_twrp_recovery_install

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

[100%] /data/local/tmp/mm_twrp_recovery_install

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

[100%] /data/local/tmp/mm_twrp_recovery_install

adb server version (32) doesn't match this client (36); killing...

error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:

Only one usage of each socket address (protocol/network address/port) is normall

y permitted. (10048)

could not read ok from ADB Server

* failed to start daemon *

adb: error: connect failed: cannot connect to daemon

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

[100%] /data/local/tmp/mm_twrp_recovery_install

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

[100%] /data/local/tmp/mm_twrp_recovery_install

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

[100%] /data/local/tmp/mm_twrp_recovery_install

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

[100%] /data/local/tmp/mm_twrp_recovery_install

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

error: unknown host service

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

error: unknown host service

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

error: unknown host service

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

error: unknown host service

adb server version (32) doesn't match this client (36); killing...

* daemon started successfully *

error: unknown host service

Finished!

Rebooting into TWRP recovery ...

adb server version (32) doesn't match this client (36); killing...

error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:

Only one usage of each socket address (protocol/network address/port) is normall

y permitted. (10048)

could not read ok from ADB Server

* failed to start daemon *

error: cannot connect to daemon

Press any key to continue . . ."

So this really doesn't look good. Just series of timeouts?

---------- Post added at 03:48 PM ---------- Previous post was at 03:44 PM ----------

Ah, School boy error. The Above is what you get if you still have Flashtool open. Below is what happens when you have to closed;

"c:\a>install.bat

* server not running *

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

Device Detected!

List of devices attached

BH91KQD416 device

Cleaning up for fresh install ...

Installing ...

[100%] /data/local/tmp/mm_twrp_recovery_install/boot_twrp_recovery.sh

[100%] /data/local/tmp/mm_twrp_recovery_install/busybox

[100%] /data/local/tmp/mm_twrp_recovery_install/byeselinux.ko

[100%] /data/local/tmp/mm_twrp_recovery_install/chargemon.sh

[100%] /data/local/tmp/mm_twrp_recovery_install/install_twrp_recovery.sh

[100%] /data/local/tmp/mm_twrp_recovery_install/iovyroot

[100%] /data/local/tmp/mm_twrp_recovery_install/modulecrcpatch

[100%] /data/local/tmp/mm_twrp_recovery_install/recovery.twrp.cpio.lzma

[100%] /data/local/tmp/mm_twrp_recovery_install/wp_mod.ko

iovyroot by zxz0O0

poc by idler1984

Error: Device not supported

Device name: D6503

Kernel version: Linux version 3.4.0-perf-gc14c2d5 (BuildUser@BuildHost) (gcc ver

sion 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Jun 28 11:15:

51 2016

Finished!

Rebooting into TWRP recovery ...

Press any key to continue . . ."

From here your phone restarts.

---------- Post added at 04:01 PM ---------- Previous post was at 03:48 PM ----------

Now in the above instructions there is this;

"twrp:

install the update-superSU*.zip"

What does this mean? How do you do it?

As far as I can see TWRP is a tool that requires root access on the phone, but the phone isn't rooted? So... have I missed something? Is the phone meant to be rooted by this point?

It sounds like the TWRP is used to install SuperSU?