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.
Hello,
few days ago i unlocked bootloader and installed twrp on my l90 d405n. Unfortunetly, something went wrong and now my phone is fully bricked. Windows see the phone only as 60mb disc with two folders, on phone screen is still black.
I tried this: (remove space)
ht tp://android forums.com /threads/guide-unbrick-lg-l70-no-download-mode-no-recovery-mode-no-fastboot.893311/
but main problem is that idk what version of software i've got (10a, 10b, 20b, etc.), only remember it was rooted android 5.0.2. I tried few aboot's, but effect is still the same - nothing happens.
it may be due to bad recovery version o rbad aboot? What can i do?
Plz help and sry for bad English
check private
TreQUS said:
check private
Click to expand...
Click to collapse
So did you find out!?!?!? I need help, I have the same problem, I am missing loader.img for D405n!
same problem
almost same problem, no download mode or anything else just as same as first reply when connecting to pc there are two folders. pls fully explain.
I have the exact problemm as well.. EXPLAIN!!
I had the same problem, but then i tried the guide with replaceing aboot boot recovery files and now my pc doesnt even see the 60mb disk. When i plug my phone to charger or pc without battery in it shows that its missing but when i put t back in nothing happens the screen just stays balack or shows 0% for a sec. When i connect it to pc nothing happens and when i hold the power button the sound of conecting a device is playd and after a sec the disconection sound plays.
Is there any hope for my device??
come on guys we need a fix please help
If your computer still recognizes it, you may be in a soft-brick. Try flashing your stock ROM onto your LG L70 and wipe caches.
Sent from my LG-D415
Hello
Have you found the solution? I have same problem
Please guys ! this happens to now...me... anyone can help me whit the solution? I have no phone now :/
Is there a TOT File for LG L90 D405n?I cant find it.Mobile phone of my 13yold son is hard brick now.Device manager shows as Qualcomm HS-USB QDLoader 9008 .
Can someone help me please? Im willing to donate him if the device unbrick.
Im trying and looking for solution 3 days now but no result.
Finaly i unbrick the device
Hi everyone !
I've a Xperia SP which wont turn on anymore ... i installed a recovery, made a wipe factory, since it doesnt turn on :'(
Just so you know, i installed PhilZ Touch and TWRP (but i dont succeed to access them now, if someone know the manipulation ...)
However, i can access the Flash Mode, so I installed Flashboot (9.19.8), installed ALL the driver which were available in the "driver" directory, and tried to flash 4 differents TFT files, i tried on every USB port, with an officiel USB cable from Sony... didnt work
I've always the same error: Processing of system.sin finished with errors.
and then, the phone boot on "Sony" logo, then turn off, finally go in flash mode again endlessly as long as i let it plugged to my PC.
I dont know what to do, so here i am. Maybe all the rom i tried arent stock or arent compatible with my Locked bootloader ? Maybe its too low in battery (but before the recovery installation, it has something like 75% ...).
Thanks for your help !
roxasaxel said:
Hi everyone !
I've a Xperia SP which wont turn on anymore ... i installed a recovery, made a wipe factory, since it doesnt turn on :'(
Just so you know, i installed PhilZ Touch and TWRP (but i dont succeed to access them now, if someone know the manipulation ...)
However, i can access the Flash Mode, so I installed Flashboot (9.19.8), installed ALL the driver which were available in the "driver" directory, and tried to flash 4 differents TFT files, i tried on every USB port, with an officiel USB cable from Sony... didnt work
I've always the same error: Processing of system.sin finished with errors.
and then, the phone boot on "Sony" logo, then turn off, finally go in flash mode again endlessly as long as i let it plugged to my PC.
I dont know what to do, so here i am. Maybe all the rom i tried arent stock or arent compatible with my Locked bootloader ? Maybe its too low in battery (but before the recovery installation, it has something like 75% ...).
Thanks for your help !
Click to expand...
Click to collapse
Please use 0.9.18.6 or 0.9.19.8. Download the proper version of Flashtool here: http://www.flashtool.net/downloads.php
Then download the stock firmware by using Xperifirm that comes with the Flashtool, afterwards flash the stock firmware.
Also what Windows are you on?
I search for 6hours without anything, i post here ... and 10min after i found the problem ...
Flashtool isnt working for my phone after the 9.18.6 version o_o
so its ok now ! ty
Edit: ty techno, i already found !
roxasaxel said:
I search for 6hours without anything, i post here ... and 10min after i found the problem ...
Flashtool isnt working for my phone after the 9.18.6 version o_o
so its ok now ! ty
Edit: ty techno, i already found !
Click to expand...
Click to collapse
Nice
But have you solved your problem??
Hi. Ive had some bad luck this weekend, firstly i had a rooted xperia sp that i rooted with the app it all worked fine for a long time. Then this last week i decided to flash a rom for the first time on this device (have done many times on my old xperia x10) everyting went well but i had really bad cellphone reception with this rom (http://forum.xda-developers.com/xperia-sp/development/xperiasp-locked-bootloader-lbl-t2947194) so i tought why not flash another rom?
Thats what i set up myself to do, i found this rom (http://forum.xda-developers.com/xpe...rom-6-0-1-cyanogenmod-13-0-xperia-sp-t3347677) and it seemd well done and all but it required a unlocked bootloader so i decide why not just flash a kernel with it unlocked already... so i found this thread (http://forum.xda-developers.com/showthread.php?t=2345567) and did the recovery method.
After this the cellphone wouldnt boot anymore (boot loop) so i tried to find a solution, the solution i found was to flash a whole new firmware so it would work fine, so thats what i tried i downloaded a image with flashtool (xperifirm)
the customized br 1271-6480 at this point i could still put the phone on fastboot and flashmode, so i started to flash that new firmware, the problem came when the cellphone disconnected (probably becouse of the boot loop) so now i have a brick.
Ive tried alot of things multiple versions of s1tools none of them "support" my device also downloaded QPST downloader the really old one version 2.7 it does detect my device when im on this "mode" with the driver "Qualcomm HS-USB QDLoader 9008" i can change back to the "ZEUS flash device" easily for s1tools but after all these hours of tests ive ran out of options... ive even opened the device 2 times the second time ive seem that when i remove the battery cable it flashes the red led once and then turns off.
any other tests i can do or just send it to someone to fix and they will ask for half of the phone price for it?
ps ive also tried to the rubber band method for about 12 hours no luck
Follow this guide to repair your phone using Xperia companion:
https://talk.sonymobile.com/t5/FAQ/How-to-perform-a-software-repair-with-PC-Companion/m-p/1061294
Sent from my Xperia SP using Tapatalk
OsGhaly said:
Follow this guide to repair your phone using Xperia companion:
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
i get stuck step 11 since i cant turn on the cellphone with flashmode otherwise i would fix it with flashtool right?
i would post a image but i cant becouse i dont have 10 posts...
warlockxx said:
i get stuck step 11 since i cant turn on the cellphone with flashmode otherwise i would fix it with flashtool right?
i would post a image but i cant becouse i dont have 10 posts...
Click to expand...
Click to collapse
For step 10, make sure that you've turned off the phone completely by pressing this tiny button in the back till it vibrates 3 times then connect the phone while holding the volume down key to enter flash mode and continue flashing.
I also recommend using this official way to repair your phone using Xperia companion to avoid hard brick, as our old XSP already has problems with the new versions of flashtool
Sent from my Xperia SP using Tapatalk
OsGhaly said:
For step 10, make sure that you've turned off the phone completely by pressing this tiny button in the back till it vibrates 3 times then connect the phone while holding the volume down key to enter flash mode and continue flashing.
I also recommend using this official way to repair your phone using Xperia companion to avoid hard brick, as our old XSP already has problems with the new versions of flashtool
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
my phone turns off if i press the reset button on the back i know that becouse i can see the " Qualcomm HS-USB QDloader 9008" but it does not vibrate since i have tried to keep that button down for 5 minutes and nothing happened, also when i try to turn on again with vol down + power it starts again as " Qualcomm HS-USB QDloader 9008"
warlockxx said:
my phone turns off if i press the reset button on the back i know that becouse i can see the " Qualcomm HS-USB QDloader 9008" but it does not vibrate since i have tried to keep that button down for 5 minutes and nothing happened, also when i try to turn on again with vol down + power it starts again as " Qualcomm HS-USB QDloader 9008"
Click to expand...
Click to collapse
Only QPST software download or eMMC software download can repair this phone
Click to expand...
Click to collapse
Just Google it, Sorry dear I wish I could be more help but I really don't know how to do this.
Sent from my Xperia SP using Tapatalk
OsGhaly said:
Just Google it, Sorry dear I wish I could be more help but I really don't know how to do this.
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
ye idk... i have qpst and qfil installed on my pc but i cant make it work since on qpst i dont have the right .hex file and on qfil i dont have the xml file it needs... im kinda of stuck now.