Related
hello all!
my phone was working properly (rooted but not boot unlocked)
pc companion told me there were a new version availlable (.253) I accepted, install, reboot, everything was fine.
I tried to backup my data in order to change the sd card to a bigger one...then it told me there was a problem while backuping so I did a reboot
this is where the problem begins:
now I have a white triangle with a screwdriver in it and a blue bar below it with an animation inside and it's stuck there...what does it mean for a start?
can you please help?
I'd like to recover it in order to get back my data (photos and video I wanted to put on the new sd card)
tried flashtool but it doesn't recognise the phone...
note: before doing all that, free space was low on my XZ internal storage (like 300 megs)
dave_id said:
hello all!
my phone was working properly (rooted but not boot unlocked)
pc companion told me there were a new version availlable (.253) I accepted, install, reboot, everything was fine.
I tried to backup my data in order to change the sd card to a bigger one...then it told me there was a problem while backuping so I did a reboot
this is where the problem begins:
now I have a white triangle with a screwdriver in it and a blue bar below it with an animation inside and it's stuck there...what does it mean for a start?
can you please help?
I'd like to recover it in order to get back my data (photos and video I wanted to put on the new sd card)
tried flashtool but it doesn't recognise the phone...
note: before doing all that, free space was low on my XZ internal storage (like 300 megs)
Click to expand...
Click to collapse
Unplug your phone from the USB cable and then start, see if that helps
This is exactly what I've encountered, can't find much help in the web, re-flash with wipe cache no joy, in the end re-flash with wipe data boot normally, last backup was 4 days old, restore and lost 4 days game progress...
Sent from my C6603 using XDA Premium HD app
That's strange.
Also had the same.
I updated to the .253 ROM and firmware etc and everything working fine.
I then rebooted after removing some system apps and got this.
I left it for a while and still stuck there.
Pressed a few buttons and still nothing then it suddenly rebooted (not sure if related to pressing the buttons or not) and everything was fine.
Then when it booted up it did the NFC firmware update so maybe related to that.
Not had it since and rebooted a few times.
Phil
thanks for replying guys.
problem really is that I can't use flashtool, for some reason I can't go in flashboot mode (green led right?)
and in fact I don't know all the key pressing procedures (if someone can post them all)
...but I think I got the press down and connect right, problem is that I have the green led for less than one second and then nothing...
dave_id said:
thanks for replying guys.
problem really is that I can't use flashtool, for some reason I can't go in flashboot mode (green led right?)
and in fact I don't know all the key pressing procedures (if someone can post them all)
...but I think I got the press down and connect right, problem is that I have the green led for less than one second and then nothing...
Click to expand...
Click to collapse
Hi,
I also encountered this when I tried to use the old root method of .253. (yah, stupid of me but managed to salvage)
Just let it run for like 20 minutes or so and it will reboot subsequently. (As long as the progress bar still move, you should be ok)
Seems like a self-recovery process in place I guess.
yeah I guess you're right , but the first time was so long (more than 20 minutes ) so I thought it was dead...it is obviously some kind of self repair,
because now after a lot of reboots it suddenly started correctly after 5minutes of this blue bar moving....and now working? WTF?
things that I did in case it could help:
-used flashtool beta 4
-flashed a base .434 in blind mode (choosed xperia Z in the list)
-went into flashboot (press down and then plug usb) I had the green light for just a second...(I also installed EMMA drivers from sony , don't know if it helped)
-reboot then wait (I put it also on the docking bay , don't know if it helped as well but it made the blue bar go faster it seems, not sure tho...)
I used "hard boot" also : just jkeep pressing up and the power button until it vibrates 3 times.
maybe just puting it on the dock and then wait (quite some time) is enough (and makes sense)
I just had the same issue - WTF!!!
I just let it sit there for a while and it automatically started.
This is f*** crazy smart (stupid) phone.
DOn't know exactly what my wife did, but I doubt she flashed anything:laugh:
The battery died, she conncted to the charger, most probably with pushing some of the volume buttons and phone booted into Triange mode. Now it's stuk in this mode since an our.
I did Hard reset, but after phone is plug into wall charger it automatically boots in Triange mode.
This is in stock ROM without any modifications, unlocking, anything.
esselite said:
This is f*** crazy smart (stupid) phone.
DOn't know exactly what my wife did, but I doubt she flashed anything:laugh:
The battery died, she conncted to the charger, most probably with pushing some of the volume buttons and phone booted into Triange mode. Now it's stuk in this mode since an our.
I did Hard reset, but after phone is plug into wall charger it automatically boots in Triange mode.
This is in stock ROM without any modifications, unlocking, anything.
Click to expand...
Click to collapse
Just wait - sometimes it takes a while but it'll eventually boot up.
I think [NUT] said somewhere that this is a repair of certain permissions by the phone itself. I've only ever had this for some minutes - but it is possible if the battery an out it could invoke this. Shouldn't be anything to worry about.
And I think fastboot is blue led - you could try flashmode.
I tend to do lots and lots of flashing and mods so I've seen it several times. The first time caught me by surprise and lasted for a long time...now I'm just used to it ..
In my case waiting in triangle mode did not helped. Was waiting 5 hours at work. I flashed with flashtool again stock ROM without wiping data and still no response.
FInally flashed with wipe and phone is running but all data gone. What a crap.
Hi guys,
Device info:
Model C6603, Unlocked bootloader
So i have the following problem, my device is in a bootloop and i can't figure out what the exact issue is. I'm out of options at least.
First a little background on how it came to be: (scroll down for short overview)
Before official lolipop came out I've been on CM12.1 for a few months, cm-12-20141221-INFECTED-yuga to be exact. When official lolipop came out I installed C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB following the instructions, although i see the thread has been modified (name, updated etc.) the instructions are the same. I did not install Xposed yet, because i wanted to try stock+root first.
After a few weeks of normal use, i used google maps navigation. This worked fine but when i arrived at my destination and picked up my phone closed google maps app but then my phone crashed. It rebooted to the point where i had to enter my pincode, but every time i was entering my pin it crashed and after a few tries it dind't even got to the lock screen but only showed the sony logo and rebooted(bootloop). I noticed my device was getting hot and left it alone for a few minutes, after that i started my phone again and was able to use my phone again. Until I started google maps again for the way back and enabled gps it crashed again, the same thing happened the phone would reboot when entering my pin, the phone wasn't hot this time. I left the phone alone till i got home, put it on the charger and the next day my phone worked fine again.
A few days later i was outside in the sun whatsapping, when the same happened my phone crashed and rebooted when entering the pin or slightly after. The phone was feeling hot, also because it was exposed to the sun for a while, in TWRP recovery it showed temperatures around 70 degrees celsius (i don't know if this is too hot?). After i had left the device alone for a while and try to boot it up it got stuck in a bootloop (sony logo), after a night of charging it got to the point of entering the pin code again but crashed and got stuck in a bootloop again (sony logo). And since then i'm not able to get rid of this bootloop. However i could still get into recovery (TWRP).
First i tried to reinstall the rom, factory reset and flash via recovery: C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB
This worked, and the device booted up but after a while it crashed and got stuck in a bootloop again (sony logo).
So all summed up:
cm-12-20141221-INFECTED-yuga
>> C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB
>> Google maps navigation >> overheated >> bootloop (sony logo) >> charging night >> working >> whatsapping in bright sun >> overheating >> continuous bootloop (sony logo)
What i have tried:
- Tried booting without sim card, withoud sd but doesn't work
- Flash same rom via recovery C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB : Worked once, but then crashed and went back in bootloop, now when i flash this only Bootloop (sony logo)
- Flash updated version of http://forum.xda-developers.com/xperia-z/help/lollipop-5-0-2-10-6-0-454-pre-rooted-t3116205 via recovery : Bootloop (sony logo)
- Flash kernel via fastboot http://forum.xda-developers.com/xperia-z/development/kernel-unlocked-bootloaders-t3114234 : Only recovery works
- Flash stock kernel via fastboot: boot (sony logo) one time then turns off
- Flash stock lolipop (with and without bootloader unlocked) via latest Flashtool : Bootloop (sony logo)
- Flash stock lolipop via xperifirm (C6603_10.6.A.0.454_KPN Mobile NL) xperia (with and without bootloader unlocked) via latest Flashtool : Bootloop (sony logo)
- Flash stock kitkat (with and without bootloader unlocked) via Flashtool: Bootloop (sony logo)
- Relock bootloader and Sony PC companion restore latest firmware : Bootloop (sony logo)
- Restoring serveral backups from TRWP and Phillz touch but they all result in the same bootloop, while at the time the backups were made there were no problems.
I'm pretty much out of options and begin to thinking something was damaged when the device overheated or a bad partion of a kernel is still stuck in the devices kernel.
Does anyone had the same issue, if so how to fix it? Or another option i could try, maybe someone spotted anything i did wrong?
Current state:
Locked bootloader, stock lolipop 10.6.A.0.454 flashed via Sony PC Companion recovery
Boots into setup, after a few reboots I completed the setup. But still randomly reboots when trying to use some apps or in general leaving it in standby for a while (might be due instability).
Thanks in advantage,
Jonathan
So the only things that you do that do not result in a bootloop are flashing a kernel. Try flashing a Stock kernel with Flashtool --> open flashtool >choose the flash button at the top left > flashmode > choose the firmware > check cache and data above and below check Only Kernel. Post result here...
Good luck
Try flashing a Stock kernel with Flashtool --> open flashtool >choose the flash button at the top left > flashmode > choose the firmware > check cache and data above and below check Only Kernel.
Click to expand...
Click to collapse
Don't do this. It will wipe your data and flash everything but the kernel, therefore losing root etc.
If you want to flash a stock kernel, you must leave everything in the "Wipe" section unchecked, and check everything but "Kernel" in the "Exclude" section.
I don't think this will help anyway, being that you're already on a stock firmware flashed via Flashtool.
aaronkatrini said:
So the only things that you do that do not result in a bootloop are flashing a kernel. Try flashing a Stock kernel with Flashtool --> open flashtool >choose the flash button at the top left > flashmode > choose the firmware > check cache and data above and below check Only Kernel. Post result here...
Good luck
Click to expand...
Click to collapse
Thanks for your fast reply, I think you meant: check everything but leave kernel unchecked (as kingvortex replied at the time of writing)? Since it is an 'Exclude' list. I flashed stock kernel, it shows the Sony logo and then shuts down. I used stock lolipop kernel from 'C6603_10.6.A.0.454_KPN' Mobile NL, and i also tried 'C6603_10.6.A.0.454_Customized CE1'. both have the same result.
I've got the most "life" after i restored my phone with pc companion to 10.6.A.0.454. Then, after being charged via the wall charger for a while, it boots up normally and goes into setup, since it is a complete restore. But crashed around the setup screen for wifi. The other options i tried do not come any further than showing the Sony logo, this stock one shows Sony logo >> android logo >> boot animation + sound.
I'm thinking it might be a case of a dead battery or battery controller of some sort. Because the phone only boots up normally, with stock android .454, when the phone is connected to the wall charger. Whenever i pull out the cable the phone crashes and reboots, also when not connected to the charger it gets stuck in a bootloop. However when the phone is connected to a charger and working for a while it still randomly crashes when using the device, sometimes these moments are suspicious because it sometimes reboots when enabling gps, wifi, mobile data or when starting an app, phone call or synchronizing accounts for instance. On a side note sometimes the battery percentage drops about 6-9 percent when rebooted one time or when crashed, also when i connect my phone to the charger the status led is red but when done showing the sony logo and when charging it turns green (or yellow, depends on battery percentage). This is why i think something internal is not working properly whether it is the battery or the battery controller, i don't know.
I still find it weird that the phone was in perfect condition before flashing .454 stock lolipop, it might be due to overheating that some components where damaged. At least i'm guessing this is the case because i know no other reason why it would show such behavior. Is there someone who has experienced something like this or another solution i might try?
In the mean time i bought a Z3, my XZ is definitely dead now after the battery has discharged and i can't charge it because it's constantly rebooting. However flashmode and fastboot are still working. Thanks for the replies. I might repair my XZ if i can get my hands on a cheap (broken) second hand and replace the internals, but i'll see.
Hi, i have the same problem... i cant charge and the constantly rebooting... and in my case also... when i try to flash any ROM, flashtool and Fastboot are stuck for 1 hour when try to flash system.sin (system.img)
i stop flashing after 1 hour... not sure if could finish after 2 hours :/
Cant use PC Companion because dont have charge in the phone (locked bootloader)
Any suggestion?
Having gotten a spare Xperia SP, I decided to venture into the realm of flashing custom ROMs. This was the first time I did anything of this sort with an Android device. So, here is what I did to it today:
At first, I successfully rooted, installed recovery and flashed CM12. After fiddling with it for about an hour and not finding anything super exciting, I decided to try out other ROMs. I did a facotry reset, wiped the data and cache, and was about to flash CM11 (I forgot that it required an unlocked bootloader, which I don't have, and the recovery console told me so). Maybe at this point I should have just reflashed CM12, but I chose (not even sure why at this point) to exit recovery instead. After this, the phone keeps getting stuck on the Sony logo (although on the second attempt to turn it on, it did display a screen showing that wrench icon, indicating some sort of configuration activity going on, but never moved past that either). I tried flashing two different stock ftf roms with flashtool, both fail with this error: Processing of system.sin finished with errors. One of them will cause the phone to shut off after about a minute on the logo instead of remaining stuck on it indefinitely.
Maybe I should mention that this phone did not exactly work flawlessly for some time, even before I started experimenting with it. Here are the main things that I can remember it doing:
-Lags on even the basic functions, apps often crashing, despite doing a very recent hard reset.
-Battery drains very fast sometimes (like going from 55% to 0 in about 2 hours with almost no usage).
-A few months ago, it would periodically freeze and reboot itself, but that problem seemed to disappear with time.
Did I do something stupid to that phone, or are there internal/hardware problems that have manifested themselves in this way? I won't be horribly upset if I killed it (after all, knowing that something of this sort may happen was exactly the reason why I was not doing all this on my main phone), but I certainly would like to get it back up and running.
Download Flashtool v0.9.18.6 from official site.
Option 1: Flash stock.
or,
Option 2: Flash tangerine-7.1.elf via 'fastboot mode' to directly get TWRP, then flash any ROM you want.
https://dl.cubeserver.eu/TechnoSparks/tangerine-stuffs/tangerine-7.1.elf
nandan21 said:
Download Flashtool v0.9.18.6 from official site.
Option 1: Flash stock.
or,
Option 2: Flash tangerine-7.1.elf via 'fastboot mode' to directly get TWRP, then flash any ROM you want.
]
Click to expand...
Click to collapse
Thank you for your reply. I have a few questions:
I downloaded the flashtool version that you mentioned (from the official site), but avast detected malware in it. Should version 9.19.8, the one I tried yesterday, work fine?
What is exactly considered "stock rom"? Is it exclusively the version your phone came with, or is it firmware of any version/carrier branding, as longs as it is made for your phone model by the manufacuter?
It looks like my phone actually won't stay in flash mode. I select fastboot mode in flashtool, a window pops up asking me to plug in the phone. I press the volume down button and plug it in, the LED glows bright green, but nothing happens in flashtool. After a few seconds, the LED goes red and the Sony logo appears on the phones screen (as if it was going to turn on), and my computer makes a sound as if the phone was ejected. The phone shuts off a minute later, goes into flash mode again, and the cycle repeats.
UPDATE
Nevermind everything I wrote before, I was able to successfully re-flash stock. Turns out I did in fact have some crappy version of flashtool that didn't work, and I found anolder version without malware.
Strangely, the infected flashtool version was the one I dowloaded from the official site... Something is fishy here.
Anyways, thanks a bunch for your help!
MrDroid15 said:
Thank you for your reply. I have a few questions:
I downloaded the flashtool version that you mentioned (from the official site), but avast detected malware in it. Should version 9.19.8, the one I tried yesterday, work fine?
What is exactly considered "stock rom"? Is it exclusively the version your phone came with, or is it firmware of any version/carrier branding, as longs as it is made for your phone model by the manufacuter?
It looks like my phone actually won't stay in flash mode. I select fastboot mode in flashtool, a window pops up asking me to plug in the phone. I press the volume down button and plug it in, the LED glows bright green, but nothing happens in flashtool. After a few seconds, the LED goes red and the Sony logo appears on the phones screen (as if it was going to turn on), and my computer makes a sound as if the phone was ejected. The phone shuts off a minute later, goes into flash mode again, and the cycle repeats.
Click to expand...
Click to collapse
Use flashtool 0.9.19.8 because that is what everyone is recommending now, Stock rom defines as what it originally comes from your phone which is manufactured by sony. To get into fastboot mode turn off your phone by taking off the cover off your xperia sp and use a pin or pen to press into a small dot and you will get 3 vibrations.
This guide is not written by me, so give credit to chris10286
Step 1. Download a kernel with twrp embedded im sure I used dooms kernel as far as I remember. There are many others just do a simple google of xperia sp kernel with recovery.
Step 2 . take phone case off the back hold button in on lower bottom for 10 seconds you will get 3 vibrations . good leave it at that.
Step 4 . open flashtool let it load completely. Now plug USB into your phone also have it into your PC ! Whilst plugging in hold down volume button to enter flashmode your phone should be green . hold up for fast boot mode which is blue either too let's you flash a kernel but fast boot mode requires "elf" kernel.
Step 5. Locate kernel install and then boot phone up whilst press the volume up button as its booting recovery mode will be accessed now flash rom of your choice or use Sony PC suite to go back to stock. Make sure you have stock kernel and bootloader locked or else it won't let you..
Use this thread to help you since i had the similar problem which involved my phone: http://forum.xda-developers.com/showthread.php?p=63660062#post63660062
If none of my methods work please ask zenith to help you or ask anyone in the xperia sp forum to help you since im not a developer but ran into a similar problem to yours.
I hope this helps you out in someway as it did me good luck.
Thanks Nandan
Thank you, I very much appreciate that you took the time to write this long post to help me out. As I mentioned in an earlier post, I found a solution to my problem - by using flashtool 9.18.6 (the one that wasn't working was actually newer).
Warning: LONG POST incoming ***
So I think I'm having the worst brick I've ever encountered on this phone, had tons of softbricks before and I could almost always sort them out easily, this one I'm having right now unforetunately is not the same case.
Current situation, phone won't boot up, no logo, no nothing, pressing power on button gives two RED blinks, holding power on gives continuous red led blink, now, vol. Up + power wont work anymore, same as hard reset of vol up+pwr with 3vibrates, it does work a few days ago but not anymore (I'm thinking about the issue of hard reset that results in about 50+ hrs or battery draining and recovery but not so sure if thats the case right now).
I've tried going flashmode but it just wont remain in flashmode, I can enter on flashmode briefly, proceed to flash stock ftf then somewhre along the process, (system.sin i think) phone exits flashmode then red led will show up. Fastboot wont work either.
Last observation i have is during wall charging, initially, when I connect to charger, no led light will show for about 3sec, then GREEN led will show and blink around 5times in about 1min, led disappears for a few sec then straight RED led will show for about 2min, and the cycle goes on and on, been monitoring like this for about 3hrs now, will continue until tomorrow.
Note: worst case, I think battery is flat dead thats why it wont charge, or something got fried during usage, never flashed antything for a few months, last thing I remember is I'm having a series of reboots, during long hours of mobile hotspot. Also worth mentioning, this phone auto reboots when it overheats during charging.
This may be a long shot but if anyone miraculously knows a workaround here other than getting a new one, then that'd be a huge help.
That's all, Thanks!
hi
I'm having a similar problem on my Xperia TL (LT30at). It was running on android 4.1.2 and I tried to flash it with a 4.3 ROM (originally built for LT30p, customized for US). During the process, there was an error while the flashtool was processing system.sin. In my case, there's no LED indication, no vibration, no nothing. The phone just won't respond to any button press combo (the battery was about 80% charged).
Plz help.
RESTORED!
Update: After long hours of battling this bricked mode, I've finally restored my phone! Stock FTF won't go through flashmode no matter what I do but luckily "Fastboot Trick" did the work along with numerous Trial and Errors, basically I was able to access fastboot by following and READING all of the instructions on xperia recovery pages here on XDA, from charging cycles, battery disconnect via opening the phone, flashmode/fastboot access, rubber band trick and so on.
Tried flashing kernel.sin from stock FTF (got into boot logo/bootloops with this), system.sin (can't fastboot flash due to huge file size), and lastly using my current roms (CM12.1 by neo) boot.img and flashing it via flashtool fastboot.this one did the trick allowing me to use my previous kernel along with my still un-wiped ROM data resulting to booting into it's previous working state.
Credits to @gregbradley , @Toledo_JAB and all that contributed to their tools and recovery thread (link below)
ALL IN ONE THREAD[Updated 12/3/13]Read me first!
[GUIDE] Recover 2012 and newer XPERIAs from SOFT-brick
The Key is as long as you're getting a response(if you don't get any, wall charge your phone for 4 ~ 24 hours and see if you can get a red led which then means you can still save your phone), vibrate, led blink, then you can bet you can still recover your phone. You just have to try everything you haven't tried before. That's all!
I had my T also similarly "bricked" last summer. Flashing always resulted in errors. Rubber band while powering helped, but only worked with original Sony charger. No luck with a Samsung one. After several reboots flashing went ok. The phone was stable only with battery almost full. After I replaced the battery, everything works well again. I guess the battery has been damaged by different chargers - a Samsung 2A (for tablet), in-car, and external battery pack. Currently evaluating CM 12.1
LiudasP said:
I had my T also similarly "bricked" last summer. Flashing always resulted in errors. Rubber band while powering helped, but only worked with original Sony charger. No luck with a Samsung one. After several reboots flashing went ok. The phone was stable only with battery almost full. After I replaced the battery, everything works well again. I guess the battery has been damaged by different chargers - a Samsung 2A (for tablet), in-car, and external battery pack. Currently evaluating CM 12.1
Click to expand...
Click to collapse
Good thing replacing battery works for you, though I have recovered my phone, I think mines hotspot module got damaged already due to extensive usage and overheating from before (currently experiencing random reboots right now when data is on), gonna check to see if this is kernel or hardware related.
PS: WhiteNeo's NeoWave(KK) and CM12.1 ROM's(development stopped / best version though is 20151010 afaik) are the fastest I have tested yet. You should check them both .
Xperia TL (LT30at) Hard Bricked!!
Well, it’s pretty much obvious that I have hard bricked my phone.
I’ve been searching over the internet (especially on XDA) about this issue and I’ve realized that I’ve caused my phone’s bootloader to be damaged and that’s why it won’t boot at all. Before unlocking the bootloader, I did not make a TA backup (as I’ve seen in some posts that it is required to restore security units in case of boot failure) and now I don’t know how to fix my phone. Most likely, I need a suitable firmware for my phone to flash it with and hence to restore bootloader, but I haven’t found a firmware for my phone anywhere over the internet.
By the way, my phone is recognized as ZEUS flash device when I connect it to my pc, so I feel like there is a chance to recover it from this brick. I took it to a repair center, they tried JTAG but the guy said it didn’t work. The phone takes the dump but still doesn’t boot.
Could anyone help please?
kain_the_sly said:
Well, it’s pretty much obvious that I have hard bricked my phone.
I’ve been searching over the internet (especially on XDA) about this issue and I’ve realized that I’ve caused my phone’s bootloader to be damaged and that’s why it won’t boot at all. Before unlocking the bootloader, I did not make a TA backup (as I’ve seen in some posts that it is required to restore security units in case of boot failure) and now I don’t know how to fix my phone. Most likely, I need a suitable firmware for my phone to flash it with and hence to restore bootloader, but I haven’t found a firmware for my phone anywhere over the internet.
By the way, my phone is recognized as ZEUS flash device when I connect it to my pc, so I feel like there is a chance to recover it from this brick. I took it to a repair center, they tried JTAG but the guy said it didn’t work. The phone takes the dump but still doesn’t boot.
Could anyone help please?
Click to expand...
Click to collapse
Not that sure when it comes to bootloader errors but I'll try to help, if it's detected on your PC, then you might still be able to recover it (mine is not even detected on my PC the last time it got bricked, but I got it fixed(detected) with proper driver installation: [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318] by @DooMLoRD), check troubleshooting section if you are using Windows 8 as you might encounter driver signature error during installation .
Question: Does it respond to any action? eg, vibrate, pressing power button just once(if it blinks red LED twice = phone is still alive), soft reset & hard reset, wall charging, fastboot or flashmode when connected to PC?
zakcaree said:
Not that sure when it comes to bootloader errors but I'll try to help, if it's detected on your PC, then you might still be able to recover it (mine is not even detected on my PC the last time it got bricked, but I got it fixed(detected) with proper driver installation: [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318] by @DooMLoRD), check troubleshooting section if you are using Windows 8 as you might encounter driver signature error during installation .
Question: Does it respond to any action? eg, vibrate, pressing power button just once(if it blinks red LED twice = phone is still alive), soft reset & hard reset, wall charging, fastboot or flashmode when connected to PC?
Click to expand...
Click to collapse
No. It doesn't vibrate, no LED blink, no fastboot or flashmode. The phone is non-responsive to every button press. However, red LED blinks just for once when I connect it to my pc and when the battery is unplugged.
So far, I've a pretty sure idea that the phone is in "dead boot" and somehow I've to restore its security units / TA backup, as the boot partition is corrupted. Unfortunately, I don't have a TA backup. However, I could make use of TA backup from another working LT30at.
P.S. I'm using Windows 7 and there are no driver issues. The phone is recognized by my pc as an ZEUS flash device.
zakcaree said:
Good thing replacing battery works for you, though I have recovered my phone, I think mines hotspot module got damaged already due to extensive usage and overheating from before (currently experiencing random reboots right now when data is on), gonna check to see if this is kernel or hardware related.
PS: WhiteNeo's NeoWave(KK) and CM12.1 ROM's(development stopped / best version though is 20151010 afaik) are the fastest I have tested yet. You should check them both .
Click to expand...
Click to collapse
Hi guys.
I have the same problem i tierd flashing the rom stock..it does't work..flash aborted and phone disconnected avain and again.
But when i remove the battery..phone in wallcharger it shows sony logo and keep restarting..no blinking led no vibration.
Any idea???
Mizouradio said:
Hi guys.
I have the same problem i tierd flashing the rom stock..it does't work..flash aborted and phone disconnected avain and again.
But when i remove the battery..phone in wallcharger it shows sony logo and keep restarting..no blinking led no vibration.
Any idea???
Click to expand...
Click to collapse
Try install stock without battery and then plug it in when u start
alial04 said:
Try install stock without battery and then plug it in when u start
Click to expand...
Click to collapse
Yes i did that...still have the same pb...end of flash session..phone keep disconnecting..and flash aborted!!!
Any advice?
Mizouradio said:
Hi guys.
I have the same problem i tierd flashing the rom stock..it does't work..flash aborted and phone disconnected avain and again.
But when i remove the battery..phone in wallcharger it shows sony logo and keep restarting..no blinking led no vibration.
Any idea???
Click to expand...
Click to collapse
Bootloop usually means boot kernel problem, Can you fastboot? try to fastboot flash your previous ROM kernel and check to see if you can boot normally to your previous rom.
im not using an xperia tl but pretty much thw same issue with my xperia e3 d2212
red light keeps blinking its charging(no logo just saying) tried evry key combination triying to connect to pc says connected for a few secs n then it gets disconnected although i say that its connected im sayin it only based on the sound derz actually no new software or unknown software msgs popping plzzz help me out............ ty in advance
Sunderesh said:
im not using an xperia tl but pretty much thw same issue with my xperia e3 d2212
red light keeps blinking its charging(no logo just saying) tried evry key combination triying to connect to pc says connected for a few secs n then it gets disconnected although i say that its connected im sayin it only based on the sound derz actually no new software or unknown software msgs popping plzzz help me out............ ty in advance
Click to expand...
Click to collapse
You mean red LED blinks during charging? Did you flash anything before this occured? Try first charging it for 2~4hrs, (also check if red LED still flashes during charging after a couple of hours), then try powering it ON... does it boot? If not, try soft reset with your phone (hold vol-up + power button for a few sec), it will vibrate ONCE, that means soft reset, power it ON... does it boot? If not, try hard reset this time (same method as soft-reset, this time hold the buttons longer, you will first get 1 vibrate, just hold it still, then you wil get 3 vibrates = hard reset).. power it ON... does it boot? If not.. try charging it a little longer and repeat the process, see if you can get it to boot that way.
zakcaree said:
You mean red LED blinks during charging? Did you flash anything before this occured? Try first charging it for 2~4hrs, (also check if red LED still flashes during charging after a couple of hours), then try powering it ON... does it boot? If not, try soft reset with your phone (hold vol-up + power button for a few sec), it will vibrate ONCE, that means soft reset, power it ON... does it boot? If not, try hard reset this time (same method as soft-reset, this time hold the buttons longer, you will first get 1 vibrate, just hold it still, then you wil get 3 vibrates = hard reset).. power it ON... does it boot? If not.. try charging it a little longer and repeat the process, see if you can get it to boot that way.
Click to expand...
Click to collapse
I will tell u my problem in detail I have a Sony Xperia e3 d2212 running stock 4.4.2 I rooted it without unlocking bootloader with" kingoroot" later saw a few privacy issues with kingo super user and used "supersume pro" to get super su as superuser and to get rid of kingosuper user
then tried an boot loader unlock with an app named "ez unlock" then tried flashing cwm
the mistake I did was that I flashed the cwm file which was made for my phone running 4.4.4
and now if it is low on battery the red led blinks only when I hold the power button
if I put it on charge for a few hours and then unplug the charger the red led keeps blinking all day long
let me know if u understood
sorry for the confusion though
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
thank you for ur interest bro.......
zakcaree said:
Bootloop usually means boot kernel problem, Can you fastboot? try to fastboot flash your previous ROM kernel and check to see if you can boot normally to your previous rom.
Click to expand...
Click to collapse
thanks but i tried that...without result.cause the phone is not reconized and keep disconnecting
is that a driver problem??
hello everyone!
i have a few questions. and i have done my research yet i still find no solutions so i will ask here
this is my story...
-root,unlock bootloader,flash cm12 android 5.0.1, ran cm recovery
-running fine for around 2 weeks.
-in those 2 weeks there has been times where phone drained to 0 its battery, then charged it then it was fine
-suddenly one day. charged it after it drained completely. then wont turn on.would boot up to 'sony' screen then repeatedly reboot and do the same thing again.
-could enter recovery, but when trying to reflash rom, phone would reenter boot loop
-have tried charging for days.
-have tried removing battery, same thing
-then used flashtool, relocked bootloader, reflashed stock firware, now cant get into recovery, flash successful, yet phone still cant turn on pass sony screen.
is it a battery problem?
just to add, ever since the first time it started having this problem, i could never get the phone to turn on at all without plugging it in .
Hi Jetdin
had the same problem with my XT a year ago, when a powerbank somehow "nuked" the battery-logic... After that, I had the pleasure to know what a deep-discharge feels like :-/
To revive my XT, I had to replace the Firmware... I did it this way, maybe you can try a "factory reset", maybe it already works out for you...
1. loading it (turned off) 24h with original recharger (don't try to turn it on)
(1a - if you can reboot it to save apps, data, files - do it)
2. reboot into TWRP - and do a factory reset
...and try your XT; with luck, this already solved your problem... if not:
3. get the new image of your choice - i downloaded whiteneos 12.1 - works like a charm... and copy it to an sd-card
4. after (re)loading the XT - boot into TWRP - and install the new image...
...reboot and hope this solved the problem...
Good luck!!
Edit:
that it only stops at the sony-logo sounds like "operating system not working" - maybe a "higher" OS-version will do the trick?
Thanks for the reply theunlucky.
I have tried most of those.
The cm12 was on Android 5.0.1
The stock firmware for the Xperia T only goes up to JB huhu
Jetdin said:
Thanks for the reply theunlucky.
I have tried most of those.
The cm12 was on Android 5.0.1
The stock firmware for the Xperia T only goes up to JB huhu
Click to expand...
Click to collapse
you cant get pass the sony logo?
unlock your bootloader again
1. download whiteneos cm
2. extract the boot.img and flash it via fastbootmode
3. reboot
4. if you see a led hit vol + ( or vol - ) several times until the led color changes
5. now you should be in recovery... try to flash cm12.1 from whiteneo and reboot
Sent from my Xperia T using XDA Free mobile app
I can do that with a locked bootloader is it sir?
How do I relock my bootloader?or do the steps u give also unlock the bootloader?sorry for all the Qs