Sudden reboot of Z3 Stock, can't login and recovery to Stock doesn't fix it - Xperia Z3 Q&A, Help & Troubleshooting

Hey folks,
I just have a very weird issue with my Z3 Stock firmware : it was in my pocket and suddenly, started to reboot over and over for no apparent reason. So it was heating and the battery was quickly flat. Since then, I can't use it anymore : it startup correctly and once you can finally use the screen to unlock it, it's already "crashed" and several second later, it reboot (over and over ...).
Tried to recovery with the Sony Companion which worked and I could see change after that flash : there is now a "hello" as if it was fresh new, but no time to select anything and again, crashed and reboot.
I have no idea of why, anyone ?
I think the hardware is now defect, but as it start correctly (and flash to stock worked), I really don't understand.
I've seen a post where someone say that it's (could) be because of the gyroscope ... really ??
Help appreciated,
Thx

Hey, more information.
So I was able to flash stock firmware, android 5 or 6, both reboot loop. Each time, it seems to works (touch screen OK) then there is a text displayed and after that, freeze and reboot.
The Killin message, on android 5 or 6 stock rom :
FACTORY STARTUP SERVICE - Please wait for on-screen POWER OFF button
I've never seen that button on screen, reboot before. Any idea? Possibly due to hardware failure? Looks to works, but is not working, sad.
Thx

Related

[Q] Stock w/ root question.

I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Orical said:
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Click to expand...
Click to collapse
If you boot into recovery or hard reset by holding the power button. It will always ask to send crash report
OK cool so it's normal, thanks for the information.

[Update 4/3: Logs] N5 works normally -> stuck on splash screen -> have to reflash ROM

[Update 4/3: Logs] N5 works normally -> stuck on splash screen -> have to reflash ROM
My Nexus 5 is having a problem that is just confusing the hell out of me.
To summarize the issue...
1. Phone will get stuck on "Google" splash screen (written in white) on bootup.
-at this point, I can reach bootloader and recovery
-clear cache/format cache does not alleviate problem
-factory reset does not alleviate problem
-fastboot flash-all does not normally alleviate problem
-only flashing a ROM via TWRP works
2. ROM flashed via TWRP, things work like normal for ~4-24 hours. At some point, there will be a random reboot. Usually, this is while under stress (playing a game, updating apps). It will reboot normally and continue to work like normal for some time. But it's a ticking time bomb. There will be another random reboot at some point, often while idle - definitely not workload-related. This second one will get me stuck on the Google splash screen again, with the only way of fixing being re-flashing the ROM via TWRP.
These symptoms are basically the same regardless of the ROM - I've tried factory images, a stock-ish ROM with Gapps removed from XDA, and CyanogenMod. It seems like it could be a hardware problem, but I don't have a clue what it would be since it is so consistently fixable, albeit temporarily. Does anyone have any troubleshooting suggestions or a clue as to what part of the phone is likely failing?
Post logs.
Elluel said:
Post logs.
Click to expand...
Click to collapse
Okay, so this afternoon I went to check on it after spending some time on the charger. The LED was lit, so I thought things would be fine. It just wouldn't wake up. It wasn't responding to various button presses, but the LED turned off after I held the power button. It took a lot more attempts than normal to get to fastboot, but eventually got there. I used fastboot boot to get to TWRP and retrieved last_kmsg, kernel_log, and logcat. Logcast was empty. Here are pastebins for the other outputs.
last_kmsg: http://pastebin.com/z2KG2aHW
kernel_log_output: http://pastebin.com/v7TZZKeb
Thanks for the help!
I'm going to bump this one time, since there are now logs posted which I think might provide some clear insights to those who know how to interpret them.

