[Q] Xperia Z, What a sad story (Urgent Help) - Xperia Z Q&A, Help & Troubleshooting

Hey guys, I don't know if this is out of topic but since this is for xperia z bricked, I'll show my problem.
So, I updated my xperia z for 3 times since I bought it, It came with Android 4.2.2 and the updates were all OTA.
Then, sudently It started to reboot itself and entering in bootloop.. Then, I tried to use flashtool but always gave me error about S1 flash, and then "Error: Flash Aborted"
So I tried to unlock my bootloader several times (Yes, several times, because it was always saying ok, but then it was showing "ROOTABLE") then, when I Finally got it unlocked, I couldn't flash anything because it was gaving me error saying that couldn't write boot.. Then, Tried Pc companion but again, failed, and my phone was stuck in "Update failed (...)"
Then finally, I flashed advanced kernel by DoomLord and entered in CWM, but when I tried to wipe factory reset, It was saying that couldn't mount data.. Then, I have formated the Data and Media (SD Card) And then, I was able to do factory reset, but, then, I went to advance and did reboot recovery.. My phone turned off, but never came on... I arrived at home and connect ti to wall charger, but no sign of life, nothing, not even red led or anytihng.. NOTHING!! Don't know what happened.. I really need help on this man, please :c

Gabe.INc said:
Hey guys, I don't know if this is out of topic but since this is for xperia z bricked, I'll show my problem.
So, I updated my xperia z for 3 times since I bought it, It came with Android 4.2.2 and the updates were all OTA.
Then, sudently It started to reboot itself and entering in bootloop.. Then, I tried to use flashtool but always gave me error about S1 flash, and then "Error: Flash Aborted"
So I tried to unlock my bootloader several times (Yes, several times, because it was always saying ok, but then it was showing "ROOTABLE") then, when I Finally got it unlocked, I couldn't flash anything because it was gaving me error saying that couldn't write boot.. Then, Tried Pc companion but again, failed, and my phone was stuck in "Update failed (...)"
Then finally, I flashed advanced kernel by DoomLord and entered in CWM, but when I tried to wipe factory reset, It was saying that couldn't mount data.. Then, I have formated the Data and Media (SD Card) And then, I was able to do factory reset, but, then, I went to advance and did reboot recovery.. My phone turned off, but never came on... I arrived at home and connect ti to wall charger, but no sign of life, nothing, not even red led or anytihng.. NOTHING!! Don't know what happened.. I really need help on this man, please :c
Click to expand...
Click to collapse
Your hard bricked my friend when you unlock the bootloader you cannot use pc companion at all. The is a hard brick tutorial in general section by NUT try that it sounds doughnting but you have no choice

Related

[Q][HELP] Xperia Z Possibly Bricked - Wont boot/charge

Hello, ive had my Xperia Z a few weeks now, it has a locked bootloader which has never been unlocked, i rooted my device, flashed CWM, backed up my existing rom and then installed a new one, but i lost all my contact/system info so i restored my previous backup. It said restoring, then 'Failed to Mount /System.' I rebooted device, it just hangs on the Sony logo. The first time this happened i used the Update Service program to reinstall software and factory reset the phone fine, but now it says the battery is below 50% and it will not proceed.
When i plug the phone into the charger, the red light stays on, (Doesnt change colour) and it just hangs on the Sony logo, i cant access recovery menu either.. Anyone have any advice for me ?
Cheers
Switch it off and leave it charging for an hour or 2 then try the update service again
Dinesy said:
Hello, ive had my Xperia Z a few weeks now, it has a locked bootloader which has never been unlocked, i rooted my device, flashed CWM, backed up my existing rom and then installed a new one, but i lost all my contact/system info so i restored my previous backup. It said restoring, then 'Failed to Mount /System.' I rebooted device, it just hangs on the Sony logo. The first time this happened i used the Update Service program to reinstall software and factory reset the phone fine, but now it says the battery is below 50% and it will not proceed.
When i plug the phone into the charger, the red light stays on, (Doesnt change colour) and it just hangs on the Sony logo, i cant access recovery menu either.. Anyone have any advice for me ?
Cheers
Click to expand...
Click to collapse
return it, says that there is a battery failure.
Pm me
Sent from my C6603 using xda app-developers app
Hows it going ? have you sorted yet, if your phone turn on then you can bring it back to life
Use flashtool to flash stock firmware,very easy
http://forum.xda-developers.com/showthread.php?t=2240614
Sent from my C6603 using xda premium
Help please. It happened to me too.
I upgrade my firware to .67, root, dual recovery, no problem. but the problem happens when i followed this thread for deodex http://forum.xda-developers.com/showthread.php?t=2458411
"Copy the rom to your microSD
Backup any important data to your microSD
Boot into recovery and do a nandroid backup first
If you have CWM: select Wipe cache partition and wipe dalvik cache, go into 'mounts and storage' and select Format /system, then /data, then /cache"
Then i tried to reboot recovery, but i choose "**Back** , then it reboot and have a red LED light with a Sony logo. It just stays there, what should i do? Please help...

