[DISASTER RECOVERY][v3.6] Getting your Z1/ZU/Z/ZL back to life!

[swooc]

yeah it does suck. it was a risk i took knowing full well that i'll have to drop some cash to send it back for warranty if i had to. just waiting for a rma now and off it goes. ah well.

thanks for the help anyway nut. much appreciate it.

 

[[NUT]]

Updated OP to include the reset operation for the Z Ultra and the Z1

 

[mcyorian]

Updated OP to include the reset operation for the Z Ultra and the Z1

thanx for this post NUT!!!

mi question is ... Is there any solution?

DUMB ERROR HERE!!!!
I was flashing a rom but i make a big mistake and install another rom instead,( i use my phone as a usb sometimes! i forgot to delete another rom from my sd card) "MIUI for GALAXY S3" or something! Battery was over 86%

PROBLEMS:

1- No Leds (NO is NO!)
2- Phone doesnt vibrate ( not even hard keys combos, not anyones! )
3- Conecting to PC and PC doesn recognize Phone Sound alert for usb not dirvers
4- device manager on PC shows my phone as "qhsusb_dload" with yellow alert for no drivers.
5- Flashtool doesnt see my phone on eny mode Fastboot or Flashtool


Any help?

I hope find a method to trick the driver an tell my pc is a XPERIA Z....
i read another post and they said to put my xperia on wall chargers until battery drained complete to 0% and wait for a red led, if the led turns on there is a hope.
but this post is about xperia S , arc, and anothers, cn this trick be possible on XZ too? ( rubberband trick, battery 0% etc,...)????

Any solutions?

Thanks!!! ( and sorry for my english)

 

[ILoveXperia]

