yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
So your bootloader is upgraded (v52)

Now the only way entering recovery is the process I describe earlier.

Flash a new one with the process I answer you.

Seems only your kernel is wrong for now.

Good luck!
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
How can I reflash the kernel? I'm on ZyxxOS v1.2. On the zip there isn't a recovery.img or boot.img.. There are only boot.sin and partition-image.sin. I can't enter into recovery, I flashed the twrp 3.0 for new bootloader but I can't enter. There's not light or vibration when I press power button.

I read on a threat that the kernel manages the energy and the way the device charges and I think andropluskernel broke that part of my device. I connect and OTG and my Z3 doesn't recognize it.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
You are right, kernel does the offline charge an the usb connectivity.

I'm looking about sin files.

To enter recovery (with new bl) turn off your phone, wait a few seconds, then press volume down and power at the same time until the sony logo appears.

---------- Post added at 20:00 ---------- Previous post was at 19:52 ----------

Is your phone a d6603 or a d6633?
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I can't enter into recovery, there's not a vibration or light, I have tried too many times to enter using that combination of bottoms.

My device is D6653. I was looking into the ZIP file of the ZyxxOS ROM which is 6.0 and there's a zip that is called CORE.ZIP and extracted that zip called CORE and there's a file with the name boot.img.

I have sent a message to the developer of ZyxxOS ROM in order to get more information to try to identify the problem... I invited him to look at my threat
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
I test sin2raw and with flashtool: no luck.

After reading this I truncate the boot.sin file provided by this zyxxos v1.2 it is in attachement in a dirty way. I can not guarantee it will work! As the kernel is the first thing started on your phone a wrong flash could result in a really bad soft brick.

The boot.img provided in the core.zip seems to be the 'dual-recovery' provided by the rom.

I thing you can restart with a fresh install with emma if something goes really wrong.

Good luck.

(or try another kernel specially build for your phone/rom)
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
The problem is not restart with a fresh install, the problem is that I can't use any program on PCs because my device is recognized as an USB unknown malfunctioned device.

I think I have to solve first the problem with the kernel (boot.img???) in order to make work the USB part of my phone, it could be by having recovery I think, reinstalling the rom with all the wipes in order to clean the system.

EDITED:

Can you check this zip? It's the XZDR remove package to make work AndroPlusKernel

https://www.androidfilehost.com/?fid=24269982086991761

I flashed that file before flashing andropluskernel but I had recovery. I lost the recovery when I flashed ZyxxOS ROM
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Even in download mode? So the computer should be the problem ;)

As I know download mode is unbreakable. I format all my partitions (d6603): fotakernel, boot, system and reflash from download.

Yes the kernel is the boot.img (go to the boot partition) and the recoveries goes to the fotakernel partitions.
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I tried another computer and it is recognized as USB unknown device, I installed the drives and nothing happened.

I have used my PC too many times to use flashtool and I could use it perfectly. After flashing these zips, my pc doesn't recognize my z3, for that reason I think it's something relative to the kernel and the way it manages connections through the USB port
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
You are right, the kernel manage the usb connection, but only when this kernel is started (system booted or off mode charging).

You test different cables, another computer and no fastboot, no download!?

I can't understand.

What I believe to know:

When you start in fastboot, the bootloader (aboot partition) manage your usb and when you start in download mode another part of the phone (don't know which one) manage the usb.

So, I think, the only way you have, in all of these boot mode, a 'bad device' is a hardware problem: broken usb port on the phone or maybe the integrated usb controller...
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I have tried different USB cables and PCs and nothing happened. The thing is that the problem happened after flashing andropluskernel, before that my PC recognized my Z3 and my Z3 used to charge perfectly with the charger. I don't understand, I'll wait for the developers answers in order to know a little more.

Thank you friend, I really appreciate your effort to help me! I'm getting crazy with this! :crying:

I would like at least make the recovery work
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
I found this:

On my computer:

nailyk@lamatsu :) % lsusb
Bus 006 Device 006: ID 0fce:51ba Sony Ericsson Mobile Communications AB

then on the phone:

root@z3:/ # cat /sys/devices/virtual/android_usb/android0/idProduct
51ba
root@z3:/ # cat /sys/devices/virtual/android_usb/android0/idVendor
0fce

and my usb is enabled:

root@z3:/ # cat /sys/devices/virtual/android_usb/android0/enable
1

Can you check on your phone please?

Also:

127|root@z3:/ # dmesg | grep usb
<6>[ 1.429210] usbcore: registered new interface driver usb-storage
<6>[ 1.429239] usbcore: registered new interface driver usb_ehset_test
<6>[ 1.430480] gadget: android_usb ready
<6>[ 1.430910] usbcore: registered new interface driver xpad
<6>[ 1.430934] usbcore: registered new interface driver usb_acecad
<6>[ 1.430958] usbcore: registered new interface driver aiptek
<6>[ 1.430989] usbcore: registered new interface driver gtco
<6>[ 1.431014] usbcore: registered new interface driver hanwang
<6>[ 1.431039] usbcore: registered new interface driver kbtab
<6>[ 1.431062] usbcore: registered new interface driver wacom
<6>[ 2.426336] usbcore: registered new interface driver usbhid
<6>[ 2.426341] usbhid: USB HID core driver
<6>[ 2.427194] usb_bam_ipa_create_resources: Failed to create USB_PROD resource
<6>[ 2.428933] usbcore: registered new interface driver snd-usb-audio
<6>[ 2.471332] qpnp_charger_probe: success chg_dis = 0, bpd = 1, usb = 0, dc = 0 batt_present = 1 b_health= 1
<3>[ 3.805914] enable_store: android_usb: already disabled
<6>[ 3.852097] qpnp_chg_rb_work: stopping worker usb/dc disconnected
<6>[ 1300.274689] android_usb gadget: high-speed config #1: fe8050c8.android_usb

We see the usb drivers are loaded and (at 1300sec after booting) my usb was plugged-in and ok.

Maybe you can check this on your phone too?

---------- Post added at 22:30 ---------- Previous post was at 22:16 ----------

I test the boot.img on the core.zip and a twrp 2.8.7.0 is included. My cyanogen doesn't start on my d6603 but the twrp seems to be working.

The uname -a return:

3.4.0-perf-gc42d8a9-02192-g20ae1c7 #1 SMP PREEMP tue Oct 13 12:04:26 CEST 2015

Not sure that is the good one.
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
On my phone:

t /sys/devices/virtual/android_usb/android0/idProduct <
51dc
t /sys/devices/virtual/android_usb/android0/idVendor <
0fce

USB enabled:

t /sys/devices/virtual/android_usb/android0/enable <
1

On this part I think there is a problem...

# dmesg | grep usb:
u0_a245@leo:/ $ su
root@leo:/ # dmesg | grep usb
[ 1928.571892] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 1929.080038] qpnp_chg_rb_work: stopping worker usb/dc disconnected
root@leo:/ #

Edited:

I tried again the last part, I connected the phone to the computer

u0_a245@leo:/ $ su
root@leo:/ # dmesg | grep usb
[ 1928.571892] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 1929.080038] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2361.900773] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2414.187768] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2414.719516] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2419.700808] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
root@leo:/ #

Edited 2:

I tried with a different cable

u0_a245@leo:/ $ dmesg | grep usb
[ 2660.822263] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2662.760351] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2664.695660] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2666.630532] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2668.571292] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2670.518925] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2733.714283] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2733.829405] dwc3 f9200000.dwc3: gadget android_usb data soft-disconnect
[ 2734.189998] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2735.154361] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2735.421464] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2737.360361] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2748.249766] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2748.369898] dwc3 f9200000.dwc3: gadget android_usb data soft-disconnect
[ 2748.769762] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2750.402083] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2750.691646] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2752.634542] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2754.584895] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2756.530012] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2758.477175] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2760.414030] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2769.675397] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2769.789545] dwc3 f9200000.dwc3: gadget android_usb data soft-disconnect
[ 2770.219536] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2784.570479] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2785.341245] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
u0_a245@leo:/ $
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
With your error I found some kernel patch (in cyanogen tree).

Anyway it seems the usb_gadget is broken on this kernel. You can try combination of booting with/without adb enabled but I think it wont change anything.

Did you see my last post about core.zip/boot.img?

When I try the boot.img I provide a few post earlier my phone was frozen. As I don't like open the access cover of my phone so I use the 'volume-up + power' (with usb plugged-in) disaster-recovery and my phone reboot in download mode. Is it working for you?

Did you try turning your phone off completely by pushing the power off buton (near the sdcard) then entering download mode or other things? (turn off this way without usb cable, press volume up or down while plugin the cable)

---------- Post added at 22:52 ---------- Previous post was at 22:50 ----------

There is a real connectivity problem with this cable :)

But maybe the usb port of the phone is broken? Did you clean it up?

edit:

you kernel configuration is ok: vendorId/productId and usb enabled.
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I just tried those methods and my PC recognized it as USB not recognized".

The USB port problem could be, the thing is that I don't understand why this happened after flashing andropluskernel...

I see the post about boot.img but I'm so scared about flashing the boot and lost my phone if it doesn't boot :crying:

PD: My phone shows blue light when I press volume up when I connect the USB cable while it is off (fastboot mode) and it shows a red and green light when I press volume down but my PC doesn't recognize it