[Q] Help needed: tried to install Cyanogen 11, can't boot.

Hello all! So, I tried to install CM11, the one on this post.
Went into CWM, did Wipe data factory reset and formatted /system. when I tried installing the rom, it said operation aborted and it could not install it. No biggie, the post says to install cm10.2 before doing so.
So i Powered the phone off to copy the file over to the SD. To my surprise, now I can't get into CWM, Philz, TWRP, fastboot or flashmode. Whenever I press the back pin to power the phone off, it turns back on automatically before I have time to press the key and connect the USB cable. Furthermore, when I manage to do it quick enouhg, the green led lights up, but it fades away after 10ish seconds only to display the sony logo again, and a "can't recognize USB device" popup comes up in my PC. I've used flashtool with this same pc in the past, so I don't know what that is about. Also, whenever I try installng flashtool drivers again, just in case 2 things happen:
there is no xperia SP device listed and whatever i select it fails to install.
What can I do now? I had 4.3 with the eXistenZ Ultra ROM before all of this.
Damm, this is the first time this happens to me, I've been swapping roms for ever, and this is not even the first phone i do this in, had a galaxy s2 and a wildfire S before. I feel like such a noob
UPDATE!:
So I finally managed to fix it. I posted this after about 8-9 hours of trying to get into fastboot on the 3 different pcs in my household, all had the drivers at some point and i've worked with them and fastboot and this same phone previously, so I figured they'd still work. They didn't, I couldnot even get SUS to work. So i went to a 4th PC, installed SUS and the needed drivers and it only took like 40 minutes worth of tries. I'm in the software download part of the SUS, i'll keep this updated!
UPDATE2!:
So, it finished downloading but it suddenly disconnected, tried again for about 10 minutes and then got it going again. Downloaded the second time and installed it successfully. Leaving this up for future reference!
Bottomline: if you can't get into flashmode, try on as many PCs as you have available for at least 30 minutes each.
Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .
Th3Duck said:
Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.
Sorry locked boot loader didn't read it correctly don't use my advice .
Click to expand...
Click to collapse
No problem, it kinda sorted itself out by brute force connections :> Dammed sony, locking the bootloaders for real. I even got the sim unlock code from my phone company and it's still not bootloader unlockable at the phone settings, even though i can now get any sim i want in it -.-

[Q] HELP needed!! Phone possibly bricked!!