Still Reboots in Marshmallow

Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Treizez34 said:
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Click to expand...
Click to collapse
I am having the same issue. Random reboots.
I already install the 6.0 three times. one sideload and two fresh installs (full wipe + factory images). I even tried to roll back to lollipop and then update again.... same problem =(
device:
Nexus 5 - 32gb international + moto360
Sorry for my English.
I have the same problem with the Nexus 5 32GB D820.
Marshmallow clean installation ran smoothly yesterday, today began to randomly reboot.
I tried to make a factory reset and left in a bootloop.
I had to re-flash the factory image.
Let's see if it happens again.
Likely defective power button
My nexus 5 32gb is also randomly rebooting on android 6.0
The same problem with D821 16 Gb. 4 times clean installation. 1 time step-by-step installation for each part of factory image - no result. Random reboots.
There is no random reboot software bug, only faulty key
GR0S said:
There is no random reboot software bug, only faulty key
Click to expand...
Click to collapse
What do you mean with faulty key? Faulty like hardware or faulty like software? Cause I have my Nexus for 1,5 years and had never problems with power button at all. The problem comes only with Marshmallow.
---------- Post added at 07:22 AM ---------- Previous post was at 06:47 AM ----------
So, there is no full restart. If you press the power button for 10 seconds, the phone will restart and you'll hear a little vibration and see "Google" logo, after that Marshmallow animation appears. Faulty key can only cause full restart effect. But in Marshmallow I have only the shell restarts, i.e. the phone restarts with Marshmallow animation (not with vibration and "Google" logo) and this lasts 3-5 seconds. This is definitely software bug.
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Exactly. Flashed with fastboot, no mods, no root, no any customs. Only user apps. But you are right. I'm testing all my apps and I've found 2 weather apps. They probably caused the reboots. I'm not sure about it, cause I'm looking into all my apps.
its not a defective power button.
I roll back to lollipop and the random reboot stopped.
I did another try with marshmallow, this time with sideload installation and full wipe after. At the beginning i get two random reboots, but now it seems to be ok. no more random reboots.
SOLVED. The problem was caused by Weather Live application (https://play.google.com/store/apps/details?id=com.apalon.weatherlive). With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
dr_stevens said:
SOLVED. The problem was caused by Weather Live application. With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
Click to expand...
Click to collapse
I found the same issue. I'm a registered user of Weather Live, but I've found that the app is causing numerous crashes after I upgraded my Nexus 5 to Android 6 ( Marshmallow). I ran a bug report and searched it for 'FATAL EXCEPTION:', I can see that everytime there is a crash, one of the threads affected belongs to Weather Live. What I then get is a restart of the User Interface, so it goes into the 'android' animation you normally see on boot. The phone stays up because the System Uptime is not reset.
I've uninstalled the app for the moment to see if that cures the issue.
i am experiencing random reboots with my Spice Dream Uno and ended up in this forum while searching for my cause. first i thought its my device got hardware issue but it never happened before in lollipop or kitkat. it seems just like a possible hardware fault too and phone will be in bootloop , then cant even power on the display(backlight flluctuates,with black screen). when i pull the battery and reinsert after few minutes the phone starts normally. seems like Marshmallow has critical campatibility issues with some applicationsThe crash never happens in same application for me.And i have no roots ,customs etc..Came to 6.0 via OTA from lollipop.
My device dont have any issues upto now(its been an year).
I've been noticing it with a very minimal base of packages. Seems to only happen shortly after waking from deep sleep so I highly suspect doze. The phone will be fine... you set it aside... it enters doze deep sleep... phone wakes, you unlock... then bam, reboots, and enters boot loop at the Google splash screen. I've already done a factory reset, will be attempting a fastboot reflash with the new November system image today.

Booting issue

Hi, I bought a used Nexus 5 and it has been causing quite some problem when booting. I flashed Cyanogenmod in it and it works fine for a few days. After that it keeps having the same problems in the following order:
- It would restart on its own, sometimes some random app will fail functioning (it's never the same app).
- Turns off on itself without restarting. Can still be turned on normally.
- From there it gets worse and start bootlooping. On CM it loops around the part where it initialises the apps. On stock its the colourful stuff that happens right after the Google logo.
- Finally it just gets stuck in boot. On CM it's stuck where it initialises apps while for stock it turns off right after the Google logo appears.
I have tried the following:
- The persist partition fix described at https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
- Cleaning the power button and made sure it wasn't stuck.
- Re-flashing CM, did a checksum to make sure the files are okay
- Went back to stock, did a checksum too.
It's a used phone so I have no idea what it went through in the past. Anything I can do to fix it?
Try running the phone with a stock ROM without root. If the problem still happens, it's probably a hardware problem.
It didn't have root but I flashed a factory image (plus another round of factory reset too) and even locked the bootloader + reset the tamper flag this time. It's working fine now but the problems normally start a few hours/days later so I can't be sure at the moment.
If it does fail again which hardware is the one with the problem? The warranty's long gone so will it be easy to buy a new part and replace it myself?
The cheapest solution may be to buy a used Nexus 5 with a smashed screen and working internal components to swap out components.

J700m rebooting problem

yo guys!
So, months ago I flashed a custom ROM on my j700m, it was EnigmaUX, it worked fine for quite a long time, but I had a issue with it that bothered me: sometimes, when the phone rebooted, it just wont accept my pattern and kept saying it was wrong until I rebooted the phone again. With that in mind, I decided to flash a new ROM to try fixing this problem, I flashed the NOUGAT 7.1.1 - SE 8.5 & GAMING and along with the previous issue I had, I also got a new one: my phone kept rebooting randomly, sometimes the system wont even start back, I had to remove the battery in order to start, it's like the phone reboots in the middle of the start process. My next attempt was to flash the stock rom, which is: J700MUBU2BRC2, and the problem is still happening. The pattern bug stills happens too, that's the weird thing, I removed the ROM and I still have the same glitch... like it was not completely removed.
Does anyone have any ideia what's causing that?

Categories

Resources