Database Develop

[Q] Xperia V Possible Bricked HELLLPPPPP!

Hey people!i need help here!i have an xperia v with bootloader unlocked and last day i flashed an img kernel of cyanogenmod with flashify...all worked good until reboot...when i pressed reboot my phone didn't started anymore.when i try to power up nothing happens no leds no fastboot nothing!what can i do to fix it????please help

sash89 said:
Hey people!i need help here!i have an xperia v with bootloader unlocked and last day i flashed an img kernel of cyanogenmod with flashify...all worked good until reboot...when i pressed reboot my phone didn't started anymore.when i try to power up nothing happens no leds no fastboot nothing!what can i do to fix it????please help
Click to expand...
Click to collapse
Ooops.
Leave the phone off, connect it in fastboot mode (I know you said it did not work, but that might just be the LED, please try it again) and then run this
Code:
fastboot devices
and tell me what it says

Xperia v brick
gregbradley said:
Ooops.
Leave the phone off, connect it in fastboot mode (I know you said it did not work, but that might just be the LED, please try it again) and then run this
Code:
fastboot devices
and tell me what it says
Click to expand...
Click to collapse
no the phone doesnt connect in fastboot mode it shows no led nothing i only see in device manager that there is a
QHSUSB_DLOAD device wich i think is the processor...so what can i do man?and in device manager i see connected qualcomm hs-usb qdloader 9008 (com8)

did you try what I said?

hello greg, hows the z1, hope you enjoy it
thanks for your many many support to all questions here, hope it wasnt that frustrated when people not tried out what you suggested :silly:
to sash89: you unlocked bootloader, and flashed an cm img kernel? that let me comes to another question. you flashed that kernel above a stock rom, or you flashed CM ROM also?

Hi
The Z1 is great, I recommend it.
Yes, it does help if people try things you suggest.

brick
gregbradley said:
did you try what I said?
Click to expand...
Click to collapse
but where i must enter that code?in cmd?or where?

yes, open up a command window where you have adb and fastboot installed on your PC.
If you do not have them installed then download and install this
minimal_adb_fastboot_v1.1.3_setup.exe - 2.12 MB

brick
gregbradley said:
yes, open up a command window where you have adb and fastboot installed on your PC.
If you do not have them installed then download and install this
minimal_adb_fastboot_v1.1.3_setup.exe - 2.12 MB
Click to expand...
Click to collapse
nothing hapened man...it may be a hard brick???if yes what can i do?

sash89 said:
nothing hapened man...it may be a hard brick???if yes what can i do?
Click to expand...
Click to collapse
By definition a hard brick is not recoverable.
OK, try this.
Code:
adb devices
and tell me what that says.
Also, download and install flashtool from the first thread in the dev section. Open the driver folder from the installation path and run drivers.exe. Choose flashmode, fastboot and TX drivers.
Then run flashtool and attach the phone, disconnect and try attaching in flashmode, disconnect and try to attach in fastboot. Then copy and paste the output from flashtool here.
One final thing, try to attach again in flashmode but this time do this.
Press and hold volume up, attach USB cable, keep pressing volume up and now press the power button. Hold both buttons for 10 seconds or until the green LED comes on. Tell me what happens.

brick
gregbradley said:
By definition a hard brick is not recoverable.
OK, try this.
Code:
adb devices
and tell me what that says.
Also, download and install flashtool from the first thread in the dev section. Open the driver folder from the installation path and run drivers.exe. Choose flashmode, fastboot and TX drivers.
Then run flashtool and attach the phone, disconnect and try attaching in flashmode, disconnect and try to attach in fastboot. Then copy and paste the output from flashtool here.
One final thing, try to attach again in flashmode but this time do this.
Press and hold volume up, attach USB cable, keep pressing volume up and now press the power button. Hold both buttons for 10 seconds or until the green LED comes on. Tell me what happens.
Click to expand...
Click to collapse
nothing happens man...no leds showing up no connection to pc...only this is showing up on device manager when i connect phone to pc qualcomm hs-usb qdloader 9008 com8

This is not looking good for you.
Try this link
or this google search
but I have not heard of good things with phones that want that driver. Best of luck and hopefully someone can come up with a solution