EDITED: I think my solution for now it's making the recovery works in order to try to change the rom with all the wipes
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
For now your phone is almost working so I understand.

It is really strange! The phone detect the usb connection well: blue light = fastboot and the 'red/green/off' = download.

Try to connect on a usb 2.0 port directly on the motherboard (not in the front panel), without usb hub, without extension cable (right word?)

Any chance you can plug this phone on a linux computer and get the dmesg output? (dmesg | tail -50)

Time to switch to cyanogenMod ;)

I reflect on it but as you can't boot with the new key combination your bootloader seems to be the old one. So the only way to get a recovery is a working kernel as I know...
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I connected to USB 2.0

u0_a245@leo:/ $ dmesg | grep usb
[ 2322.831931] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2323.359519] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2336.244450] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2383.710482] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2384.259534] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2385.188135] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2392.669067] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2393.209843] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2393.725163] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2414.634684] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2415.139530] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2416.047791] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2436.343992] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2436.859542] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2438.512870] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2458.806967] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2459.340378] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2460.763578] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
u0_a245@leo:/ $

I guess I don't have the new bootloader because when I flashed the ZyxxOS rom I used Phil recovery using volume up bottom after press power bottom and a purple light appear, (the light used to change to orange when I pressed volume up to enter into recovery)

EDITED: I lost the recovery after flashing ZyxxOS rom.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
your dmesg always show a connectivity problem (flapping link?)

The 'in kernel-recovery-boot-process' is exactly that you describe and was writen by Dees_Troy. The kernel (in the boot.img) boot up, wait 3 secs the volume press. If volume-rocker had been pressed the recovery ramdisk is used, otherwise, the regular ramdisk is used.

That's why a working kernel is really important with the old bootloader. Without this Dees_Troy trick there is no way to boot a recovery.

Actually I'm looking for:

- a way to start twrp on your running system and restore a backup you made earlier,

- install zyxxos on my phone and dump the boot.img then send to you but this is really heavy for my (encrypted cyanogen with f2fs so I need to factory reset 2 or 3 times....)
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I really appreciate your effort, I'm looking for a recovery image for the old bootloader, I mean, a recovery.img to flash it through the terminal commander, I tried the TWRP but that doesn't work.
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
No problem. This week I have I little time and I know this stress about almost broken phones :D

Sorry if I am not clear but I am not english natural speaker.

There is one universal way to boot recoveries (all phones, even iPhone):

bootloader

With the sony xperia, before the upgrade of the bootloader, the branch with the 'recovery "Y"' doesn't exist. So Dees_Troy write a splendid code (extract_elf_ramdisk) placed in the 'real kernel' (boot partition in this schema) which is a workaround to 'start' a recovery.

As your actual kernel doesn't provide this part of code you cannot start recovery.

For sony xperia Z series the _only_ way to boot in recovery is: new bootloader or extract_elf_ramdisk. Sorry.
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I'm losing the hope. Is there a way of installing the new bootloader? In order to install TWRP 3.0.0 through terminal emulator.

The kernel is the biggest problems... Omg
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Yes, reflashing all with emma..... :s
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
In the 'TA' partitions there is some information written by bootloader.

Try to start the phone in fastboot mode (with hard reset: volume-up+power when system is started), then

restart your system and report the result of:

strings /dev/block/platform/msm_sdcc.1/by-name/TA | tail -50

(hope you have busybox installed. If not send me a copy of your ta partition by PM)

With the new bootloader there is nothing interesting but on some backup made with the old one there is some information:

[ERROR @ S1/boot/src/s1boot_lib_api.c:1448]:
TA read failed!
[370] S1 decisions complete, image to boot is 0.
[380] IMEI[0]: 35163707277796
[380] Info: failed to retrieve secondary IMEI (optional) in facility 0x1 with code 0x2 (error ignored)
[1090] Using DTB entry 194/00010000/8/0 for device 194/00010001/8/0
[1100] CHG_STATUS_REG is 0x20 after pm8x41_chg_sts_get()
[1100] icon_flg is 0x0 battery_flg is 0x0 chg_presence_flg is 0x1
...
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I've attached the TA.bin
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
Yes, my bootloader is unlocked!
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
Did you find something useful with the informations in your ta partition?

A thread open recently : Sony Xperia Z3 D6616 possibly hard bricked?. You should have a look, there is a lot of good tips to try imho.
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I don't know what to do with the TA partition information because I don't know nothing about partitions. I read a little more the threat of ZyxxOS and that rom use Dualrecovery, so, I have to reflash the partition which have the recovery files.

I'll take a look of that threat and I'll try the tips that they gave
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
This idea was to find a lead about the non working fastboot or download mode. Just googling some errors could give you hints maybe?

