Database Info

Phone wont stay shut off?

Hello again everyone, im here with another new problem. Out of the blue.
This is what happens.
-Phone is on
Hold down power
Shut off
-Phone shuts off screen goes blank
5 seconds pass
-Phone boots up... never touch a thing....
WTF?
It will not stay off, no matter the rom, I pulled the batter,SD,SIM nothing will shut it off unless i pull the battery.
I've downgraded the phone with the ace hack kit, ive re-rooted. nothing. I've searched, nothing. Anyone out there got a clue? Cus I dont.
FYI:when the phone rebooted after it flashed the downgrade during re-rooting, the alarm was going off and had the snooze button and everything, no matter what it wouldnt go off. but I just went on with the root process and now its gone, but the phone still wont stay off, something just screwed up!

That's hilarious, and I don't mean that literally. I am laughing though, kind of. Why? Because the same thing just happened to me last night. I know I said the exact same thing you said, possibly more. I have been on the same rom for a week and the only thing I have done was update a couple of apps from the market last night. Nothing else was done. Suddenly I can not power off the phone, it simply shuts off for five seconds and then reboots. I have wiped, restored, and tried flashing and the issue still persists. I am heavily researching and experimenting on what could be the cause for this issue. If I figure it out I will be sure to let you know.

Wolf_2 said:
That's hilarious, and I don't mean that literally. I am laughing though, kind of. Why? Because the same thing just happened to me last night. I know I said the exact same thing you said, possibly more. I have been on the same rom for a week and the only thing I have done was update a couple of apps from the market last night. Nothing else was done. Suddenly I can not power off the phone, it simply shuts off for five seconds and then reboots. I have wiped, restored, and tried flashing and the issue still persists. I am heavily researching and experimenting on what could be the cause for this issue. If I figure it out I will be sure to let you know.
Click to expand...
Click to collapse
Lol that is funny, what apps did you update?
I also have a problem with charging the phone and not sleeping, i was starting to think that it was just finaly getting worst

The only apps that were updated were Battery Monitor widget, Elixir, Xfinity TV, and one more which I can't remember right now. If you do get your phone to shut off, which I have been able to do twice, it may not wish to power back up, which is what mine does now also. (Laughing hysterically now.) Just pull the battery out and put it back in and it will power up. My feelings are that this may have been caused by some kind of update. Possibly from the market or from ATT. I have tried three different roms and it is still doing the same thing. I am about to wipe and restore the phone back to stock and see if it does it still. I will keep you appraised.

Wolf_2 said:
The only apps that were updated were Battery Monitor widget, Elixir, Xfinity TV, and one more which I can't remember right now. If you do get your phone to shut off, which I have been able to do twice, it may not wish to power back up, which is what mine does now also. (Laughing hysterically now.) Just pull the battery out and put it back in and it will power up. My feelings are that this may have been caused by some kind of update. Possibly from the market or from ATT. I have tried three different roms and it is still doing the same thing. I am about to wipe and restore the phone back to stock and see if it does it still. I will keep you appraised.
Click to expand...
Click to collapse
I dunno, I already did that and it did nothing, but I guess its worth a shot for you...
And I dont have any of those apps
If I find something I'll post here
/me shrugs

I am very confused by this, but I will have to try a restore to stock to see what happens. I do find it strange that two different people had this happen to their phones at about the same time and day. I will let you know how things progress later.
Edit: What version of Clock Work Mod recovery do you have installed and which rom were you running? Trying to go through the variables with this issue.

Wolf_2 said:
I am very confused by this, but I will have to try a restore to stock to see what happens. I do find it strange that two different people had this happen to their phones at about the same time and day. I will let you know how things progress later.
Click to expand...
Click to collapse
Yeah it is odd, could be coincidence, could be related, dunno, I dont see how it could be an ATT update when nearly all the roms here have that function disabled. Then again maybe you know something I don't
What did you do to get it to turn off finally? I dunno if I wanna try now that you said it wouldn't turn back on.
Also, what rom where you on when it started, I was on CM nightly #121 or maybe #120 I forget

I just happened to come across this in the general section
http://forum.xda-developers.com/showthread.php?t=1145495
no fix though

I am restoring an old rom and I will try changing the date as someone suggested to see what that does. If it does not work then I will have to wait until later tonight to return the phone to stock and go step by step from there.

Wolf_2 said:
I am restoring an old rom and I will try changing the date as someone suggested to see what that does. If it does not work then I will have to wait until later tonight to return the phone to stock and go step by step from there.
Click to expand...
Click to collapse
Could this have something to do with partitioning the SD card? I think i remember reading that clockwork bricked some phones, is that true?

I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
Edit: I changed the time and date back to automatic and it is working like it should again. Did you get yours working again or is it still having problems?

Wolf_2 said:
I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
Edit: Did you get yours working again or is it still having problems?
Click to expand...
Click to collapse
This worked for me also.

