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??
Related
Okay, here's what happened.
I installed CWM recovery and installed custom ROM (Cyanogen Mod 7)
Since the kernel did not support it, I flashed the Kernel using Flashtool.
It flashed successfully and asked me to unplug the phone.
I left the phone connected to USB and left it for quite some time (maybe 1/2 hour )
All the while, the green LED was showing up meaning it was in Flash or Fastboot mod or whatever.
When I finally removed the phone, the led turned off and then nothing would happen.
When I tried to power on, nothing happened. (no vibration, no led, no screen flash, nothing)
A thing to be noted is that this was my first time and I had downloaded almost 2gb of unlocking, flashing and rooting tools and some of 'em were open.
Now the phone is hard bricked with no response to any input.
Please suggest any method to fix this without taking it to the SE Service.
I searched everywhere, but couldn't find.:crying::crying::crying:
albinkc said:
Okay, here's what happened.
I installed CWM recovery and installed custom ROM (Cyanogen Mod 7)
Since the kernel did not support it, I flashed the Kernel using Flashtool.
It flashed successfully and asked me to unplug the phone.
I left the phone connected to USB and left it for quite some time (maybe 1/2 hour )
All the while, the green LED was showing up meaning it was in Flash or Fastboot mod or whatever.
When I finally removed the phone, the led turned off and then nothing would happen.
When I tried to power on, nothing happened. (no vibration, no led, no screen flash, nothing)
A thing to be noted is that this was my first time and I had downloaded almost 2gb of unlocking, flashing and rooting tools and some of 'em were open.
Now the phone is hard bricked with no response to any input.
Please suggest any method to fix this without taking it to the SE Service.
I searched everywhere, but couldn't find.:crying::crying::crying:
Click to expand...
Click to collapse
First of all,did you tried to unlock bootloader?
if not then try to flash stock ROM(which includes STOCK kernel)
and btw this
albinkc said:
All the while, the green LED was showing up meaning it was in Flash or Fastboot mod or whatever.
.
.
.
.
When I tried to power on, nothing happened. (no vibration, no led, no screen flash, nothing)
Click to expand...
Click to collapse
doesnt make any sense....if LED was green AFTER you flashed kernel than your phone should turn on
Anyway try to flash using FLASHTOOL (IT SHOULD WORK)
yeahh
if you didn't Unlock Bootloader your phone, maybe u got Softbrick
just flash the 2.1 firmware
download from my signature
cheer
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.
Hello!
Earlier, I rooted my new Xperia V and flashed official CM 10.2 (stable). Everything worked fine. Later, I tried a few times the CM11 nightlies. 1-2x I get back to CM10.2 with a previous CWM backup. Yesterday, I changed back to CM10.2 again, after I got a few blue screen reboots with CM11. But after I restored CM10.2, I noticed that I am still getting blue screen reboots with CM10.2 too. :-O I didn't understand it, so I wiped everything, formatted my SD card and tried a full clean install. After the first gapps updates via play store, I got a blue screen reboot again. I was angry and formatted system, data, cache, sdcard0, sdcard1 via CWM and power off. I copied the needed install zips to my SDcard with a card adapter, put it back to my phone and tried to turn on, but nothing happened at all. I also tried to connect to my PC and start in fastboot, but the blue LED also did not come and nothing happened. Totally dark everything, even after some minutes with removed battery. Only I get a blinking red LED when I remove the battery and connect to the charger (which stops, when I am pushing the power button), but apart from this, completely nothing. (( I am really scared now, help somebody. :$$$
Best regards,
Zalan
EDIT: sorry, DUPLICATE - http://forum.xda-developers.com/showthread.php?t=2572334
banciii said:
Hello!
Earlier, I rooted my new Xperia V and flashed official CM 10.2 (stable). Everything worked fine. Later, I tried a few times the CM11 nightlies. 1-2x I get back to CM10.2 with a previous CWM backup. Yesterday, I changed back to CM10.2 again, after I got a few blue screen reboots with CM11. But after I restored CM10.2, I noticed that I am still getting blue screen reboots with CM10.2 too. :-O I didn't understand it, so I wiped everything, formatted my SD card and tried a full clean install. After the first gapps updates via play store, I got a blue screen reboot again. I was angry and formatted system, data, cache, sdcard0, sdcard1 via CWM and power off. I copied the needed install zips to my SDcard with a card adapter, put it back to my phone and tried to turn on, but nothing happened at all. I also tried to connect to my PC and start in fastboot, but the blue LED also did not come and nothing happened. Totally dark everything, even after some minutes with removed battery. Only I get a blinking red LED when I remove the battery and connect to the charger (which stops, when I am pushing the power button), but apart from this, completely nothing. (( I am really scared now, help somebody. :$$$
Best regards,
Zalan
Click to expand...
Click to collapse
Does your pc recognize it in flashmode? If so, flash the kernel from your cm10.2 via flashtool
St.Jimmy90 said:
Does your pc recognize it in flashmode? If so, flash the kernel from your cm10.2 via flashtool
Click to expand...
Click to collapse
No, it doesn't recognize my device in any mode. I tried simple connect, volume up push connect, volume down push connect, but nothing at all.
Same as me. Only red LED blinking (the normal one does not, it's can enter to fastboot even if not on the battery).
Hope you find the solution soon.
Atm, I am checking this guide: http://forum.xda-developers.com/showthread.php?t=1849170
I hope I can find something, somewhere... :SSS
Try this maybe
Open up flashtool.
Hold vol down and plug in
Leave it plugged for a while(a couple of minutes) with red LED blinking.
see if it changes into green or blue ( last time it changed into green for me
then if it has changed flash stock ftf.
if nothing happens take the battery off and try again.
Something similar happened to me last time, send it to fix and lost warranty....fixed it myself after it was back
Allen Hu said:
Try this maybe
Open up flashtool.
Hold vol down and plug in
Leave it plugged for a while(a couple of minutes) with red LED blinking.
see if it changes into green or blue ( last time it changed into green for me
then if it has changed flash stock ftf.
if nothing happens take the battery off and try again.
Something similar happened to me last time, send it to fix and lost warranty....fixed it myself after it was back
Click to expand...
Click to collapse
No LED blinking or any other LED actions at all. Flashtool or my PC doesn't recognize the phone at all.
edit: it blinks (red) only if I connect to the charger or the PC with removed battery
Too Bad... couldn't help you...
It may be a faulty battery. Your simptoms are pointing to that. What about leave it to charge for 12 hours?
Sent from my LT30p using xda app-developers app
Moon_Fire said:
It may be a faulty battery. Your simptoms are pointing to that. What about leave it to charge for 12 hours?
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
Nothing helped. The problem was that I formatted every /partition on the phone, so there was nothing to start. The service could not fix my phone in 3 months, so finally they give me a new one with 70% discount because of the long waiting time. (No warranty because of the root ofc.)
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).
Hello,
my Redmi 4x won't boot. I tried to find some solution for this issue, but I can't find it anywhere, so I created this new thread to ask you for your help.
Last night I was out in the city and my phone died because of low battery, so after I came home I just wanted to charge it as usual. Battery logo showed up and it was behaving as always, but when I tried to turn it on it couldn't boot again.
After pressing the power button the splash screen flashes for a brief moment and then it just turn off again. This happens all the time from the moment my phone died. I'm not sure what went wrong here. I can't get it to recovery mode either. So I wanted to do a fresh start and flash it again with new ROM here (Ressurection Remix 6 is what I have now)
I'm able to get it on fastboot mode, but once I try to flash it with MiFlash I get error message like "error:FAILED (remote: Critical partition flashing is not allowed)"
So I looked up for a solution and I found that I need to get it in EDL mode with adb.exe
I tried this solution but with no luck. Phone is restarting but it won't turn on again and the fastboot mode is lost.
I'm not really sure if I have right drivers for it. Qualcomm HS-USB Diagnostics 900E is what I have now. I can't also change the usb debugging mode obviously, so I'm also trying to find some solution for this issue either (is there any chance how to turn it on with adb.exe?)
I think it's softbricked but i'm not really sure.
Thank you for your help
p3wp3w said:
Hello,
my Redmi 4x won't boot. I tried to find some solution for this issue, but I can't find it anywhere, so I created this new thread to ask you for your help.
Last night I was out in the city and my phone died because of low battery, so after I came home I just wanted to charge it as usual. Battery logo showed up and it was behaving as always, but when I tried to turn it on it couldn't boot again.
After pressing the power button the splash screen flashes for a brief moment and then it just turn off again. This happens all the time from the moment my phone died. I'm not sure what went wrong here. I can't get it to recovery mode either. So I wanted to do a fresh start and flash it again with new ROM here (Ressurection Remix 6 is what I have now)
I'm able to get it on fastboot mode, but once I try to flash it with MiFlash I get error message like "error:FAILED (remote: Critical partition flashing is not allowed)"
So I looked up for a solution and I found that I need to get it in EDL mode with adb.exe
I tried this solution but with no luck. Phone is restarting but it won't turn on again and the fastboot mode is lost.
I'm not really sure if I have right drivers for it. Qualcomm HS-USB Diagnostics 900E is what I have now. I can't also change the usb debugging mode obviously, so I'm also trying to find some solution for this issue either (is there any chance how to turn it on with adb.exe?)
I think it's softbricked but i'm not really sure.
Thank you for your help
Click to expand...
Click to collapse
Hi, most likely your battery is faulty. Current draw during Android kernel boot up phase is above 1A whereas only around 0.2A for a working OS, that's why neither OS nor recovery can start when the battery develops high ESR (internal resistance). Do the following test:
fully recharge the battery
do not disconnect the charger
turn it on
Your Android may now actually work again but you must use a short quality cable connected to a 2A+ charger, which will support the battery at boot time - and you can disconnect it later.
k23m said:
Hi, most likely your battery is faulty. Current draw during Android kernel boot up phase is above 1A whereas only around 0.2A for a working OS, that's why neither OS nor recovery can start when the battery develops high ESR (internal resistance). Do the following test:
fully recharge the battery
do not disconnect the charger
turn it on
Your Android may now actually work again but you must use a short quality cable connected to a 2A+ charger, which will support the battery at boot time - and you can disconnect it later.
Click to expand...
Click to collapse
Thank you, but the battery wasn't the main issue, because once I was able to flash it through EDL mode to the latest stable official ROM, the battery was on 93% already.
Now I'm stuck with MI logo and powered by android with 3 blinking dots above. I watched somewhere, that it could last for 7 minutes, but for me even the 15 minutes is not enough, so I guess i'm in bootloop.
For some reason my bootloader is locked again, even though I already made the unlocking process earlier before I flashed to Resurection remix 6. My phone doesn't even appear in device manager. I can't even use it as a storage, so I could try to flash it to custom ROM.
I'm not really sure wat happened and how is it possible to brick your phone by just draining your battery to 0%
Ok, phone is alive again. It booted up right after I inersted microSD card in slot. I didn't know this was necessary...