Hello all, new to the forum, though have been using it for issues I've had along the way with my Sony Xperia Z3 Compact.
Presently it is in a boot loop. It will boot up, and the phone is usable for approximately 2 minutes before it shuts down and immediately restarts. Only to do the same thing over and over. It also takes 2-8% out of the displayed battery remaining each time. Generally the battery is getting really hot though all of this.
Each time it registers as a "System Incident" in the diagnostics. Though no details are given. Does not register the crashes as "restarts" in the diagnostics.
Here's the kicker: It will NOT boot loop and operate normally (without overheating) if the phone is connected to a computer via USB or if it is playing music or a movie. But, once either of these conditions are no longer, it goes right back into restarting itself.
Here's the phone info:
D5803 (Originally a Canadian market phone)
Android version 5.1.1 (has been since I've owned it)
Build Number: 23.4.A.1.200
Unlocked
NOT rooted
No SD card mounted or present
Here's what I've done:
Hard reset (multiple times)
Boot in safe mode (will still boot loop in safe mode) restart in regular mode.
PCC repair, twice
Gone into service mode and wiped customizations
Complete factory data reset
*Done all of the above WITHOUT restoring my backup files in case there was a corrupt file within those backed up. Also have tried reset attempts with and without re-downloading my normal array of apps from the Play Store. Though none should be crashing the OS.
Even took the Flashtool to it, and reflashed 23.4.A.1.200 Customized US firmware with APPS_LOG and USERDATA wipe, no exclusions. Though, I was suspect of this, as the firmware is US, and on initial setup, it still defaulted to "English (Canada)" for the language on the first screen. Which is where it usually defaults. So I don't think memory was totally wiped or the firmware was reflashed in its entirety.
I would suspect hardware if the phone was not functioning properly while playing music or a movie. I have all functions and all systems working properly otherwise, even during the boot loop, just before it crashes.
Had a similar boot loop issue when 5.1.1 came out, much like many others. That problem righted itself with a few restarts and a full night of being totally shut off. This is not fixing the issue this time.
Thanks in advance for your help. All is appreciated.
Yeah, so this seems to be a hardware, i have had this happen to me, although just randomly.
You should send it off to be repaired, as restoring software should have fixed the issue.
Related
Starting today my nexus one (not rooted, stock vodafone ROM, Android 2.2.1) doesn't start anymore After I restarted my phone, because the sound came from the speaker while a headset was plugged, the 'X-animation' plays 4 times and than sticks for 3 seconds, and starts over again repeatably. Of course I have removed the battery, and tried starting it without the SD-card and SIM, but without success. Also I tried to boot in safe mode, but with no success too.
Can I do something about this, or do I have to do a factory reset (clear storage?) and lose lots of data?
Sounds like you are in dire need of a wipe. Jumbled up bits of data and code from the time the phone was new until now are most likely the culprit for the bootloop. I would say now would be a good time to root.
At least then you can make backups and not have to lose everything.
First, I will say that i'm not a developer. I am familiar with backups, rooting and custom roms. I'm just at a total loss with a total loss phone :/
So here's the rundown of my issue/s with my Moto Turbo (XT1254)
The phone is completely "unmolested." My phone is stuck in boot loop, currently. I did bust my screen a few weeks back but it had been working just fine. I picked up my phone to check texts, and I saw the "updating 24 of .... apps." Once finished, it's been stuck in a boot loop since. (Odd thing, my screen now shows split Moto image when trying to boot. Ex: a slot machine with only 2 roller wheels that wont match up)
I have tried to clear the cache several times with no luck of it booting up correctly. I do have files that I was trying to recover since they are not linked to a cloud account, and was trying to avoid a full on reset. I did, however, get frustrated and even tried to reset it back to full factory settings. That did not work either. So, all this being said, I'm back to trying to recover my files (my daughter's first year of life, family stuff, etc), since I cannot get it to even preform a factory reset. Does anyone have some guidance or same issue on this matter? Again, I am trying to salvage my files now while stuck in soft brick / boot loop status.
Thanks any and all who can help me with this!
******* Solved********
I have better diagnosed and fixed my own issue. I'm sorry I don't have pictures or video to better document what I did, but in short, it was as simple as replacing my damaged screen/digitizer, with a new one.
My theory was that during the update, the phone checked over it's systems and found that the digitizer was non-responsive in a few very small areas (this I already knew from using it a couple weeks with the screen damaged) and it somehow caused it to go into a boot-loop. My experience with fixing Playstations 3's, helped shed some light on this for me. I had a PS3 i thought was in good working order, updated firmware to it, and it bricked the system. Come to find out, the blu-ray laser head was no good. Upon the firmware doing system checks, it found that was bad and ended up bricked.
I did replicate the problem by switching the broken screen and new screen back and forth 2 more times after the initial fix. Upon disassembly, (youtube for teardown vidoes) you disconnect the battery from the logic board anyways, so when you boot the phone up, it does a app check and system check again. Every time the damaged screen was connected to the logic board and then powered on, it would end up in boot loop. The new, undamaged screen, would do the required checks, then boot up like normal.
I will do my best to borrow/rent a camera soon, so I can make a short video to show this works.
I'm not going to promise this will work for everyone but with replicated results, hopefully it's a fix for someone!
I hope
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Note 5 crash
Yep, have the same problem, but I have not attempted to Flash the Phone yet...
Did multiple factory resets, clear caches... but to no avail. There is no structure or pattern in crash rate. Although it is getting more often day by day...
Found no working sollution, but it feels like there is a bad memory segment or something. Everytime it randomly uses that segment... crash!
Really don't know. Will try to get warrenty fix.
Let me know if you found a sollution on your side?
Cheers,
Wim
kbiscu1t said:
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Click to expand...
Click to collapse
OP here. Made a warranty claim, they seem to have replaced the motherboard as the solution. Complete repair experience from warranty claim to package back at my doorstep was less than two weeks, which is impressive for what I've heard about Samsung's support. Good luck!
Hi Guys,
I have this phone for many years, but suddenly the random reboots started approx 2-3 months ago, running originally KitKat 4.4.4 at this time. Before that I was rooted the phone and I supposed it could be something with that. However, flashing back & factory resets didn't help at all, clearing dalvik caches as well. What I tried up to now:
1. Upgraded/Downgraded the bootloader -- no change
2. Tried different recovery modes -- CWM & TWRP(the current one)
3. Different ROMs -- no change, the sudden restarts persist.
(4. Updated the radio -- the signal got quite better)
Three days ago I've upgraded to Lollipop 5.1.1 (the Cyanogenmod 12.1), the same story continued after a while (different applications installed).
There's one thing for sure: flashing the factories always results into a very stable phone at the beginning, installing some more applications leads to the same state -- random and frequent restarts.
I've checked the hardware -- the power button looks ok, it's definitely not the main cause b/c it reboots without touching! The CPU temp & free memory look quite good too.
Now, the current situation is as follows:
- flashed ROM (official one): 2016-03-03 Poland (T-mobile) 4.4.4 I9305XXUFOL2 I9305TPLFOL2 (seems like the most stable till now)
- installed ATK (Advanced Task Killer) -- configured to kill all applications aggressively when the screen goes off.
For me it looks like the ATK helps much, although I don't know the reason. Also, memory checked, I've executed all kind of possible tests up to the phone -- all appears as OK. Also, I don't know if it's related to the issue but I moved all possible apps installed to the SD card. The internal memory has been formatted via TWRP before the last ROM installation... Does anyone have any idea what could be the reason for the sudden restarts? It restarts even in Safe Mode, without any obvious reason and not touching the phone at all. The CPU load at the times of restart is quite low, the temperature as well. I doubt if the RAM is corrupted or maybe the NAND has some bad blocks. Are there any useful utils for tests that could be executed?
PS: I attach some log file, which I gathered once I was running the Cyanogenmod 12.1 (Lollipop). As I stated above the situation is the same when running 4.4.4 and 5.1.1. Sometimes after such a restart, it sticks in a boot-loop (if I boot manually via the GUI in recovery or download mode it will not).
Current versions:
---------------------
Android: 4.4.4
Baseband: I9305XXUFOA1
Kernel: 3.0.31-4282983/[email protected] #1
Build: KTU84P.I9305XXUFOL2
SELinux: Enforcing
Recovery: TWRP
I beg for your help on this! Cheers!
Same problem here...
Hi there
I'm having this same annoying issue with my Samsung GT-I9305. It suddenly restarts without doing absolutely nothing but looking at the screen or scrolling a text or just sending a sms/whatsapp/whatever.... I started trying to restart the phone (nah) turning it off and back on (nah) changing the battery for another one that I have here with me (nah)... After that, I extracted the SD Card and leave the phone only with internal storage (again, nothing happened but restarting randomly). I tried not installing apps such as FB, even Pebble App or just stopped sycronizing my phone with my Pebble Time via Bluetooth, but with the same and well known result: still restarting suddenly. I have noticed that when Google Play detects that there are few apps with a newer version asking to be updated, the phone restarts too! I tried deactivating this option in Google Play, just letting me to decide when and how to upgrade my apps, but It seems that it still detects the app upgrading needs and keep doing it the same way.
About a year ago, I found the same problem with my phone, but in that time it was related to the power button, it seems that it was pressed all the time and the device felt into a rebooting cycle. I check some blogs and I solved the problem cleaning the button with this electronic cleaning spray. I almost drowned my Samsung but I let it dry for a few hours. It worked fine, until now.
My cellphone is still in Android 4.3 (I9305ZHUCNB1) I don't know why I can't upgrade it to a newer version, even when I see that the 4.4 is available for this model. Right now, I'm thinking about change the cellphone and just forget the whole problem. But I'm just exploring again to see if I can find a last solution that tackles this annoying issue.
Did you manage to solve this problem??
Thanks in advance!
Unfortunately not, I had to buy a new phone. I guess the processor or other element suddenly broke, there's no other explanation to me. Also, as you see no any reasonable support in the forum.. Anyway, wish you a good luck with this.
Not so good here too...
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
fjpp81 said:
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
Click to expand...
Click to collapse
Sorry for bothering this thread also... I got success by replacing the display!
Hi guys. This issue just started happening a couple of days ago, it started when I was playing games (phone wasn't hot) then it turned off by itself. My battery was still at 80% so I turned it back on, after it started saying "starting apps" it turned off again and the phone is now constantly rebooting. It doesn't seem to be bricked at all as it sometimes boots to the menu but when i start tapping on an app it shuts off and does the constantly rebooting issue again. It could be a hardware issue which means I'm gonna need to send my phone to the service center for a repair but one thing that makes me think there could be a way of fixing this without paying a technician is, when i boot to download mode, it doesn't do its constant reboot issue. I was even able to flash a firmware via Odin but when the phone started to boot after firmware installation, It did the spontaneously rebooting in the middle of the boot process again. If any of you guys have any idea on how to fix this or if there's even a way to, Please help me. Thanks! Cheers!
junnelle said:
Hi guys. This issue just started happening a couple of days ago, it started when I was playing games (phone wasn't hot) then it turned off by itself. My battery was still at 80% so I turned it back on, after it started saying "starting apps" it turned off again and the phone is now constantly rebooting. It doesn't seem to be bricked at all as it sometimes boots to the menu but when i start tapping on an app it shuts off and does the constantly rebooting issue again. It could be a hardware issue which means I'm gonna need to send my phone to the service center for a repair but one thing that makes me think there could be a way of fixing this without paying a technician is, when i boot to download mode, it doesn't do its constant reboot issue. I was even able to flash a firmware via Odin but when the phone started to boot after firmware installation, It did the spontaneously rebooting in the middle of the boot process again. If any of you guys have any idea on how to fix this or if there's even a way to, Please help me. Thanks! Cheers!
Click to expand...
Click to collapse
Try flashing the experimental firmware from the rooting guide, and if that doesn't work then it is most likely a hardware issue, and I have a strong suspicion that it is.
If you have an external SD card, remove it and see if problems persist. Honestly that sounds like a firmware scrambled.