sash89 said:
Hey people!i need help here!i have an xperia v with bootloader unlocked and last day i flashed an img kernel of cyanogenmod with flashify...all worked good until reboot...when i pressed reboot my phone didn't started anymore.when i try to power up nothing happens no leds no fastboot nothing!what can i do to fix it????please help
Click to expand...
Click to collapse
Try SUS bro..
http://forum.xda-developers.com/showthread.php?p=45965388
Sent from my C6602 using xda premium

YudiA1 said:
Try SUS bro..
http://forum.xda-developers.com/showthread.php?p=45965388
Sent from my C6602 using xda premium
Click to expand...
Click to collapse
He cannot connect in flashmode, so that wont work, he will have to solve the connection problem before repairing the OS

brick
gregbradley said:
He cannot connect in flashmode, so that wont work, he will have to solve the connection problem before repairing the OS
Click to expand...
Click to collapse
so may i send it to warranty?what are your suggestions guys?

sash89 said:
so may i send it to warranty?what are your suggestions guys?
Click to expand...
Click to collapse
Your warrenty is void because you unlocked the bootloader.

oh one more thought from me. you sure your battery wasnt gone empty while you did flashing stuff?
happened to me one time, restored backup and battery gone empty while in the process. it looked dead too for some time, but wasnt.

brick
immerblind said:
oh one more thought from me. you sure your battery wasnt gone empty while you did flashing stuff?
happened to me one time, restored backup and battery gone empty while in the process. it looked dead too for some time, but wasnt.
Click to expand...
Click to collapse
and what is this meaning man?my battery was something like 18 percent when i flashed...so may the battery be broken?anyway when i put the phone into charge without battery red led flashes for one time...what this means?

when you put charger in, is it loading the battery the usual way like it did before you broke your handy?
also you not answered one of my previous posts, you flashed the CM kernel without flashing any CM rom. you on stock sony rom or on cm when mistake happens?

