Hi there,
I am very happy with my Moto Z, but since about 8 weeks the phone keeps randomly rebooting, even over night when I don't interact with the phone. I did already a factory reset, installed less applications as before, but after about one week the random reboots returned. Does someone else also have this issue, and has probably a solution?
Some system details:
- Moto Z, Andoird 7.0 (stock), reteu
- Build NPLS25.86-31-5
- Baseband M8996_1239.53.01.12R SRS
- Kernel [email protected] #1 from 30/03
I fear everything started with the first 7.0 update installed via OTA. I know that safe mode is often suggested, but then I can't install any application for about one or two weeks to check stability. That's actually a no-go for me.
Best
subwayne
Related
So I had this SGP321 for over a year now.Bought it brand new from this guy on the internet for a suspicious low price.Not a real shop or anything so no waranty. It worked very well for a few months then I noticed it started rebooting every now and then.After a OS update that was rolling out at that time (can't remember the version) the reboots were more often.After the KitKat update arrived and I downloaded it,after the process was over and the phone had to reboot,it entered a reboot loop that could not be stoppped (apart from forced shut down,but with same thing when trying to turn back on). I repaired the OS with the PC tool,no changes.I flashed older versions of stock OS with flashtool,reboots every couple of minutes. Then I installed Cyanogenmod 11.That worked very well,no reboots,but had many bugs and battery draining fast in stand by (about 1% per hour no matter what I deactivated,or with various apps to induce deep sleep). The new CM12.1 does not work,keeps rebooting.
Now,yesterday I tried again and again to get the tablet to work with a stock ROM. I only intend to use it for reading comic books,so all I want is a stable ROM with good battery life.So I would like to have a stock one. But why does a custom one run fine on it and a stock one keeps rebooting? I tried Sony forum but they were at a complete loss and sent me here for help.Any ideas?
rammstein_08 said:
So I had this SGP321 for over a year now.Bought it brand new from this guy on the internet for a suspicious low price.Not a real shop or anything so no waranty. It worked very well for a few months then I noticed it started rebooting every now and then.After a OS update that was rolling out at that time (can't remember the version) the reboots were more often.After the KitKat update arrived and I downloaded it,after the process was over and the phone had to reboot,it entered a reboot loop that could not be stoppped (apart from forced shut down,but with same thing when trying to turn back on). I repaired the OS with the PC tool,no changes.I flashed older versions of stock OS with flashtool,reboots every couple of minutes. Then I installed Cyanogenmod 11.That worked very well,no reboots,but had many bugs and battery draining fast in stand by (about 1% per hour no matter what I deactivated,or with various apps to induce deep sleep). The new CM12.1 does not work,keeps rebooting.
Now,yesterday I tried again and again to get the tablet to work with a stock ROM. I only intend to use it for reading comic books,so all I want is a stable ROM with good battery life.So I would like to have a stock one. But why does a custom one run fine on it and a stock one keeps rebooting? I tried Sony forum but they were at a complete loss and sent me here for help.Any ideas?
Click to expand...
Click to collapse
Seems that it has hardware problem like corrupting internal Flash memory or smth else, that is very difficult or imposible to fix by reflashing.
I have a VF-895N (rooted and stock rom - update 130FFN2), yesterday I decided to update my phone from 5.0.2 120FFN2 to 5.0.2 130FFN2, I removed root and made a hard reset, started the update process but at the very end of the update, it said "error", then I got stuck into a bootloop " no command" but managed myself to re-flash stock rom already updated with the latest version. When it finished flashing, I booted up the phone, started to remove bloatware, rooted the phone and started to install apps like Facebook, Instagram and other stuff like that.
I finished installing all the apps I wanted but I noticed my battery was draining very fast and also my phone was overheating, I tried to open Instagram for the first time but it freezed, tried the same with Facebook, it freezed.
Overall the phone's performance was very bad comparing with the one I had before re-flashing.
Now I don't know what to do, some apps close or freeze, the phone does not overheat much now bcuz I installed setcpu and set the values to min.=240mhz and max.=980mhz tho I don't understand much of these things... (Initially the values were 1.020mhz of min. And 1.020mhz of max.
I did hard reset 3 times and I always got the same result and I also cleaned the cache too.
I can't downgrade bcuz there is no stock rom available anywhere except for a flash tool (Sugar QCT) that flashes the latest update, which I already have and seems to be broken.
Please help me.
Hello guys,
This issue has been haunting me. Whenever i try and pair my device it freezes the phone and after about 5 seconds, it restarts the device. The weird thing is, it doesn't ask me for my SIM pin which is enabled. So i'm thinking it's a soft-boot (is that even a thing?).
The watch is useless at the moment.
It's worth noting that it works fine with CyanogenMod 12.1.
Logcat logs can be provided (can't post because it's too long).
Things i've tried:
-Install older version of android wear.
-Clear cache.
-Manually pair watch via Bluetooth settings.
Device: Moto X 2014 victara.
OS: CyanogenMod cm-13.0-20160508-NIGHTLY
Watch: Moto 360 2n Gen.
Android Wear version: 1.5.0.2714488.gms
Any help is greatly appreciated. Thank you.
I am having this exact same issue. Yesterday I flashed the latest nightly of CM13 for my device. I flashed it clean coming from the last CM12.1
Right now I have the watch connected to my phone manually via bluetooth.
I've tried the same things you have without any success.
Device: Nexus 6 shamu
OS: Cyanogenmod CM13.0-20160605-nightly-shamu
Watch:LG G watch
Wear version: 1.4.0.2576000
Same issue
Guys, did you manage to fix this issue?
On a OPO CM13.1 and on restored backup to 13, I too having this issue with a moto 360 g2. Factory reset watch and still android wear crashes the phone on pairing. Worked great for 6 months until I down graded Google services due to battery drain issues, and now can't get wear working again.
Any suggestions on fixing it would be gratefully received.
So, since the past few days my i9300 keeps randomly rebooting. At first it was not that much of an issue but today it started to go into a boot loop.
Sometimes it finishes booting but before I can go into the settings to factory reset it, it crashes.
I also tried to get into TWRP but as soon as the logo shows up, it crashes.
I can't even use the download mode because, guess what happens: it crashes.
I really don't know what to do right now. I still have a spare motherboard but I'm not able to access it for another week. It would be a shame to throw away a perfectly fine motherboard if it is just a software thing.
Currently it is running the last version of SlimKAT that was released, I don't know which version of TWRP it is running, but I updated it just a few weeks ago. It is not using the original battery fom Samsung but one from Anker which should be fine.
If anyone needs more or specific information, I'm more than happy to provide it.
Hi,
just want to ask, you're stuck in bootloop at the "samsung" Logo or where?
Because I am having bootloops, too since 2 days. Phone kept restarting one or 2 times since last 3 days and when i got home on 1. november i put my phone to the charger and got back 20min later and saw it was rebooting.
Mine is stuck in optimizing apps or if i wait long time then it is at starting android: starting apps and i see when the color temperature of the phone changes (i think of the light sensor) it gets stuck and reboots.
just for docu (even if its not the same problem):
i have a 2nd spare s3 for testing here and to test ag. hardware issue i made a twrp backup and both are dying. after facory reset and installing apps i recognized that it is dying at the installation of telegram app and after that its going to the same bootloop on both phones. i checked telegram and seems to fit in, they updated their app at 1. november. and date code of last changes before the bootloop: telegram was modified. so for my problem it seems to be caused by telegram.
I am using bliss rom 6.1 (Andoid 6 Marshmallow, CM13 based) at i9300
sorry for maybe not beeing a help. I now found out that it happens to other app installations, too. so seems to be a problem deeper in android/interfering with this specific rom - maybe its play store . So far since it happens on 2 identical s3 with this rom I will have to change the rom now. :crying: (was stable >1year)
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Niggyminator said:
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Click to expand...
Click to collapse
good luck!
But if you'r stuck at the samsung logo, sounds even worse than mine. if your having a new board could at least be an option to check if its really not a hardware issue (you mentioned that its getting again unstable after some time)
for my problem I managed to backup most things out of the nandroid image and moved to ressurection remix with android nougat. the new rom is running fast and so far without any problem - hope it stays like that .
Hi all!
I have already commented on a opened thread about this problem but, as it was a similar, not exactly the same problem, I decided to make a new one, and delete the comment. I tried to install AOKP osprey nougat on my Moto G 2015. It installed with no problem at all, I installed it with Magisk and OpenGapps micro. But, as soon as the phone turned on and I started to go through google registration stuff, I started get a "advanced settings has stopped" with a close button. It was happening forever. I could fast click close and do one click on the phone but the error message was popping up every second. It was unusable, forcing me to not use aokp custom rom. I'm waiting for a new release. U guys do an awesome job and I would love to be able to use it on my phone...
Ty.
:crying:
Hello again guys! A new aokp Osprey version has been released in 05/23. I tried it in my Moto G 2015 that was running LineageOs with no problems. Just like the older ones it installed fine with gapps. But the further problems that I had with the older versions happened again. In the first boot, after installation, the popup error, that I talked about in the previous post appeared, but, this time I managed to get rid of it by just closing it some times (approx. 20x), so then I could login to my google account. In this first boot the phone was working fine, I installed some apps, changed some configs, and it seemed to be working ok. I decided to reboot my phone for testing purposes and here is where stuff broke again. The same error popup that I talked about, but now even with me closing it for at least a hundred times the popup was showing everytime. So, saddly, I just had to return to LineageOS.
That's it, bugs are still happening... But keep up with ur good work and, hopefully we will have some amazing Osprey ROM in te future.
Same bugs...
New ROM (aokp_osprey_nougat_nightly_2019-06-06_ota.zip), same bugs...
I'm giving up on AOKP for now...