Question Bricked - Sony Xperia 5 III

Have a XQ-BC62, was working fine until it randomly died, and it won't respond to anything.
I was rebooting into fastboot, and hit the option to reboot to bootloader accidentally but then a red light started blinking when my phone was connected to my laptop.
Soft-reseting doesn't work at all, and the phone doesn't respond to any inputs at all, only a red light when charging. Unplugging turns off the red light, but nothing else happens.
My bootloader is unlocked, I have root with Magisk, and I've tried several different cables and chargers only to get the same red light.
Is there any fix to this?

Hi,
any solutions? am also facing a similar issue. mine is not responding to anything, no led lights, the screen is black, no response on any keypress, no charging indications. it's completely black.
plz do help me out if you know anything that is helpful

I haven't found a direct solution, but I am trying to discharge the battery and see if it could fix something.

Update: Still haven't found a proper fix, tried everything from the 2 minute restart to the old rubber band trick used on older Xperia's. If there is another possible fix, someone let me know, otherwise I'm just going to let the battery die in a drawer for a week and see if that works. If it doesn't, I'll just call Sony.

subiesubiesubie said:
Update: Still haven't found a proper fix, tried everything from the 2 minute restart to the old rubber band trick used on older Xperia's. If there is another possible fix, someone let me know, otherwise I'm just going to let the battery die in a drawer for a week and see if that works. If it doesn't, I'll just call Sony.
Click to expand...
Click to collapse
This exact same issue happened to me, flashing red light no matter what, no response to key presses etc. Taking apart the phone and manually disconnecting the battery did nothing, and I had to send my device in.

subiesubiesubie said:
Have a XQ-BC62, was working fine until it randomly died, and it won't respond to anything.
I was rebooting into fastboot, and hit the option to reboot to bootloader accidentally but then a red light started blinking when my phone was connected to my laptop.
Soft-reseting doesn't work at all, and the phone doesn't respond to any inputs at all, only a red light when charging. Unplugging turns off the red light, but nothing else happens.
My bootloader is unlocked, I have root with Magisk, and I've tried several different cables and chargers only to get the same red light.
Is there any fix to this?
Click to expand...
Click to collapse
Install Xperia Companion, and try the Software Repair tool. It worked for my XQ-BQ72, but my issue was wrong firmware flashed and wouldn't boot up.

Ko2nutJuz said:
Install Xperia Companion, and try the Software Repair tool. It worked for my XQ-BQ72, but my issue was wrong firmware flashed and wouldn't boot up.
Click to expand...
Click to collapse
I have the same problem. I have a XQ-BQ72, and I messed something up while installing firmware via Newflasher. (I tried to go back to Android 11)
Now I'm stuck in the "Your device is corrupted" loop and cannot solve it.
- Xperia Companion just says my device is locked, and will not do anything.
- I tried several times to flash a new firmware using Newflasher, and it runs through fine, but I'm still stuck in the boot loop.
Any ideas what else to try?
Edit:
Okay, after reading deeper in the Newflasher thread, I realized that the error is due to "rollback protection", because I wanted to install a newer version over an older version.
However, I'm still stuck, because even when flashing the newest version of the firmware (61.1.A.7.35), the problem remains.
Or could it be that it is a problem of the region customization? Does it matter which version of the XQ-BQ72 firmware I install?
Edit 2:
So it turns out I had the wrong drivers for fastboot. With that solved I could unlock the bootloader via fastboot and then use Xperia Companion to do a software repair.
And after that I was able to start over, use Newflasher to flash the old Android 11 version, lock the bootloader via fastboot and finally got what I wanted. Puh!

Related

Bricked Xperia Z3v with locked bootloader, can't enter recovery or flash mode

Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.

Bricked Xperia Z3v with locked bootloader, can't enter recovery or flash mode

Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Same thing here. Flashed wrong ROM via TWRP.
As a result, immediate loop (repetitive vibration, led blinking red) when connected via USB. No recovery access. Only fastboot access (blue led).
Locked bootloader.
Flashtool:
- tried flashing kernel.sin extracted from a stock ftf - no good (locked bootloader, unlocking requires flashboot which is not accessible).
- tried flashing system.sin extracted from a stock ftf - no good, flashtool says
INFO - Flashing selected system
and immediately after that
INFO - Please check the log before rebooting into system
So it clearly doesn't do anything. Any other approaches to try?
Tech core said:
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
Click to expand...
Click to collapse
Flashmode does not work, it starts cycling immediately.
Tech core said:
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
Click to expand...
Click to collapse
Yes, certainly.
Tech core said:
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or at least take a rest for what the heck is going on with your phone
Click to expand...
Click to collapse
Can't flash anything, so can't try it.
Tech core said:
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Click to expand...
Click to collapse
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
TheControlled said:
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
Click to expand...
Click to collapse
I didnt get your comment brief it to me

Xperia Ion won't turn on

