Phone dead after update flashing. - Sony Xperia L

I had LineageOS 14.1 ROM installed using TWRP recovery in Xperia L. A new update came through and installed it using TWRP recovery. Successfully installed with a message and just after pressing reboot, the phone went dead. The phone just gives a boot vibration nothing else. No SONY logo, no backlight, nothing. On connecting it to charging or laptop, it turns on red LED. On disconnecting the phone, the red LED remains turned ON till battery remove.Has the phone bricked? Please, any suggestions to help the phone boot up?
EDIT: It was a kernel problem. Flashed new kernel using flashtool in fastboot mode. Surprisingly, fastboot mode didn't worked before lol. Sorry for inconvenience. Remove this.

I don't think that it is bricked. Try to boot into fastboot mode and then into recovery and do a full wipe. Try another rom or reflash lineage 14.1

Related

bricked while flashing recovery

my phone is running cyanogenmod snapshot m9
yesterday i tried to flash the new twrp recovery with flashify.
an error must have occured because after restarting i am stuck.
the phone wont boot it just goes directly to odin mode.
at the top of the screen in red writing it says "Could not do normal boot"
my laptop wont recognize anything being pluged into the usb
when i plug the phone in with no battery the red light turns on for a few seconds then goes out
not sure what else to try
thanks for any help
Looks like me and you caught the same bug.
You make any progress? I too atempted to flash TWRP 2.8, I used terminal emulator. Caused hard brick however I used the sdcard bricked boot and I can now get it to boot to ODIN. But every attempt to flash to stock or flash a new boot-loader, fails

Xperia Z5 Recovery (TWRP) problem.

Hello, i seem to have an issue with my Xperia Z5
I will begin from the start.
So earlier today i flashed the @infected_ AOSP Android N build. Flashing was good, all went well.
But then, when i booted up the device, my LED for the recovery did not blink at all. I tried pressing Vol Up rapidly, yet to no avail.
So i was stuck on N for a while and then decided to go back to stock using Flashtool. I installed the Nordic firmware and all went well. So now i am on stock.
Then, i went to fastboot mode and flashed the TWRP recovery from infected. It is version 3.0.2.0. I have however, the same problem. The LED does not blink, and when i want to boot into TWRP using fastboot, it stays at the SONY splash. My computer gives me a error message, that the device could not be recognized.
Any help is greatly appreciated, i just hope that i didn't fry my recovery partition.
EDIT1: Tried CM Recovery, problem persists.
EDIT2: Will try Androplus kernel and Androplus boot.img, will see if i get different results.
Thanks,
-Aero
Well.
Got the recovery working using AndroPlus. Problem is solved, if anyone could close the thread, that would be greatly appreciated.
-Aero

bootloader disabled

Hi all, recently i've flashed Nitrogen rom with kernel, but i was flashed the wrong kernel. 2202, mine is 2203. The phone is rebooted but no screen just it's screen on. After reflash the right kernel, 2203, everything got to normal but my bootloader is missing. Can't access to him. I try everything, reboot mode in bootloader, vol - power. The phone boot but by pass the bootloader and goes directly to system. I tried resolving issue with Sony companion but an error when he told me to reboot with vol- power, it's booted directly to system after few second.
Someone can help me ? Please.
Thks
Try with Emma (Sony flashtool) insted of Sony companion or use Flashtool by androxyde (community flashtool) and flash .ftf file.
Thks i'll try it.
Doesnt work. The will boot directly to system.
Help please !
Do you use correct combo? Does volume keys work?
Yes the correct combo vol down and usb. Reboot via system to bootloader the same. The phone stay few second to screen off with Led orange and boot to system. But boot to team recovery works perfect, blue Led and i'm in....

OPO Bricked & Stuck on TWRP