Sure but it depends where you would like to go.

In my opinion, from what you answer and I check:

- you flash a rom which is not for your phone,

- this rom or a earlier you flash update your bootloader with a 'almost' incompatible one,

- the kernel you flash is not build for you phone model.

The result is your usb connectivity is broken in bootloader (fastboot mode) and system.

Now how do you get back your phone?

- you can flash 'in-place' new kernels, recovery, systems etc but it won't get back fastboot.

-- flashing in place is really risky because if something goes wrong you won't be able to boot anymore

- you can try to get your bootloader working again, then reflash a full system.

-- flashing a new bootloader is risky as the bootloader is the first started part of your phone (bootloader is sort of bios on your pc).

- send your phone to repair

-- as it is a software problem it could have a cost.

That is just what I understand but maybe I'm far away of what happens.

I hope my explanation are clear and should help you :)
[Xperia Z3 Q&A, Help & Troubleshooting] DarkAngel217:
Which version of the kernel did u flash I used that kernel before but did not really work properly for me
[Xperia Z3 Q&A, Help & Troubleshooting] nailyk:
remove fotakernel recovery

As the remove tool is a binary you could extract the zip file and run the 'update-binary' as root.

Otherwise, to remove the recovery in your FOTAKernel partition, basically, you could run something like this:

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel

This will fill the FOTAKernel with '0' resulting in a empty partition.

As usual be careful with the dd command, especially this time because you are writing to the emmc.
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I ran it and this was the result

u0_a245@leo:/ $ su
root@leo:/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-nero of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKer nel <
dd: /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel: No space left on device
32769+0 records in
32768+0 records out
16777216 bytes transferred in 1.982 secs (8464791 bytes/sec)
1|root@leo:/ #

I tried to enter into recovery but I couldn't... I think I had to tried to install the zip file which we have to flash in order to install dualrecovery.

I remember when I was on the beta rom of marshmallow (not the concept) we didn't have recovery and I tried to install the recovery with the computer through adb and it created a temporary recovery and after rebooting the recovery, the recovery disappear, I would like to tried at least having a temporary recovery but my pc doesn't recognize my device. I tried Flash Gordon app in order to try to flash on running system the zip of Dualrecovery but the app it's not compatible with marshmallow and another app called flashfire it's not compatible with the root provided by KingRoot.

Any idea to flash the zip of Dualrecovery?

Thank for your help
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I flashed the last version v72 permisive, in my case after flashing that kernel, I start having big problems.
[Xperia Z3 Q&A, Help & Troubleshooting] DarkAngel217:
yea that one i had troubles for me as well you might have to enter fastboot if u can then flash a recovery then reflash using that recovery the rom that will fix the problem as this rom u flashed has a kernel in it installation

can u access fastboot by putting the cord in and holding volume up button at the same time if u can like i said enter adb command prompt or install this http://xdaforums.com/showthread.php?t=2317790 and fastboot flash boot recoveryname.img

hope this works
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I can access to fastboot and flashmode but my pc recognizes my device as "unknown USB device (descriptor request failed)" and I don't have recovery to flash another rom... I have a kernel/boot problem.

I have to flash a rom or make the recovery works again
[Xperia Z3 Q&A, Help & Troubleshooting] DarkAngel217:
can u connect it in when it says unknown usb device go to device properties and if its there with error which it will go to the properties and see if theres an error code
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I've attached a screeshoot on the threat.

The code is 43.
[Xperia Z3 Q&A, Help & Troubleshooting] DarkAngel217:
Hmm I have searched the code and saying to reinstall it uninstall the driver reconnect the phone and see what happens
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
It's not relative to the drives, it's something relative to the system of the phone because it happened after installing andropluskernel. I have installed the drives of every device of Z series, I have tried with others cables and pcs...

Thanks friend
[Xperia Z3 Q&A, Help & Troubleshooting] DarkAngel217:
ok maybe we can do something in the phone using terminal like flashing a recovery (not sure if u actually tried) i can send u a recovery that works for me and i can find the terminal code and see if u can do it that way
[Xperia Z3 Q&A, Help & Troubleshooting] JuanMnz93:
I have tried to install a recovery in the fota partition but my rom uses dual recovery, this rom has inbuilt recovery on the boot.img (you can read the description of the rom on the threat of ZyxxOS rom v1.2) but I can try with your recovery, just send me the link and I'll try
[Xperia Z3 Q&A, Help & Troubleshooting] DarkAngel217:
http://d-h.st/5EA let me find the code for terminal

---------- Post added at 06:14 AM ---------- Previous post was at 06:13 AM ----------

su

flash_image recovery /sdcard/recovery_image_name