My Sony Xperia Ion won't turn on any more. I am getting a blanks screen, no LED, nothing.
I wanted to change my phone's hostname. To do that I edited the "build.prop" file as mentioned in a guide and added it. After that my phone got stuck in a boot loop. It got to the Sony logo and then rebooted again and again.
I tried flashing the stock firmware with Flashtool, but it's giving me just an error, with no error messages.
I had to do the "hard reset" (holding volume up and power until it vibrated 3 times) to turn it off to get into flashmode.
Now I don't know what happened, but the phone stopped turning on at all. The screen is just blank, no LEDs, not even when I connect it to the charger.
I followed the [GUIDE] Recover 2012 and newer XPERIAs from SOFT-brick thread and now I'm at this point. I would have asked in it for help, but I can't post there yet.
So, my question is: does anyone have any suggestions? My last hope is waiting to see if the battery will drain in a couple of days and I can get the red LED again, to try and flash the stock image (or kernel if I figure out how to get just the kernel) back. But will that work, because I didn't have luck flashing the stock image even before?
EDIT: the guides mention draining my phone's battery. How can I do that if it's unresponsive? Some posts suggest leaving it connected to a charger for a few days. How can it drain the battery if it's connected to a charger? I guess I have nothing to lose, but can someone confirm that this will indeed help me drain the battery and get a LED signal back?
Thanks in advance
Basically the very thing that ****ed up my S years ago.
I still have to understand why the hate between normal notepads and build.prop.
EDIT: an idea
Anyway, the tip is: hard shutdown the phone as soon as possible (i.e. until you feel the 3 vibration)
This way you won't waste your precious battery juice needed for reparations (and require to externally recharge battery like I had to do)
Now, if you have unlocked BL.. I guess it's easier to recover and all with fastboot, but you can do it wirh flashtool too.
The problem now is just that its latest version is bugged. You'd have to use 0.9.18.6 or older.
Thanks for the suggestion.
The problem now is just that its latest version is bugged. You'd have to use 0.9.18.6 or older.
Click to expand...
Click to collapse
Totally bugged or? Because I successfully used the latest version to flash the stock firmware recently. Do you mean I won't be able to use the latest version now specifically because of this or?
I took up the advice from the other thread and put it to charge. Now I have a solid red LED again and I guess I can follow the thread. I'm only worried about screwing it up now by using the latest version of Flashtool.
I managed to get a red LED again. I also managed to get it into flashmode, but the phone runs out of battery before the whole FTF file can be flashed (always stops at same percentage). I charged the phone all night long.
Fastboot mode seems to work fine.
Is there a way for me to flash the whole stock firmware in fastboot mode? I have the FTF file, which contains a bunch of SIN files when I unpack it.
EDIT:
I fixed it. Details can be found in the general thread about recovering Sony Xperia phones.

