Hello Guys.
Am facing a wired issue on my SXL.
Am Rooted, Bootloader unlocked and on Custom Rom build by Fshami..
The Thing is i flashed between 2 diff rom without full wipe. ROM wise everything works fine.
As now my Battery has screwd up cos of flashing and Reflashing, so i thought of doing a Charge cycle.
I made the SXL die without any blood in it and when i plugged in, the device goes into CWM rather charging.
When i select power off in CWM, it again goes into CWM..
I have to boot back into OS to get it charged..
Is this Normal?
Can someone try to charge the device with device powered off ??
Thanks in Advance
omg ... i m having that issue right now and dun know how to fix it ... as soon as i restart da phone it goes into CWM ... i can't mount sd card or factory reset .... irritating ...
HELPPPP!!!!!!! :crying:
Flash stock recovery.
With .bat
and you can charge the phone.
What you are facing is a known issue for CWM. Whenever you turn off the phone and plug it in, the phone enters recovery mode. Anyway it's not a big problem. You can flash another recovery as Stona suggested (thanks to him for many useful posts that helped me before ), or you can simply select "reboot system now" from recovery menu and charge the phone while it is on. Then, if you would like to charge the phone at night without being annoyed by calls or notifications, you can let your device on and select airplane mode...
hi guys, yesterday i did some flashing of roms just like i do almost every day or so, and i didnt like the rom(flyme rom) i flashed so i just tried to restore the previous rom which was the existenz rom .... so using TWRP, i put that to restore and i went to eat something but after a couple of minutes, i went to my phone to see if it was completed and it was powered off by itself... ( the phone was not completely charged but it had at least 50% of battery so i dont think battery is the issue here).....so after that,i powered it on and it stuck in a bootloop so i realized that the restore wasnt successful.... so i went into the recovery and i did a factory reset and i tried to flash another rom cm11 based (that i had been using some days ago) and the flashing was successful ( with gapps and ssu...) so i rebooted but nothing.... my phone powered off as it should but when it powered on, sony logo appeared (as it should) and then it suddenly powered off again..... i couldnt even enter the recovery cause it immidiately turned off 2 seconds after sony logo appears.....so i went into fastboot mode and i flashed a kernel of cm11 just to be able to enter at least the recovery .... successfully flashed boot.img but again couldnt enter the recovery...the same as before.....then i realized that if i tried to power on my phone while it was charging ( wall charger) it could boot and even enter the rom but still after some seconds it immidiatly powered off by itself for no reason...then i didnt know what else to do so i had a last chance.to flash an ftf....so i flashed one successfully using flashtool and the same problem again..... then i flashed another one ( older ftf ) but nothing..... then i tried to charge my phone until full ( i could see in TWRP the percentage) and then i powered on but the same..... however it did open whithout charging ....but again after some seconds it powered off again.... so i went in TWRP and i left it there open all night to drain all the battery ...and i noticed that it drained until 1% and then it took it about 1 hour to power off ....i mean it was on 1% with screen on for more than an hour.... so i think that the battery has to be reseted or something..... i dont know what to do.... i have unlocked bootloader, i have no warranty , and i dont even know what is causing that so please if somebody knows something about that tell me....
(btw before all that happened, my battery was fine...i could spend many hours with screen on.... i had not noticed any damage to the battery or something)
Try to flash a stock ftf to your phone from flashtool
tjlm21 said:
Try to flash a stock ftf to your phone from flashtool
Click to expand...
Click to collapse
They already did. Read before posting.
Sent from my C6603 using Tapatalk
A partition or partitions could be corrupted, and formatting is the only way to fix that. Not sure if flashtool formats before writing images - so..
1. Fastboot a kernel (boot.img) .
2. Boot into recovery and format EVERYTHING, including /data/media.
3. Power off phone.
4. Flash an ftf.
Good luck:thumbup:
shoey63 said:
A partition or partitions could be corrupted, and formatting is the only way to fix that. Not sure if flashtool formats before writing images - so..
1. Fastboot a kernel (boot.img) .
2. Boot into recovery and format EVERYTHING, including /data/media.
3. Power off phone.
4. Flash an ftf.
Good luck:thumbup:
Click to expand...
Click to collapse
thanks for posting but i already did that.... i will buy a battery and i hope that solves the issue :/
Hi,
I was trying to install stryflex rom (http://forum.xda-developers.com/xpe...-stryflex2013266073-lp-official-sony-t3180637) on my xperia yesterday. I already tried stryflex in November but it had some bugs so I had to move to 4.3 rom at that time. I successfully installed stryflex yesterday but touchscreen was not working even upon multiple restarts. I thought to re-flash whole thing. Don't know how but I think I accidentally flashed some other files in kernel via flashboot software and after that phone was not taking any charge. Showing red led even after charging for more than 1 hours. I checked few kernels and installed William kernel using that .elf file and flashing as 'flash kernel' option in fastboot mode.
After that, phone is starting but showing William kernel for some 15-20 minutes. I tried doomkernel and it also showed it's logo for some 20 minutes and shut down and restarts again. Phone is still not taking charge and showing red led. I think it is not taking more that 1-2% charge.
I don't know what to do. Please tell me solution in schematically way.
Also, how installing custom roms works? Which process (installing rom, twrp etc) comes first and which last.
Any help would be highly appreciated.
Thank You
destiny4life said:
Hi,
I was trying to install stryflex rom (http://forum.xda-developers.com/xpe...-stryflex2013266073-lp-official-sony-t3180637) on my xperia yesterday. I already tried stryflex in November but it had some bugs so I had to move to 4.3 rom at that time. I successfully installed stryflex yesterday but touchscreen was not working even upon multiple restarts. I thought to re-flash whole thing. Don't know how but I think I accidentally flashed some other files in kernel via flashboot software and after that phone was not taking any charge. Showing red led even after charging for more than 1 hours. I checked few kernels and installed William kernel using that .elf file and flashing as 'flash kernel' option in fastboot mode.
After that, phone is starting but showing William kernel for some 15-20 minutes. I tried doomkernel and it also showed it's logo for some 20 minutes and shut down and restarts again. Phone is still not taking charge and showing red led. I think it is not taking more that 1-2% charge.
I don't know what to do. Please tell me solution in schematically way.
Also, how installing custom roms works? Which process (installing rom, twrp etc) comes first and which last.
Any help would be highly appreciated.
Thank You
Click to expand...
Click to collapse
if you can flash kernel via flashtool its great, but doomlords or William kernel looks like dont support offline charge so if you have at leats couple percent of battery try to flash some costum roms ,
i recommend this few steps:
1. flash doomlord kernel ( .elf) or lates cynogen recovery ( .img) via flashtool
2. if you flash it , try to put phone on charger if you have low battery (0-10 %) , or if you have over 10 %
ps. Lastest cm recovery should support offline charging
3 .just flash costum CM 12.1 form sd card
ps 2.( "Phone is still not taking charge and showing red led. I think it is not taking more that 1-2% charge. ")
its seams you have couple percents of battery , so installing cosutm rom should not be a problem
anyway let us know what happend
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,
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...