im still having this phone wont shut off issue as well. i have set it to the same date as u and turned off auto and it still just reboots when trying to turn it off

Try leaving automatic off for a whole day. Then see if it is still having this problem. Also replied to pm but try this first to see if it gets past it and works..

willdo thanks a bunch

BAleR said:
Hello again everyone, im here with another new problem. Out of the blue.
This is what happens.
-Phone is on
Hold down power
Shut off
-Phone shuts off screen goes blank
5 seconds pass
-Phone boots up... never touch a thing....
WTF?
It will not stay off, no matter the rom, I pulled the batter,SD,SIM nothing will shut it off unless i pull the battery.
I've downgraded the phone with the ace hack kit, ive re-rooted. nothing. I've searched, nothing. Anyone out there got a clue? Cus I dont.
FYI:when the phone rebooted after it flashed the downgrade during re-rooting, the alarm was going off and had the snooze button and everything, no matter what it wouldnt go off. but I just went on with the root process and now its gone, but the phone still wont stay off, something just screwed up!
Click to expand...
Click to collapse
I had that problem, but it was the car app. I had to disable it in the settings.

seems this keeps happening more and more to people. i still have yet to solve my issue
well i retried setting the date on the phone but this time i chose 1/1/2011 and now the phone stays off when i turn it off which is nice but now i have to deal with having the wrong date

[Q] AT&T SG3 re-boots every 2-3 minutes after OTA upgrade to 4.2.2

Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.

ShrinkWrap561 said:
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.

bweN diorD said:
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
Click to expand...
Click to collapse
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.

ShrinkWrap561 said:
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
Click to expand...
Click to collapse
you have got me on this one. it acts like a classic software issue. now that that has been eliminated.
you performed a factory reset after the flash im assuming?
i don't know what else to tell you, if the software is clean, it has to be hardware damage.
sorry

Frequent Reboots. Please Help

I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.

I
demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
I don't know why your having such an issue with cm. Which is odd because I'm running a rom that's CM based and works fine. I'd say maybe try another rom if for nothing other than to see if CM is truly the issue.
I praise you for having the unlimited data still, I wish I would be been smarter and kept mine because there are months where I'm a little too close to that sad but lack of data with 2gb
And my hometown is Syracuse NY as I see your city is there. I miss the cuse but not the loudness of the city
From my Wicked S3 on SOKP

Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...

BSOD2600 said:
Pull a logcat or use a tool like https://play.google.com/store/apps/details?id=com.tortel.syslog to do this for you. then after the phone reboots itself, run syslog and examine the last_kmsg and logcat to see what the obvious errors/issues are.
I too have noticed google maps crashing, camera unable to connect, random reboots, file system errors, sluggishness, etc more lately with my G3 too. Wonder if some aspects of the hardware are failing...
Click to expand...
Click to collapse
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
From my Wicked S3 on SOKP

ShapesBlue said:
I solved the problem on my S3 with the camera. Freeze the system. Default and run another app, I'm on 4.4.4
Click to expand...
Click to collapse
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.

BSOD2600 said:
You mean freeze the stock camera and use the Google camera instead?
Yea, when the camera is broken, neither app can connect until phone rebooted. Already tried many a time.
Click to expand...
Click to collapse
Yes freeze stock camera. I'm using focal and it works fine but the stock camera won't work at all
From my Wicked S3 on SOKP