Worst case scenario ****up, need help badly :(

After 8 years of tinkering with Android phones I have no clue how this happened.
PIXEL 2 (Walleye, non-xl)
Tried getting TWRP and ElementalX working but either one or both weren't doing there thing, though I could at least boot and use my phone normally. Finally ended in a situation where I couldn't boot passed fastboot with an error at the bottom "ERROR: LoadImageAndAuth Failed: Load Error". Found a fix that said to change the active partition. Set it to b and that worked and surprise it loads TWRP...so somehow TWRP was installed, but I can't actually load Android.
Grabbed the latest factory image and manually flashed all the files in the zip-within-the-zip. Everything flashed with no hiccups so I rebooted to bootloader with the intention to then reboot the system, and now this is happening:
TLDR Phone won't turn on. Holding PWR+VolDown SEEMS to do nothing, but it actually flashes a line on the screen like it's trying to load something for a milisecond, then does nothing. Holding PWR+VolUp does nothing. Holding PWR+VolUp+VolDown does the same screen flash followed by the notification LED blinking red 2 or 3 times. Please help!
EDIT: if it matters, the phone is about 50% battery and currently still on judging purely by the fact that it's been warm for about an hour.
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices? If it shows in devices, can you run platform-tools and see if it shows up via fastboot devices with an ID? If you can connect to fastboot, you could attempt to flash images that way.
djer34 said:
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices?
Click to expand...
Click to collapse
Nothing happens if I plug into the computer, no sound and not listed in devices. Plugging it in to the charger does nothing except possibly charges it, but I wouldn't know because the screen doesn't seem to be able to turn on for more than a milisecond of a flash.
I had this same problem when I flashed Elemental X kernel over top of the flash kernel and all I did was use the flash-all script that is included with the system image from google. This got me back to my OS where I flashed elemental and magisk. Do you have insurance through your provider?

XZP G8142 Bootloop

Hi, so yesterday my phone went into bootloop. I believe it happened while the phone was on low battery and I put it in stamina mode (which I never do otherwise) and maybe there was an update waiting, not sure.
Regardless, it was in bootloop, I did some digging and got flashtools, an older firmware, the usb drivers and after many hours I was able to flash it, not selecting any of the options under wipe. It didn't fix it, then I selected all options in wipe except userdata and ssd, didn't work. Then I gave up and tried the xperia companion's software repair, it didn't work, then I let the battery drain overnight and charged it a bit this morning, turned it on, still in bootloop.
Can anyone help me out here? I really did not want to upgrade in this round (xperia 1 is great but I'd rather wait for a premium or 2 version; plus release date isnt even known), and I really did not want to lose the data I had, but too late for that now.
I'm not super familiar with flashing and all that, but I believe it is bootlocked as Sony's emma tool says it is. I don't know what bootlocked is, I thought it meant locked to a carrier (which mine is not) but I guess it does not mean that.
Anyways, please help! I'm using my busted up z5 premium for now
fissure said:
Then I gave up and tried the xperia companion's software repair, it didn't work,
Click to expand...
Click to collapse
If your phone hasn't been bootloader unlocked then Xperia Companion will be your best route forward. When you say it doesn't work, what happens?
There are some instructions here
The phone needs to be turned off completely. Hold the power and volume up untill the phone vibrates three times.
Start Xpreia companion and follow the repair instructions. When it asks for you to connect the phone, plug the USB in whilst holding the volume up(+). Once the software has started you can let go.
If you are using Windows10 it might be a driver issue, as 10 fails to install drivers, but doesn't tell you. So start it in safe mode and look for 'driver signing disabled'
Thanks for replying!
When I say Xperia Companion doesn't work, I mean that I was able to successfully go through the repair option and am still in bootloop afterwards; it didn't resolve the problem.
fissure said:
Thanks for replying!
When I say Xperia Companion doesn't work, I mean that I was able to successfully go through the repair option and am still in bootloop afterwards; it didn't resolve the problem.
Click to expand...
Click to collapse
You're not describing what doesn't work. The phone doesn't boot at any point before you connect it to Xperia Companion, you put the phone into flash mode.
It doens't need to boot to get into flash mode. You just need to connect it to the PC with volume up pressed. If you can't get the phone to be recognised by Companion, you may be missing the drivers.
Try installing it with 'driver signing disabled'
Didgesteve said:
You're not describing what doesn't work. The phone doesn't boot at any point before you connect it to Xperia Companion, you put the phone into flash mode.
It doens't need to boot to get into flash mode. You just need to connect it to the PC with volume up pressed. If you can't get the phone to be recognised my Companion, you may be missing the drivers.
Try installing it with 'driver signing disabled'
Click to expand...
Click to collapse
Ok let me try to be more clear:
The phone is currently in a state that when it is turned on it boots to the Sony logo screen, stays there for about 25seconds, then restarts, repeat ad infinitum.
I am able to proceed with a software repair in Xperia Companion by selecting the device cannot connect then choosing the device type as a phone. I have connected the phone, while it is off, while pressing the volume key at the same time. Companion proceeds to repair the phone, took 10-25min. That process completes successfully within Companion. After which I disconnect my phone, turn it on, and I am still in a bootloop.
The point is, I have flashed through flashtool without problem resolution, I have repaired via Companion without resolution. Those steps were done correctly, but the bootloop persists. I'm looking for new suggestions to resolve the bootloop.
fissure said:
Ok let me try to be more clear:
The phone is currently in a state that when it is turned on it boots to the Sony logo screen, stays there for about 25seconds, then restarts, repeat ad infinitum.
I am able to proceed with a software repair in Xperia Companion by selecting the device cannot connect then choosing the device type as a phone. I have connected the phone, while it is off, while pressing the volume key at the same time. Companion proceeds to repair the phone, took 10-25min. That process completes successfully within Companion. After which I disconnect my phone, turn it on, and I am still in a bootloop.
The point is, I have flashed through flashtool without problem resolution, I have repaired via Companion without resolution. Those steps were done correctly, but the bootloop persists. I'm looking for new suggestions to resolve the bootloop.
Click to expand...
Click to collapse
Sorry, I didn't read your first post completely, my bad.
It sounds like a problem with the boot partition, but I don't understand how the Companion fails to spot it's broken as it usually wipes and re-wrties everything.
Try lettig the battery run out, so it's completely flat, won't start or power up, then charge it to 100% while turned off. Then try again.
I've never heard of Companion failing a repair on a bootlocked device before, so there'a chance it's a hardware issue.
I've tried charging it to full and using xperia companion, it still does not work.
One thing I don't think I mentioned is that when connecting the phone to the computer, xperia companion says the device is locked and it won't proceed with the repair. So I have to start Companion and choose the my device cannot be detected option and repair that way, which as I mentioned earlier does not resolve the bootloop issue.
Didgesteve said:
Sorry, I didn't read your first post completely, my bad.
It sounds like a problem with the boot partition, but I don't understand how the Companion fails to spot it's broken as it usually wipes and re-wrties everything.
Try lettig the battery run out, so it's completely flat, won't start or power up, then charge it to 100% while turned off. Then try again.
I've never heard of Companion failing a repair on a bootlocked device before, so there'a chance it's a hardware issue.
Click to expand...
Click to collapse
From what I know flashtool doesn't work and u need to use newflasher in order to flash properly. I tried flashtool one time for the xz premium and ended up not working till I used new flasher
Same problem after upgrade on low power and now bootlop. any variants?
I concur. Flash tool does not work for xz premium. You need to use new flasher. Do that and then see what happens and then we can go from there

Categories

Resources