Hi guys,
I have a OPO bricked in a very weird way... It's booting straight to TWRP (v3.0.2-0) and nothing else. It is impossible to boot into bootloader (Vol. Up + Power), it still goes to TWRP. And when it is plugged on a computer, it's also booting straight to TWRP...
First a little recap :
- The OPO has (had) an unlocked bootloader and was updated from COS13 to Oxygen OS a while ago.
- The screen was smashed, touch screen not working anymore, and I had it replaced
- Then this problem occured (before screen change, it was booting to Android without a problem)
What I tried :
- Tried to reboot into bootloader, from TWRP via the reboot menu, nope.
- Tried to reboot into bootloader, from TWRP with "adb reboot bootloader", nope.
- Hard Reset from TWRP, nothing.
- Flash latest COS from TWRP (cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip) found here, nothing.
- I wanted to try this last chance unbrick "OnePlus Recovery Tool", but for that the OPO has to be OFF while plugged on a computer, and mine automatically boots on TWRP when plugged , so it's not bricked enough to use it, f***!
Since I can't access the bootlader, I can't do a proper clean/flash
I'm really out of ideas here. I'm starting to think that the problem isn't software but hardware...
Has anyone ever encountered such a brick, or has another idea?
Thanks in advance for your help.
fully shutdown your device and then press the volume up while connecting your phone to pc and see if it can boot into fastboot or not...
just.befa said:
Hi guys,
I have a OPO bricked in a very weird way... It's booting straight to TWRP (v3.0.2-0) and nothing else. It is impossible to boot into bootloader (Vol. Up + Power), it still goes to TWRP. And when it is plugged on a computer, it's also booting straight to TWRP...
First a little recap :
- The OPO has (had) an unlocked bootloader and was updated from COS13 to Oxygen OS a while ago.
- The screen was smashed, touch screen not working anymore, and I had it replaced
- Then this problem occured (before screen change, it was booting to Android without a problem)
What I tried :
- Tried to reboot into bootloader, from TWRP via the reboot menu, nope.
- Tried to reboot into bootloader, from TWRP with "adb reboot bootloader", nope.
- Hard Reset from TWRP, nothing.
- Flash latest COS from TWRP (cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip) found here, nothing.
- I wanted to try this last chance unbrick "OnePlus Recovery Tool", but for that the OPO has to be OFF while plugged on a computer, and mine automatically boots on TWRP when plugged , so it's not bricked enough to use it, f***!
Since I can't access the bootlader, I can't do a proper clean/flash
I'm really out of ideas here. I'm starting to think that the problem isn't software but hardware...
Has anyone ever encountered such a brick, or has another idea?
Thanks in advance for your help.
Click to expand...
Click to collapse
Open the back panel of your device and clean it properly with isopropyl alcohol and microfiber cloth.Also clean the power and volume buttons strips.
Reattach it correctly and then try booting into system or fastboot.
Thank you guys for your help.
So, what happened is that the volume buttons connector was dead, and that the volume down signal was "permanent", that is why the device was systematically booting in recovery mode, no matter what I tried.
Replacing it worked just fine

Phone is not power up?

I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
sanrajbhar said:
I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
Click to expand...
Click to collapse
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
xMotoDA said:
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
Click to expand...
Click to collapse
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
sanrajbhar said:
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
Click to expand...
Click to collapse
I have a similar issue, as my phone also cannot turn on and I have TWRP recovery.
I had rooted my phone with SuperSU and unlocked the bootloader via motorola's tool. But then due to SafetyNet, apps such as Snapchat wouldn't work (cant log in), and I couldn't download Netflix (totally a huge issue).
So I decided to try switching to Magisk instead, as I heard that uses systemless root that doesnt trip Safety Net. While uninstalling SuperSU (using the built in feature for full removal), I was able to uninstall SuperSU and unroot my phone, but was not able to restore the stock boot image in the process. It was at this point I made a NANdroid backup in case I stuffed anything up.
Because of this, I was unable to flash Magisk via the TWRP recovery, so I downloaded a previous version of the firmware from January to flash back to from here. After flashing this and also wiping the user data, my phone booted up fine and worked, and appeared to be in normal condition.
However, then I elected to download and install the firmware update. This all went well, and was installing, until just at the end of the process, when the phone turned off. It had over 60% battery at the time.
At this point in time I'm still unable to get it to boot up, even into recovery or fastboot mode, so I cant really do anything, or restore my NANdroid backup.
If I plug it into my laptop, and hold the power + volume button down for a period of time, I can hear the USB connected tone (Windows 10), which then switches to a disconnected tone and a "USB device malfunctioned" error message pops up.
I tried leaving it unplugged all of last night just in case it was stuck in a boot loop or something so the screen couldn't display anything, in order to flatten the battery, but obviously I couldn't tell any difference. I'm currently now trying to have it plugged into power for an extended period of time just in case it is actually just flat. The current condition is just a black screen as if there was no power at all, with no lights or anything, regardless of a charger being connected, with the buttons not doing anything (I've attempted holding down the power and volume down buttons together for at least 2 minutes to no effect)
Any help would be greatly appreciated.
My specs: Moto G Turbo (2015), model XT1557, running Android 6.0.1. Can't remember exactly, but it previously had the latest firmware available before I tried flashing the January firmware.

Categories

Resources