demarcmj said:
I have been using Cyanogen for at least the past year. In the past I have had trouble with things like random reboots, maps crashing during navigation, etc. Because of this I switched to just running the milestone releases for the past six months or so, and that has worked reasonably well. Its still way buggier than stock, but I put up with it for all of the nice features and what not.
Lately though reboots have become more and more frequent even though I hadn't changed anything. I had been running M9 for the past month with no real problems and then last night it decided to just go into a boot loop. I tried pulling the battery, clearing the cache, clearing dalvik, nothing worked. Eventually I just let the thing boot loop all night long and when I woke up it was finally booted.
Then this afternoon it did it again for a short period of time (3 or 4 minutes). When it came out I decided to download the newest, M10. It took several tries to actually flash it because the phone would reboot iself while in the middle of the wipe, or the flash, etc. But I started the wipe/flash process from the beginning every time to make sure I had a clean flash and eventually I got all the way through. But now it is at a point where it will boot, sit there for 2 or 3 minutes (I don't even touch it), and then reboot.
I'm hoping someone can help. I'm holding onto my unlimited data for dear life... I don't want to have to get a new phone. But re-flashing doesn't fix the problem so I really don't know what to do.
Click to expand...
Click to collapse
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.

BattsNotIncld said:
These symptoms could indicate a sticky power button. Try knocking it lightly against the corner of a table to jar whatever is making it stick loose.
It doesn't sound software related, especially since it rebooted while in recovery. If you hold the power button down long enough in recovery it will reboot, which makes me think you just have a sticky power button. It's happened to me before.
Click to expand...
Click to collapse
I think you might be right. Even when it is up and running, I have been noticing lately that I get the power menu popping up sometimes when I wasn't even touching the power button. So last night when it was in one of its constant boot loop fits I took it apart a bit (took the back off, took out the battery sim and sd, and unscrewed the shell) and blew some compressed air all around the power button. It had been rebooting for about an hour at that point and then as soon as I put it back together it came up on the first try. So far so good.

Random restarts

Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks

OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?

Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?

Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?

So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?

I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.

TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor

I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app

TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.

harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...

Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.

Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.

I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.

Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/

XZP goes dead everyday

My XZP goes dead everyday once. No reaction and black screen, even if the power cable is connected. I had to press both volume up and down plus power to wake it up. I wiped everything and flashed the newest official firmware without root. It still died last night. I could go into fastboot but it doesn't recognise the device so I can't flash twrp. Adb is fine. Is it a hardware issue? Do I need a new phone now? The phone is almost 3 years.... please help.

Usually when flashtool (I'm guessing that's what you meant) doesn't recognize a device it's because of incorrect drivers.
The powering off thing is weird because it's not just powering off, because if it were you'd just hit the power button to turn back on. Is the phone reset when you power back up or is everything as it was? If you're on stock firmware that should eliminate it being software. My guess it's time for a new phone. Extremely doubtful Sony will make this a Treble phone which means no android 10 and they're already working on 11, plus the whole 5G thing. My advice, new phone, not Sony.

Thank you for your reply...I don't think it's the driver because I flashed TWRP before with the same laptop. And nothing has been changed. It just didn't recognise the phone in fastboot, when I typed 'fastboot devices' it just says 'waiting for device'. After the phone was dead, it didn't lose anything...I guess you are absolutely correct - it's time for a new phone, not Sony. Maybe a Pixel would be a good choice, my original Pixel is still working fine without any problems, only the battery is not lasting as long as the XZP...

xueyaotianxia said:
Thank you for your reply...I don't think it's the driver because I flashed TWRP before with the same laptop. And nothing has been changed. It just didn't recognise the phone in fastboot, when I typed 'fastboot devices' it just says 'waiting for device'. After the phone was dead, it didn't lose anything...I guess you are absolutely correct - it's time for a new phone, not Sony. Maybe a Pixel would be a good choice, my original Pixel is still working fine without any problems, only the battery is not lasting as long as the XZP...
Click to expand...
Click to collapse
Just for the heck of it go into device manager with phone plugged in, dev mode enabled, blah blah blah and see what it says. I've had to reinstall drivers in the past. Also try disabling usb debugging then re enable and see if the phone asks you to allow debugging from this device (your comp.). None of this is going to fix the powering off but just to see if you can get your computer to recognize the phone again.

Tried to reinstall the driver again...still cannot find device in fastboot mode...maybe I'll just monitor the phone for a few days to see if it behaves normally. It did freeze again yesterday when I was playing a video...

I deleted the old driver and installed again...it is ok now. I'll flash Carbon rom now and see if the phone will go dead in the next few days...

xueyaotianxia said:
I deleted the old driver and installed again...it is ok now. I'll flash Carbon rom now and see if the phone will go dead in the next few days...
Click to expand...
Click to collapse
I tried Carbon on my XZP and had issues with the phone not seeing a sim card. I use eXsistenZ on mine. I know it's not a rom but has nice customization options and works smoothly. I'm getting to where I really don't want to mess with all the glitches of custom roms just to be able to remove crapware and see some arbitrary improvement that means little to me, and then lose the stability of stock. You can always hide the crapware, and yes it's still there, hiding, but I can live with that.

I also had same sim issue with Carbon...back to stock now. Rooted and delete the bloat. It died once last night unfortunately...I think I'll get a new phone after this Covid 19 thing, don't really want to go out now under national lockdown...time to upgrade.

xueyaotianxia said:
I also had same sim issue with Carbon...back to stock now. Rooted and delete the bloat. It died once last night unfortunately...I think I'll get a new phone after this Covid 19 thing, don't really want to go out now under national lockdown...time to upgrade.
Click to expand...
Click to collapse
I hear ya. We need more people to take this seriously.

Just an update. The phone went dead again on stock. So I flashed carbon yesterday, until now there are no issues....I shall stay on carbon now. It feels way better than stock rom.

Hmmm. That's so weird. You would think that if it were a firmware issue, that glitch would be in all XZPs running it. How did you solve Carbon rom not seeing your sim card?

bobsright said:
Hmmm. That's so weird. You would think that if it were a firmware issue, that glitch would be in all XZPs running it. How did you solve Carbon rom not seeing your sim card?
Click to expand...
Click to collapse
Until now the phone is ok. So I'd say it is a firware issue. I found out I had to wait like 2 minutes after each reboot before Carbon recognises my sim card. But, it is still better than the phone dying everyday...it runs much smoother than stock. More features too..I am happy now haha...

Excellent!!