Hi Guys,
I was trying to update my Z1(C903) to Lollipop, but weirdly I wasn't able to boot into my recovery to install the pre-rooted rom. Every time i tried to enter into recovery, the phone would just vibrate and then proceed to boot the OS(I have dual recovery installed). I tried to reinstall the recovery but to no avail so I tried to flash stock FTF (14.4.A.0.157) but the process was struck at "flashing data" for a long time and I idiotically unplugged the phone after couple of hours!! And now my phone boots and i see the sony logo and next screen says "Software update failed. Connect your phone to computer and try again" And I'm unable to flash any FTF and the process still gets stuck at "flashing data".
Help me out guys as I badly need my phone for work!! Thank you!
akash 13 said:
Hi Guys,
I was trying to update my Z1(C903) to Lollipop, but weirdly I wasn't able to boot into my recovery to install the pre-rooted rom. Every time i tried to enter into recovery, the phone would just vibrate and then proceed to boot the OS(I have dual recovery installed). I tried to reinstall the recovery but to no avail so I tried to flash stock FTF (14.4.A.0.157) but the process was struck at "flashing data" for a long time and I idiotically unplugged the phone after couple of hours!! And now my phone boots and i see the sony logo and next screen says "Software update failed. Connect your phone to computer and try again" And I'm unable to flash any FTF and the process still gets stuck at "flashing data".
Help me out guys as I badly need my phone for work!! Thank you!
Click to expand...
Click to collapse
Looks like bad usb cable also check drivers and install latest flashtool and disable antivirus software if still problem appears try another pc...
kathanpatel1001 said:
Looks like bad usb cable also check drivers and install latest flashtool and disable antivirus software if still problem appears try another pc...
Click to expand...
Click to collapse
thanks dude...but that explains why i'm unable to flash a FTF! But I'm still perplexed why I can't enter recovery!!
akash 13 said:
thanks dude...but that explains why i'm unable to flash a FTF! But I'm still perplexed why I can't enter recovery!!
Click to expand...
Click to collapse
you definitely can't enter recovery now, cause that partition would have been wiped now. try flashing again.

[Q] E: Cannot be found when factory resetting

Hi all,
I really need your guys help. Out of nowhere today my phone restarted and then got stuck in a bootloop. When I went into recovery, it gave me the "android is updating" pop-up. I knew there was no update and within 20 seconds or so it said "no command". I went through to wipe the cache, and after rebooting it back up, strangely it didn't give me the "android is updating" screen that occurs after wiping cache. I went ahead and tried to factory reset through recovery and everything was fine until I got a msg "E: could not mount (file or directory could not be found) or something a long those lines. I'm assuming the EFS is fried? I rebooted it after and even at the "Welcome Screen" it started boot looping again. I'm stock lollipop unrooted. I never rooted this phone or flashed any ROMs. I called T-Mo and they will send me a replacement but I still want to see if this can be fixed. I also don't have a replacement phone so..there's that. Would anyone be able to help?
Edit: The only thing I haven't tried is flashing the stock firmware via odin. Would this trip the knox counter though? I really want to avoid that especially since I am having these issues and I don't want tmo/samsung to think I caused this issue.
Bad phone. Ur new phone will be good to go.
BAD ASS NOTE 4

[Q] Stuck in bootloop, cant access recovery

Post in wrong section, its 1st gen. Please move
So recently I decided to unlock my bootloader and flash CM12 on my Moto G 1st gen
Everything went fine till a friend told me to download and install Xposed. As I launched the app and hit frame work it mentioned creating a backup before installing so I did using TWRP. From there I rebooted the phone and thats where I ran into problems, it started to bootloop. After many hours (3 days to be exact) I still cant get it out of this state.
I thought I fixed it by reflashing, but apparently it just flashed it onto a seperate partition and the new ROM didnt work well (Notification bar didnt pull down right, no home button or multi-task). Since it didnt work I tried to wipe it and reflash but that apparently wouldnt boot, then I lost the ability to access recovery.
ADB doesnt find the device, I think usb debugging got disabled at some point.
I need some help on how to unbrick this, I'm 4 days in and still out of luck. Please!
Nobody?
You can´t access the recovery at all? When i get into a bootloop i need to do a little trick to enter recovery; hold down the power button for several seconds until it reboot, then as soon as the screen turns black hold the power button and volume down for 5 seconds to enter into bootloader. Then enter recovery from the bootloader, do a full wipe and install a stable rom. If you can´t connect the phone to the pc, take the sd card out and put it on another phone so you can connect it to a pc to transfer a stable rom for flashing on your phone.
Sorry this is late, completely forgot I post this. I can now get into recovery although some features dont work as the phone has nothing else on it. Got a USB OTG cable today and going to try mount cm12 that way.
Update : Using TWRP mount I now have files on the device (Data, boot, sys, system) which I didnt have before. Although I'm now getting a E:unable to mount '/system' but TWRP says Successful. Any thoughts?
Update 2 : Flashed it another 2 times, that seemed to fix it. Now no SIM detected.

Categories

Resources