Database Develop

[Q] Serious problem, auto shutdown

i am currently using the Xperia Z LTE with version .244, LOCKED BOOTLOADER.
After HEAVY flashing with the previous Z1 camera ports and the existanZ roms, my phone shut down randomly. Its getting more shut downs recently, the screen Just blacked and i need to turn on the phone again. I even have problem starting up, example it shuts down immediately during booting up, sometimes during normal usages. I have tried re flashing using flash tool , erasing everything flashing a new firmware, still no luck, using PC companion to repair. I even try NOT to root it, but it still shutdowns, only way to prevent it was to PLUG IN THE POWER WHILE USING.. no shut downs then. After unpluging, the shutdown come back. Anyone has this issue too? Any help?

Maybe your battery is mostly empty, or gets recognized as empty.
This could help you:
Let the phone charge for 24h while it's on. Then flash Stock Rom with PCC or FT.
Sent from my Dualbooted XZ

Tried but still no luck, anyone any more ideas?

finoqq84 said:
i am currently using the Xperia Z LTE with version .244, LOCKED BOOTLOADER.
After HEAVY flashing with the previous Z1 camera ports and the existanZ roms, my phone shut down randomly. Its getting more shut downs recently, the screen Just blacked and i need to turn on the phone again. I even have problem starting up, example it shuts down immediately during booting up, sometimes during normal usages. I have tried re flashing using flash tool , erasing everything flashing a new firmware, still no luck, using PC companion to repair. I even try NOT to root it, but it still shutdowns, only way to prevent it was to PLUG IN THE POWER WHILE USING.. no shut downs then. After unpluging, the shutdown come back. Anyone has this issue too? Any help?
Click to expand...
Click to collapse
battery or the battery circuit problem.
first try with replacing the battery.

Can't turn ON my Xperia V [DUPLICATE]

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.)

Xperia Z Boot problem

Hello, this is my first post here and ofcourse I have a problem...
So yesterday I was rooting my Xperia Z, unlocked the debug mode and was able to access the recovery mode a few times. So I flashed my device to 4.2 version with a computer then I copied the 4.2.2 .tft file and the Kernel into my phones internal memory, turned my phone off, turned it on again, turned on the recovery mode, did the "Wipe data/Factory reset", wiped the catche partition, wiped the Dalvik cache, formated the system, formated the data and the cache. So then I went to install the prerooted ROM but my phoned seemed not to find it in the internam memory so I selected to reboot my device and since then it is acting all weird...
So the phone then tried to reboot but freezed at the Sony logo, the battery was about 89% and the phone started heating like it was working on its max, the phones battery died after about 2 or 3 hours, so ofcourse I tried connecting it to my PC to try to charge it but it just started to boot loop, I could hear the computer making a notification sound that the device is connected and after a few seconts it just disconnects. It seems that the phone isnt charging at all because after leaving the phone to charge for the whole night with a regular charger the phones LED was still red and was giving me 3 blinks when I tried to turn the device on. I think that if I could to access the recovery mode again I would be able to fix everything from there on my own...
Any help to fix this problem is welcome, I can provide more information about the problem if there are some questions
P.S. I already tried to remove the microSIM and microSD cards

flash the ftf file you have using flashtool

Richy99 said:
flash the ftf file you have using flashtool
Click to expand...
Click to collapse
I noticed a really weird thing. It looks like it might be both technical and software problem. So earlyer I had the rooted 4.4.2 version but it started to bootloop when I turned on the camera, the device turned off when it was at about 60% battery. So I though to hell with this version and wiped everything again, installed the 4.4 version with flashtool but then the bootlooping started again, it went no further than the Sony logo, after about 2 hours of trying to get the damn thing on I took my fathers Galaxy S4 charger and pluged it into my phone, for my surprise the phone started charging and was displaying that battery icon in the middle of the screen, so now its about at 30% battery and trying to turn it on wont work, almost gets to the main screen and then instantly turns off. Ill try to charge it to about 80% battery and then try to turn it on. I suspect that the device thinks its battery is empty when it is actually at about 60%

FerretXing said:
I noticed a really weird thing. It looks like it might be both technical and software problem. So earlyer I had the rooted 4.4.2 version but it started to bootloop when I turned on the camera, the device turned off when it was at about 60% battery. So I though to hell with this version and wiped everything again, installed the 4.4 version with flashtool but then the bootlooping started again, it went no further than the Sony logo, after about 2 hours of trying to get the damn thing on I took my fathers Galaxy S4 charger and pluged it into my phone, for my surprise the phone started charging and was displaying that battery icon in the middle of the screen, so now its about at 30% battery and trying to turn it on wont work, almost gets to the main screen and then instantly turns off. Ill try to charge it to about 80% battery and then try to turn it on. I suspect that the device thinks its battery is empty when it is actually at about 60%
Click to expand...
Click to collapse
Try flashing 4.3 Stock rom from flashtool

androidtweaker1 said:
Try flashing 4.3 Stock rom from flashtool
Click to expand...
Click to collapse
Still boot looping, when I flashed it into 4.3 and it started up for the first time i got the message "process system isnt responding"

HELP xperia z problem-cant solve it

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 :/

XZ in continious bootloop, no matter what i flash/do

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?