immerblind said:
when you put charger in, is it loading the battery the usual way like it did before you broke your handy?
also you not answered one of my previous posts, you flashed the CM kernel without flashing any CM rom. you on stock sony rom or on cm when mistake happens?[/QUOTEi was on stock rom man
Click to expand...
Click to collapse

[Q] zeus mode ?!?!?!?

hi guys,
today i have bricked my z...i was only formatting the sd card and then it reboot and then it died...i tried everything but it won't turn on...the strange thing is when i plug it to my pc, it knows it as ZEUS FLASH DEVICE
there are no led blinking and i tried with hard reset but nothing...i had nameless rom 4.4.2 with unlocked bootloder
what i should do?
UPDATE: if i press power+volume + it reboots in the same mode but it doesn't vibrate or turn on leds

up

flash with flashtool if not solved problem is hw .

lauri_ylonen said:
flash with flashtool if not solved problem is hw .
Click to expand...
Click to collapse
Flashtool in this case is useless and i don t think is hardware...when i plug it in the pc (usb) it recognize it as zeus flash device but you can t do anything...no recovery no flashboot no flashmode...anyway i have sent it in assistance and i m not sure they will repair it

ex19961996 said:
Flashtool in this case is useless and i don t think is hardware...when i plug it in the pc (usb) it recognize it as zeus flash device but you can t do anything...no recovery no flashboot no flashmode...anyway i have sent it in assistance and i m not sure they will repair it
Click to expand...
Click to collapse
please check this method
http://forum.xda-developers.com/showthread.php?t=2646405

lauri_ylonen said:
please check this method
http://forum.xda-developers.com/showthread.php?t=2646405
Click to expand...
Click to collapse
thank you but this method isn't compatible with z yet...there isn't "test point" and package...i have to do all this on my own?

[HELP] Boot loop and Cannot enter recovery/fastboot/flashmode

Guys,
I flashed a stock kernel (.207) through fastboot for relocking bootloader.. I was on CM 10.2 (FXP)
I was planning to flash .207 stock through flashmode after relocking BL
But the phone continuosly bootloops. It does not stay in fastboot or flashmode for more than 2 secs, so I cant flash the original kernel of CM 10.2
Also, pc says USB device not recognized when I connect in fastboot or flashmode,I have installed all the drivers also.
Please help me out guys, its urgent..
SOLVED:
Tried this method:
"You mean the problem you were facing is, it keeps on bootlooping even you turn it off via yellow button(off button at the back).then you need to do this. First, ready the flash tool ( until it it prompts to connect the phone.) Then open the back cover, you need a stick or a ballpen to be a tool for pressing the button, then put the pen in standing posistion(the tip's up) hold your phone,place the yellow button against the tip of the pen, press the volume down(if im not mistaken for the flashmode). If you follow me right, you will notice that if you push your phone down, the tip of the pen will trigger the button.. Then ready your usb data cable using your other hand but dont insert it in this point... Now press your phone down until it turn off. Hold and press the volume down(dont release it until you see the green light. Count to five so the movements will sync, after 5 release the pen and immediately attach the cable. If your lucky enough, you can do this in first try."
IT WORKED!!! LIFE SAVER! thanks to Aljon!!

Uhm to relock the bootloader you need to install a Stock ROM via Flashtool.. No need to mess with fastboot mode etc etc..
You could try to reflash the boot.img from the FXP you used before.
~~ Regards

mrjraider said:
Uhm to relock the bootloader you need to install a Stock ROM via Flashtool.. No need to mess with fastboot mode etc etc..
You could try to reflash the boot.img from the FXP you used before.
~~ Regards
Click to expand...
Click to collapse
THe problem is my phone does not stay in fastboot or flashmode long enough
It again goes into bootloop
Also my pc says USB not recognized even when I have installed all drivers (both win 7 and 8)

Use another cable? Or USB port
~~Regards

Xperia SP Hard Bricked , Possible Solution ?

HI everyone
i have hard bricked my xperia sp , my xperia sp is c5302 i have falshed c5303 ftf its hard bricked
Led not working when put in charge and when connected with pc
power button not working
hard reset button not working (back on the phone)
display not working
fastboot and flashmode not working
but when connected with pc qhsusb_dload driver instalation started and windows cant find drivers , i updated the drivers manually
and treid testoint method but its not working
log:
20-03-2015 15:57:45 will use DLOAD protocol ...
20-03-2015 15:57:45 0808010600900000
20-03-2015 15:57:45 0D0F50424C5F446C6F6164564552322E30
20-03-2015 15:57:45 162001000100
20-03-2015 15:57:45 17004001000100E1108800
20-03-2015 15:57:45 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
20-03-2015 15:57:46 PHONE NOT SUPPORTED IN THIS MODE
20-03-2015 15:57:46 Elapsed:19 secs.
but i havent opened the device and used metal with testpoint
because there is no successfull report on working on xperia sp in the forum
Is there any one sucessfully unbricked using test point method or any other method to unbrick
And im willing to donate for the solution
regards
david

Hi,
First of all : There is no hard brick for Xperia SP. Either you have a soft brick or your phone has a hardware default.
Now there are two common cases of soft brick from which you can recover:
The first is some kind of early bootloop. It seems like the phone is off but your phone is bootlooping. This happens if you flash a non working kernel (and can probably also happen with a corrupt kernel).
To recover from this: plug your phone to pc, press volume up and without releasing it, press the reset button on the back. You should keep all the three (volume up, usb and reset) until you see the green led. This mean you are in flashmod and from then just follow the guides !
The second kind generally comes from the first one. It's an empty battery with non working software. It happens if for example you have a bootloop which drains your battery totally.
To recover from this: plug your phone to wall charger (not on computer) and wait for some hours (you will probably need at least 3. Maybe even 5-6 hours) and then try the solution for the first kind of brick.
I don't think I have seen any harder brick than these two and I believe hard brick cannot happen unless you mess with the bootloader (like editing it).
The problem could also be a hardware default. In this case, just send your phone for repair if you still have warranty or buy a new one.

ty
thank you pec0ra for the reply
i can confirm that its not soft brick (bootloop , sony logo,display on) and there is no hardware defect , bootloader is unlocked and i havent played with bootloaders ,never relocked or other things
tried by connecting hard reset button + volume down +volume up to enter flashmode but no it isnt
what happenedd is i have flashed wrong ftf (charge level 50+ percentage) and falshtool succesfully flashed c5303 ftf and removed usb and tried to turn on but power isnt responding phone doesnt turned on and back hardreset button also failed to reboot the phone , when i coonected with pc it tried to install qualcomm drivers (qhsusb_dload)
i dont know what will happen after flashing wrong ftf technically
can you say about that little more that would be helpfull
thank you

uh oh said:
thank you pec0ra for the reply
i can confirm that its not soft brick (bootloop , sony logo,display on) and there is no hardware defect , bootloader is unlocked and i havent played with bootloaders ,never relocked or other things
tried by connecting hard reset button + volume down +volume up to enter flashmode but no it isnt
what happenedd is i have flashed wrong ftf (charge level 50+ percentage) and falshtool succesfully flashed c5303 ftf and removed usb and tried to turn on but power isnt responding phone doesnt turned on and back hardreset button also failed to reboot the phone , when i coonected with pc it tried to install qualcomm drivers (qhsusb_dload)
i dont know what will happen after flashing wrong ftf technically
can you say about that little more that would be helpfull
thank you
Click to expand...
Click to collapse
I'm not sure about this, but I think flashing a c5305 firmware on a c5302 shouldn't brick your phone but only your wireless connectivity.
The bootloop I talked about is a bootloop that happens before the sony logo displays. Booting android happens approximately so :
Reset signal sent to cpu
Load kernel (I'm not sure but this should be done by some hardware procedures and the bootloader) and initialize devices
Load ramdisk and display splash logo (sony)
Launch android and display boot animation
If you have a bootloop at 4 (after the boot animation has appeared), it means your kernel is working but your rom has a problem (for example it is not compatible with the kernel)
If you have a bootloop at 3 (after the splash logo has appeared), it means you have a problem in the ramdisk
If your CPU is totally broken, you might never arrive at 2
Now the interesting part is if your kernel is broken (for example not compatible with your hardware or there is an error in the code or the binaries are corrupted). If an error happens in the kernel, an interrupt signal will be sent to your CPU and you will start again at 1. This will lead in a loop in 1 and 2. Your screen will stay off but your CPU will run at max speed doing the early initialization again and again. This often drains the battery before you find it out.
This kind of hidden bootloop only happened to me when I modified a kernel and made some errors, but I can easily imagine that this can also happen with something going wrong in firmware flashing or corrupted firmware.
I have seen this kind of problem a few times, mainly on my phone, but I've also seen other users report similar problem. My guess is your phone only has this problem and I recommend you to let it charge a few hours and then try to connect it in flashmod.
If the problem isn't the one I mentioned (and this is of course possible), then I can unfortunately not help you further and you should wait for others to reply.
Good luck !

uh oh said:
HI everyone
i have hard bricked my xperia sp , my xperia sp is c5302 i have falshed c5303 ftf its hard bricked
Led not working when put in charge and when connected with pc
power button not working
hard reset button not working (back on the phone)
display not working
fastboot and flashmode not working
but when connected with pc qhsusb_dload driver instalation started and windows cant find drivers , i updated the drivers manually
and treid testoint method but its not working
log:
20-03-2015 15:57:45 will use DLOAD protocol ...
20-03-2015 15:57:45 0808010600900000
20-03-2015 15:57:45 0D0F50424C5F446C6F6164564552322E30
20-03-2015 15:57:45 162001000100
20-03-2015 15:57:45 17004001000100E1108800
20-03-2015 15:57:45 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
20-03-2015 15:57:46 PHONE NOT SUPPORTED IN THIS MODE
20-03-2015 15:57:46 Elapsed:19 secs.
but i havent opened the device and used metal with testpoint
because there is no successfull report on working on xperia sp in the forum
Is there any one sucessfully unbricked using test point method or any other method to unbrick
And im willing to donate for the solution
regards
david
Click to expand...
Click to collapse
Did you select s1 Emergency mode? Do you have s1boot version wich support SP? Which driver did you use? You have to use Gordons Gate drivers.

pec0ra said:
I'm not sure about this, but I think flashing a c5305 firmware on a c5302 shouldn't brick your phone but only your wireless connectivity.
The bootloop I talked about is a bootloop that happens before the sony logo displays. Booting android happens approximately so :
Reset signal sent to cpu
Load kernel (I'm not sure but this should be done by some hardware procedures and the bootloader) and initialize devices
Load ramdisk and display splash logo (sony)
Launch android and display boot animation
If you have a bootloop at 4 (after the boot animation has appeared), it means your kernel is working but your rom has a problem (for example it is not compatible with the kernel)
If you have a bootloop at 3 (after the splash logo has appeared), it means you have a problem in the ramdisk
If your CPU is totally broken, you might never arrive at 2
Now the interesting part is if your kernel is broken (for example not compatible with your hardware or there is an error in the code or the binaries are corrupted). If an error happens in the kernel, an interrupt signal will be sent to your CPU and you will start again at 1. This will lead in a loop in 1 and 2. Your screen will stay off but your CPU will run at max speed doing the early initialization again and again. This often drains the battery before you find it out.
This kind of hidden bootloop only happened to me when I modified a kernel and made some errors, but I can easily imagine that this can also happen with something going wrong in firmware flashing or corrupted firmware.
I have seen this kind of problem a few times, mainly on my phone, but I've also seen other users report similar problem. My guess is your phone only has this problem and I recommend you to let it charge a few hours and then try to connect it in flashmod.
If the problem isn't the one I mentioned (and this is of course possible), then I can unfortunately not help you further and you should wait for others to reply.
Good luck !
Click to expand...
Click to collapse
pec0ra after charging my phone for 6 hours (leds off all time) and connected to the pc red led glows in device and windows started searching for drivers and device named as unrecognized and after some time device disconnected from pc
and i treid to boot in flashmode volume down + power , power +volumedown+hard reset button but the led is red and turns off after 3 or 4 sec
i cant boot to flashmode or fastboot ,
2 : kernel is broken or not there to load or wrong kernel , and what might be the cause for not booting up in flashmode or fastboot is that kernel problem.
thank you pec0ra

smogf said:
Did you select s1 Emergency mode? Do you have s1boot version wich support SP? Which driver did you use? You have to use Gordons Gate drivers.
Click to expand...
Click to collapse
s1 emergency mode: yes
s1boot version for sp : yes from the other forum
gordon gate drivers :yes
thank you smogf

uh oh said:
pec0ra after charging my phone for 6 hours (leds off all time) and connected to the pc red led glows in device and windows started searching for drivers and device named as unrecognized and after some time device disconnected from pc
and i treid to boot in flashmode volume down + power , power +volumedown+hard reset button but the led is red and turns off after 3 or 4 sec
i cant boot to flashmode or fastboot ,
2 : kernel is broken or not there to load or wrong kernel , and what might be the cause for not booting up in flashmode or fastboot is that kernel problem.
thank you pec0ra
Click to expand...
Click to collapse
Flashmode is independent from the kernel.
The right combo is volume up + hard reset. Keep them at least 10-15 seconds while connected to usb.

pec0ra said:
Flashmode is independent from the kernel.
The right combo is volume up + hard reset. Keep them at least 10-15 seconds while connected to usb.
Click to expand...
Click to collapse
volume up+hard reset : not working
volume down +hard reset : not working
volume up/down+power , volume up/down + hard reset: red led for 3 or 4 sec then turned off device disconnected
when ever i connect with power button + other button red led for 3 or 4 sec is that when power button is pressed the device try turn on ?
and when connecting with wall charger with pressing power button red led blink (a flash) is that device is in low battery
and one big question should i drain the battery completly and tried to connect in flashmode or charge the device fully overnight and try to boot in flashtool
really thank you pec0ra for the patience , help

try installing another kernel and flash any rom?

Marília de Oliveira said:
try installing another kernel and flash any rom?
Click to expand...
Click to collapse
cant boot to flashmode or fastboot
@noahvt can you help with this thank you

uh oh said:
cant boot to flashmode or fastboot
@NovaHt can you help with this thank you
Click to expand...
Click to collapse
Try to install the drives in FlashTool

Marília de Oliveira said:
Try to install the drives in FlashTool
Click to expand...
Click to collapse
installed drivers from flastool/drivers
commom flashmode
common fastboot
and viskan board

uh oh said:
volume up+hard reset : not working
volume down +hard reset : not working
volume up/down+power , volume up/down + hard reset: red led for 3 or 4 sec then turned off device disconnected
when ever i connect with power button + other button red led for 3 or 4 sec is that when power button is pressed the device try turn on ?
and when connecting with wall charger with pressing power button red led blink (a flash) is that device is in low battery
and one big question should i drain the battery completly and tried to connect in flashmode or charge the device fully overnight and try to boot in flashtool
really thank you pec0ra for the patience , help
Click to expand...
Click to collapse
I'd say the red blink is a good sign but unfortunately I have no further knowledge to help you. If I find the time I'll make some tests.
In the mean time, you should try your computer with another phone to see if usb works and/or try with another computer.

pec0ra said:
I'd say the red blink is a good sign but unfortunately I have no further knowledge to help you. If I find the time I'll make some tests.
In the mean time, you should try your computer with another phone to see if usb works and/or try with another computer.
Click to expand...
Click to collapse
thank you pec0ra hope it would be fixed , and one last ques where i can download zeus flash drivers
:highfive:

uh oh said:
thank you pec0ra hope it would be fixed , and one last ques where i can download zeus flash drivers
:highfive:
Click to expand...
Click to collapse
Zeus Flash Driver is in Gordon Gates package. But U have to select this driver manually. Default is SEMC Flash Device.

smogf said:
Zeus Flash Driver is in Gordon Gates package. But U have to select this driver manually. Default is SEMC Flash Device.
Click to expand...
Click to collapse
after bricking phone is not recognised as semc flash device, now my device is connecting only in qhsusb_dload
and in drivers its qhsusb_dload qualcom hs-usb QDloader 9008(com13)
thank you for clearing zeus flash

uh oh said:
after bricking phone is not recognised as semc flash device, now my device is connecting only in qhsusb_dload
and in drivers its qhsusb_dload qualcom hs-usb QDloader 9008(com13)
thank you for clearing zeus flash
Click to expand...
Click to collapse
Of course is recognized as qhsusb_dload. Thats why U have to install Gordons Gate drivers.

smogf said:
Of course is recognized as qhsusb_dload. Thats why U have to install Gordons Gate drivers.
Click to expand...
Click to collapse
sorry for wrong info, device connected as zeus flash device(with power button pressed , normally device is not recognized) , disconnects after a minute

uh oh said:
sorry for wrong info, device connected as zeus flash device(with power button pressed , normally device is not recognized) , disconnects after a minute
Click to expand...
Click to collapse
Do you have any LED light? Below example from my hardbricked Xperia S.
When I've connected Xperia S to computer, red light show up. After a little while LED turn off, and device is recognized as qhsusb_dload (SEMC Flash Device, Zeus flash device, or which driver I have installed or I havent.) No matter. The thing is, that my phone is recognize after RED led turn off. Dont know how about SP, but I suppose that can be similar.
In the end. Launch s1boot, select sin_file_set wich you have to flash (theres a Thread with proper file to recover boot) click on Testpoint Ready and connect the phone to usb. I suppose not, but can work without disassembling device and attaching testpoint. You have to try.

Serious problem.Phone not booting!

My phone unsuddenly bricked after I reboot my phone.Can't even boot into recovery cause Sony logo appear for a second and turned off.My phone even don't charge.I tried to flash stock rom via flashtool but phone not detected or after pressing vol down button nothing happened.I also tryed to use fastboot mode to flash boot.img but nothing happened though My phone can turn into fastboot mode.What should I do now?Senior XDA members please help.:crying:
Edit:how can i fix adb "device not found" issue?I installed all the necessary drivers but still not solved. Can't flash stock rom because vol down button not working but the button is fine.
Edit2:How can I fix adb driver issue that not recognizing my phone?
Problem solved!

Maybe died flash boot

Chum.zuizui said:
Maybe died flash boot
Click to expand...
Click to collapse
So is that mean my phone hard bricked?

Røbin said:
So is that mean my phone hard bricked?
Click to expand...
Click to collapse
Yes.i think so

Chum.zuizui said:
Yes.i think so
Click to expand...
Click to collapse
I don't think so because this happened to me long ago when I tried to unlock bootloader.But I did something to the driver to work adb properly and it worked.And now I forgot that method and couldn't find in google also.So I'm really in big trouble.I just don't know why when I want to flash the stock rom and flashtool show in popup to power off the phone and press vol down button and connect to computer using usb cable but vol button don't work or not give any signal to computer.So I can't flash the rom.

Go to sony official site and download drivers.. ZR drivers dont exist but you can use drivers for Z, install those on your computer and use the fastboot method again and you should be fine.. Your phone is only soft bricked.. Hard brick is when there are absolutely no life in the phone at all.. Use a boot.img you know will work and no need to flash stock ROM once you're in recovery.. Unless you want to of course.. Custom ROM will boot your phone just fine
Also take your battery out and re-insert to make sure your phone is properly off.. Flashtool should also work after that

Røbin said:
I don't think so because this happened to me long ago when I tried to unlock bootloader.But I did something to the driver to work adb properly and it worked.And now I forgot that method and couldn't find in google also.So I'm really in big trouble.I just don't know why when I want to flash the stock rom and flashtool show in popup to power off the phone and press vol down button and connect to computer using usb cable but vol button don't work or not give any signal to computer.So I can't flash the rom.
Click to expand...
Click to collapse
Yes.good luck for you

hagar006 said:
Go to sony official site and download drivers.. ZR drivers dont exist but you can use drivers for Z, install those on your computer and use the fastboot method again and you should be fine.. Your phone is only soft bricked.. Hard brick is when there are absolutely no life in the phone at all.. Use a boot.img you know will work and no need to flash stock ROM once you're in recovery.. Unless you want to of course.. Custom ROM will boot your phone just fine
Also take your battery out and re-insert to make sure your phone is properly off.. Flashtool should also work after that
Click to expand...
Click to collapse
ZR driver exist in Sony developer website and I installed the driver but I don't know why my computer not recognizing my phone.My phone can turn into fastboot mode(blue light on when pressing vol up and connecting cable to pc) but when I type command "adb devices" the listed device is empty I mean no adb fastboot device found.I'm just asking the drivers are not working beacuse of windos 10?Actually when after I use custom rom I couldn't connect my phone to pc.So any driver can fix this problem?I searched really hard on google but couldn't find any proper sloutions.

Chum.zuizui said:
Yes.good luck for you
Click to expand...
Click to collapse
This isn't helping!

Windows 10 is a pain to install drivers into.. But use fastboot in flashtool instead of flasmode.. Should recognize your phone and flash the boot image from there

hagar006 said:
Windows 10 is a pain to install drivers into.. But use fastboot in flashtool instead of flasmode.. Should recognize your phone and flash the boot image from there
Click to expand...
Click to collapse
I know you are trying to help me but I tried everything and nothing is working.I installed driver from flashtool but still no clue why pc not recognizing my phone.My phone is like a live junk.My phone soft bricked many times and I could recover my phone with flashtool so I know what to do but this problem is way more confusing.I just need to know what is causing this issue.

You've managed to install the drivers inc the lagan drivers in flashtool and connected your phone in fastboot mode with flashtool running and flashtool still don't recognize your phone? I've done that loads of times even with no drivers installed and flashtool has been able to recognize the device in fastboot.. If that's the case, then I'm sorry I'm not able to help any further as flashtool has always been my failsafe when things have gone wrong.. Adb and fastboot are usually no help for me in Windows 10..

hagar006 said:
You've managed to install the drivers inc the lagan drivers in flashtool and connected your phone in fastboot mode with flashtool running and flashtool still don't recognize your phone? I've done that loads of times even with no drivers installed and flashtool has been able to recognize the device in fastboot.. If that's the case, then I'm sorry I'm not able to help any further as flashtool has always been my failsafe when things have gone wrong.. Adb and fastboot are usually no help for me in Windows 10..
Click to expand...
Click to collapse
Flashtool is the best tool to recover soft bricked phone I know but this problem is way more complicated.
Thanks that you tried to help me.I hope I'll figure it out some time later.

Røbin said:
This isn't helping!
Click to expand...
Click to collapse
I dont meant it like that .did you fix it

Chum.zuizui said:
I dont meant it like that .did you fix it
Click to expand...
Click to collapse
Unfortunately no.For some reason pc not detecting fastboot device even after I installed fastboot driver.

same problem plz help
I have same problem . phone not charging ,not booting , just sony logo comes for a sec then it turns off .
I'm tired of searching for a solution almost a week but nothing helped me.
Last day i flashed a stock rom via flash tool , still problem persists .
Pc companion -no detection of device , can't boot into recovery mode..
Please guys help me.. I'm in serious trouble with my phone

pralay445 said:
I have same problem . phone not charging ,not booting , just sony logo comes for a sec then it turns off .
I'm tired of searching for a solution almost a week but nothing helped me.
Last day i flashed a stock rom via flash tool , still problem persists .
Pc companion -no detection of device , can't boot into recovery mode..
Please guys help me.. I'm in serious trouble with my phone
Click to expand...
Click to collapse
My problem was created because local charger damaged my phone battery.So I couldn't turn on my device like yours.I replaced the battery and charger from Sony Center and now my phone is good as new.So Try to use other good battery(small or similer size that suites to your phone's battery pin)and see if your phone turns on without any issue.Then you can target the problem.