hello all, @[NUT] need help.. my xz suffer the soft brick. it happen when i try to update through sony pc companion. currently on .432 if not mistaken. update was the latest one. i try to fastboot but im stuck at flashing the kernel.sin through fastboot. btw, the phone automatically goes into flashmode when connected to pc. my phone was rooted through ur method of rooting with dualrecovery. please help me.. below is my log
20/052/2013 16:52:09 - INFO - <- This level is successfully initialized
20/052/2013 16:52:09 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
20/052/2013 16:52:10 - INFO - Device disconnected
20/054/2013 16:54:06 - INFO - Device connected in fastboot mode
20/054/2013 16:54:13 - INFO - Device Status: FASTBOOT mode
20/054/2013 16:54:35 - INFO - Device Status: FASTBOOT mode
20/054/2013 16:54:40 - INFO - Device will now exit fastboot mode and start booting into system
20/054/2013 16:54:40 - INFO - Device disconnected
20/054/2013 16:54:46 - INFO - Device connected in flash mode
20/054/2013 16:54:55 - INFO - Device disconnected
20/004/2013 17:04:11 - INFO - Bundle creation canceled
20/005/2013 17:05:49 - ERROR - This action can only be done in fastboot mode
20/006/2013 17:06:01 - INFO - Device connected in fastboot mode
20/006/2013 17:06:12 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Avelino\Desktop\destop\xperia z\kernel.sin
20/006/2013 17:06:12 - INFO - Flashing selected kernel
20/007/2013 17:07:53 - ERROR - This action can only be done in fastboot mode
20/008/2013 17:08:07 - INFO - Device Status: NOT FOUND
20/008/2013 17:08:11 - INFO - sending 'boot' (7645 KB)...
20/008/2013 17:08:11 - INFO - FAILED (data transfer failure (Too many links))
20/008/2013 17:08:11 - INFO - finished. total time: 118.147s
20/008/2013 17:08:11 - INFO - FASTBOOT Output:
sending 'boot' (7645 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 118.147s

20/008/2013 17:08:11 - INFO - Please check the log before rebooting into system
20/008/2013 17:08:11 - INFO - Device disconnected
20/008/2013 17:08:33 - INFO - Device connected in fastboot mode
20/008/2013 17:08:38 - INFO - Fetching connected device info
20/008/2013 17:08:38 - INFO - Connected device info: [ BX903H1N23 ]
20/008/2013 17:08:43 - INFO - Fetching fastboot version info from connected device
20/008/2013 17:08:43 - INFO - FASTBOOT version info: [ version: 0.5 ]
20/008/2013 17:08:49 - INFO - Device Status: FASTBOOT mode
20/008/2013 17:08:53 - INFO - Device will now exit fastboot mode and start booting into system
20/008/2013 17:08:54 - INFO - Device disconnected
20/008/2013 17:08:59 - INFO - Device connected in flash mode
20/009/2013 17:09:03 - INFO - Device disconnected
20/009/2013 17:09:09 - INFO - Device connected in fastboot mode
20/009/2013 17:09:16 - ERROR - This action needs a connected device in ADB mode
20/009/2013 17:09:30 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Avelino\Desktop\destop\xperia z\kernel.sin
20/009/2013 17:09:30 - INFO - Flashing selected kernel
20/016/2013 17:16:45 - ERROR - This action can only be done in fastboot mode
20/017/2013 17:17:32 - INFO - sending 'boot' (7645 KB)...
20/017/2013 17:17:32 - INFO - FAILED (data transfer failure (Too many links))
20/017/2013 17:17:32 - INFO - finished. total time: 481.454s
20/017/2013 17:17:32 - INFO - FASTBOOT Output:
sending 'boot' (7645 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 481.454s

20/017/2013 17:17:32 - INFO - Please check the log before rebooting into system
20/017/2013 17:17:32 - INFO - Device disconnected
20/018/2013 17:18:09 - INFO - Device connected in fastboot mode
20/018/2013 17:18:28 - INFO - Selected system (system.img or system.sin): C:\Users\Avelino\Desktop\destop\xperia z\system.sin
20/018/2013 17:18:28 - INFO - Flashing selected system
20/019/2013 17:19:51 - INFO - Please check the log before rebooting into system
20/019/2013 17:19:54 - INFO - Device will now exit fastboot mode and start booting into system
20/019/2013 17:19:58 - INFO - Device disconnected
20/020/2013 17:20:00 - INFO - Device connected in flash mode
20/020/2013 17:20:21 - ERROR - This action can only be done in fastboot mode
20/020/2013 17:20:25 - INFO - Device disconnected
20/020/2013 17:20:57 - INFO - Device connected in fastboot mode
20/021/2013 17:21:09 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Avelino\Desktop\destop\xperia z\kernel.sin
20/021/2013 17:21:09 - INFO - HotBooting selected kernel
20/024/2013 17:24:02 - INFO - FASTBOOT Output:
creating boot image...
creating boot image - 7831552 bytes
downloading 'boot.img'...
FAILED (data transfer failure (Too many links))
finished. total time: 173.105s

20/024/2013 17:24:03 - INFO - Device disconnected
20/027/2013 17:27:07 - INFO - Device connected in fastboot mode
20/027/2013 17:27:23 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Avelino\Desktop\kernel.sin
20/027/2013 17:27:23 - INFO - Flashing selected kernel
20/030/2013 17:30:04 - INFO - sending 'boot' (7645 KB)...
20/030/2013 17:30:04 - INFO - FAILED (data transfer failure (Too many links))
20/030/2013 17:30:04 - INFO - finished. total time: 161.132s
20/030/2013 17:30:04 - INFO - FASTBOOT Output:
sending 'boot' (7645 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 161.132s

20/030/2013 17:30:04 - INFO - Please check the log before rebooting into system
20/030/2013 17:30:05 - INFO - Device disconnected
20/030/2013 17:30:16 - INFO - Device connected in fastboot mode
20/031/2013 17:31:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\kernel.sin
20/031/2013 17:31:04 - INFO - Flashing selected kernel

 

[[NUT]]

[snip]
1- No Leds (NO is NO!)
2- Phone doesnt vibrate ( not even hard keys combos, not anyones! )
3- Conecting to PC and PC doesn recognize Phone Sound alert for usb not dirvers
4- device manager on PC shows my phone as "qhsusb_dload" with yellow alert for no drivers.
5- Flashtool doesnt see my phone on eny mode Fastboot or Flashtool
[snip]

Anytime I come across a poor soul like you flashing anything samsung related, they end up with a hardbrick... though if your device still shows signs of life like being able to connect it to the PC, then you can certainly try something, though i do have to temper your expectations... it might just as well fail...

Have a look at the hardware id's for that device windows does pick up, I might be able to send you a customized driver to try and fool your pc in to seeing it as an Xperia Z...

Look at the device properties in the device manager:



I need all the info you see here (create a screenshot!).

hello all, @[NUT] need help.. my xz suffer the soft brick. it happen when i try to update through sony pc companion. currently on .432 if not mistaken. update was the latest one. i try to fastboot but im stuck at flashing the kernel.sin through fastboot. btw, the phone automatically goes into flashmode when connected to pc. my phone was rooted through ur method of rooting with dualrecovery. please help me.. below is my log[snip]

Connect the USB cable to your pc ONLY, power off your device with the 10+ seconds hold of power+vol-UP. Then prepare flashtool to flash your device in FLASHmode using an FTF. Deselect all wipe options and exclude everything except system and kernel. Make sure you use a .423 FTF for this.

Then when flashtool is waiting for you to connect the usb cable, hold the VOL-DOWN button WHILE you connect the USB lead to your phone. Flashtool should now start flashing your phone with a working /system and replace the current kernel with the one from the FTF.

Let me know if you where successful

 

[mcyorian]

...Look at the device properties in the device manager

here is the Screen shot, Thanks very much for your attention! and about fake drivers, it would be GENIUS! ....

lets try!



THANX A LOT NUT!!! !

 

[ILoveXperia]

Anytime I come across a poor soul like you flashing anything samsung related, they end up with a hardbrick... though if your device still shows signs of life like being able to connect it to the PC, then you can certainly try something, though i do have to temper your expectations... it might just as well fail...

Have a look at the hardware id's for that device windows does pick up, I might be able to send you a customized driver to try and fool your pc in to seeing it as an Xperia Z...

Look at the device properties in the device manager:

View attachment 2337938

I need all the info you see here (create a screenshot!).



Connect the USB cable to your pc ONLY, power off your device with the 10+ seconds hold of power+vol-UP. Then prepare flashtool to flash your device in FLASHmode using an FTF. Deselect all wipe options and exclude everything except system and kernel. Make sure you use a .423 FTF for this.

Then when flashtool is waiting for you to connect the usb cable, hold the VOL-DOWN button WHILE you connect the USB lead to your phone. Flashtool should now start flashing your phone with a working /system and replace the current kernel with the one from the FTF.

Let me know if you where successful

damm it!!!!!!! it work!!!!!!!!!!!!!!!:victory::victory::victory:
thankyou very much @[NUT] ur guide here works to revive my phone.. from now on i will not play around with update.. for 1 day i was so depress without my phone..
ur help i really appreciate it..:highfive::victory:

 

[[NUT]]

here is the Screen shot, Thanks very much for your attention! and about fake drivers, it would be GENIUS! ....

lets try!



THANX A LOT NUT!!! !

Sorry bro, I've been extremely busy IRL... i'll get you that customized driver package ASAP... I did however search on the name, it seems that even on the Samsung models where you can end up with this as a result of over-flashing your device, getting this means curtains for your phone... But let's try anyway... I HOPE I will have some time to work on it tonight.

damm it!!!!!!! it work!!!!!!!!!!!!!!!:victory::victory::victory:
thankyou very much @[NUT] ur guide here works to revive my phone.. from now on i will not play around with update.. for 1 day i was so depress without my phone..
ur help i really appreciate it..:highfive::victory:

Great! Happy you resurrected your device :highfive:

Now be more careful next time you tinker with your device

 

[[NUT]]

@mcyorian

I've sent you a PM with a link... for obvious reasons I don't want that package out in the public

Let me know if you're successful

 

[mcyorian]

@mcyorian

I've sent you a PM with a link... for obvious reasons I don't want that package out in the public

Let me know if you're successful

THANKS!... see your PM!

you are unique NUT!

 

[lordzedd]

hi

i have a problem...
i have tried to install the newest cm rom on my sxz.
at first i installed the cwm recovery and then i follow a instruction to install cm and gapps.
This all works fine but after the install the phone didnt boot. There only was one vibrate and sometimes the red led. I follow your instruction and now i have a bootloop

I dont know what i should do now. i tried the sus but after connecting the sus says that i have the newest firmware and i only can close the program...dont know whats going on here

maybe someone can help me?

aaaand sry for my english but i'm a german.

 

[[NUT]]

hi

i have a problem...
i have tried to install the newest cm rom on my sxz.
at first i installed the cwm recovery and then i follow a instruction to install cm and gapps.
This all works fine but after the install the phone didnt boot. There only was one vibrate and sometimes the red led. I follow your instruction and now i have a bootloop

I dont know what i should do now. i tried the sus but after connecting the sus says that i have the newest firmware and i only can close the program...dont know whats going on here

maybe someone can help me?

aaaand sry for my english but i'm a german.

Please try to be detailed on how you tried to return to stock... the devil is usually in the little details...

I have actually written a guide for this, requested by someone who had the same problem as you: [GUIDE] How to revert your phone from CM/AOSP/AOKP/PAC to STOCK

Try to follow this to restore your phone.

 

[szunyi77]

Please try to be detailed on how you tried to return to stock... the devil is usually in the little details...

I have actually written a guide for this, requested by someone who had the same problem as you: [GUIDE] How to revert your phone from CM/AOSP/AOKP/PAC to STOCK

Try to follow this to restore your phone.

hi
Help me please!
There is a big problem
This thread has been reported, but unfortunately they can not help!


Aborted updates, bootloop

The flashtool does not recognize the device ...
connect and disconnect constantly!

I do not know what I should have done
I tried what you wrote at the beginning of the post, but unfortunately does not work either!

 

[[NUT]]

hi
Help me please!
There is a big problem
This thread has been reported, but unfortunately they can not help!


Aborted updates, bootloop

The flashtool does not recognize the device ...
connect and disconnect constantly!

I do not know what I should have done
I tried what you wrote at the beginning of the post, but unfortunately does not work either!

If you turn off your phone, and try to turn it on again, what does it do exactly?

Please calm down and answer my questions, I did read some of the other thread, so I have an idea what is happening.

Let's take this one step at a time, ok?

Sent from my C6603 using xda app-developers app

 

[szunyi77]

If you turn off your phone, and try to turn it on again, what does it do exactly?

Please calm down and answer my questions, I did read some of the other thread, so I have an idea what is happening.

Let's take this one step at a time, ok?

Sent from my C6603 using xda app-developers app

Thanks for the quick reply

when the phone is turned off does not blink and do not respond to anything!
whatever clues it does not vibrate, will not restart does not blink!

When I connect the charger, then it vibrates 1 and 3 and the red light flashes ... And keep doing it!

So if you connect the charger, the red light at the villa for a while and then goes out

 

[[NUT]]

Thanks for the quick reply

when the phone is turned off does not blink and do not respond to anything!
whatever clues it does not vibrate, will not restart does not blink!

When I connect the charger, then it vibrates 1 and 3 and the red light flashes ... And keep doing it!

So if you connect the charger, the red light at the villa for a while and then goes out

So, if I understood you correctly, it only does something when you connect an USB charger or connect it to the pc?

 

[szunyi77]

So, if I understood you correctly, it only does something when you connect an USB charger or connect it to the pc?

Yes, you can respond to anything you are connected!

whatever traces (power, volume up and down) does nothing!

When connected to a PC, you can connect the loop-disconnet keep you!

 

[[NUT]]

Yes, you can respond to anything you are connected!

whatever traces (power, volume up and down) does nothing!

When connected to a PC, you can connect the loop-disconnet keep you!

I hope you still have warranty? If so, take it to your service center as soon as you can. An aborted or failed flash is sometimes due to a problem already in your phone. They might have a way to revive phones which are not bricked (like yours) but malfunctioning in some way.

If you have no warranty, you could try to buy a charging dock (even 3rd party ones are OK) and try to charge it with that to see if you can power it on the regular way. But in this case I have to say it's a bit of a long shot...

There is not much I can do to help you out now, sorry!

 

[szunyi77]

I hope you still have warranty? If so, take it to your service center as soon as you can. An aborted or failed flash is sometimes due to a problem already in your phone. They might have a way to revive phones which are not bricked (like yours) but malfunctioning in some way.

If you have no warranty, you could try to buy a charging dock (even 3rd party ones are OK) and try to charge it with that to see if you can power it on the regular way. But in this case I have to say it's a bit of a long shot...

There is not much I can do to help you out now, sorry!

Unfortunately, there are no guarantees have been
I understand it is discharged, and docks shall be filled for the first time?

 

[[NUT]]

Unfortunately, there are no guarantees have been
I understand it is discharged, and docks shall be filled for the first time?

You can try it, but as I said: it's a long shot: it might not work out in the end...