I am curious if this has been happening to anyone else. I am using the ROM Galaxy Note 5 OGD Deodexed Stock Rom using Xposed Framework and Wanam Xposed. My kernel is the BeastMode Kernel with the new TWRP that supports our phone and everything runs smoothly on my phone and when I restart it sometimes it reboots flawlessly..... and sometimes when it reboots it hangs at the Sprint Spark screen forever. I go into my recovery and wipe the Dalvik Cache and normal cache and reboot it a couple times until it eventually gets passed the sprint spark screen and begins to optimize my apps. Is there a reason why sometimes when I reboot everything just stops working and other times everything is working flawlessly I am not changing around anything in the Xposed framework or modifying any settings. It is just sometimes hit or miss on my reboots and I don't know why. If there is something I missed that the community here has announced about this issue I apologize I just feel really confused and cant find any talk about this anywhere.
innocentone1 said:
I am curious if this has been happening to anyone else. I am using the ROM Galaxy Note 5 OGD Deodexed Stock Rom using Xposed Framework and Wanam Xposed. My kernel is the BeastMode Kernel with the new TWRP that supports our phone and everything runs smoothly on my phone and when I restart it sometimes it reboots flawlessly..... and sometimes when it reboots it hangs at the Sprint Spark screen forever. I go into my recovery and wipe the Dalvik Cache and normal cache and reboot it a couple times until it eventually gets passed the sprint spark screen and begins to optimize my apps. Is there a reason why sometimes when I reboot everything just stops working and other times everything is working flawlessly I am not changing around anything in the Xposed framework or modifying any settings. It is just sometimes hit or miss on my reboots and I don't know why. If there is something I missed that the community here has announced about this issue I apologize I just feel really confused and cant find any talk about this anywhere.
Click to expand...
Click to collapse
This happened to me on my Note 4 when I dirty flashed a ROM. My recommendation would be to do wipe and clean install of the ROM you are using, unfortunately. I missed my alarm (luckily my SO's went off) and nearly missed work due to my phone restarting and hanging on the Spark screen. But usually if I soft reset (power+vol down - or battery pull in my case on the N4), it would get past the spark screen. I haven't ROM'd my N5, but that was my recently past experience.
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.
Starting on the first week of 2019, I have experienced problems with my Tab3 7 Essentials tablet that I bought 7-8 months after its initial release. I enjoyed it until that following day.
The problem first started after I am updating some apps from Google Play Store. I tried to update it, but got an error of -504 after 5-10 minutes of trying to install (not downloading from WiFi). One reviewer even said that the same thing happened on his device which runs Android 5.0.
I tried numerous apps to install/update, but the same problem, even for the apps that are not installed yet. I restarted my tablet.
The tablet went to the manufacturer bootlogo (right after the initial bootscreen with "Powered by Android" text) and instead of taking the regular time (about 15-40 seconds), it went up to about 7 minutes of the bootlogo to just start up.
I then tried to install/update my apps again, but this time, Play Store gave me an error of 910 (again install). Even Play Store is unable to update itself, but it either gives up and makes me unable to open Play Store until I restarted my tablet, or the tablet automatically restarts which took about another 7 minutes. What's weird is if the tablet has automatically restarted (soft reboot) because Android crashed, the logo doesn't show up but it boots up normally.
Also, my apps are soon going to be dependent on Lollipop and above, by making them incompatible with Jellybean, or my apps that I'm going to install isn't compatible with Jellybean.
I scanned my device for suspected malware by Malwarebytes, but nothing is found except one of the system apps (related to system update) that has Adups. None of the ads show up yet.
My firmware is updated to its latest version, if it helps. It originally came with the S00025 firmware and I'm running S000028. Each upgrade took around 30-35 minutes to optimize all apps with the black screen.
I knew that Lollipop should run correctly, because I have another tablet, which runs Jellybean, that works correctly except the ghost touch issue. Is there any solution to get out of this problem where I can't install some apps and the tablet taking around 7 minutes to boot up?
Sent from my Lenovo TB3-710F using Tapatalk
Bump.
Sent from my Lenovo TB3-710F using Tapatalk
slow boot Tab3 7
tried volume UP + power and reseted cache -> no changes
EoflaOE said:
Bump.
Sent from my Lenovo TB3-710F using Tapatalk
Click to expand...
Click to collapse
finally reset to factory solved issue - booting 35 sec
nEON7T said:
tried volume UP + power and reseted cache -> no changes
Click to expand...
Click to collapse
Pardon for a long story but someone gave this Samsung J7 Prime(SM-G610F) to me with an issue "An Error Has Occurred While Updating The Device Software". So I gave Samsung Smart Switch a try sadly they removed the Initialize option and old version don't seam to do what it suppose to do so I wen to a traditional Odin flashing. I then look for a stock rom for the phone that I think is the right one. Started with android 6 MM region pakistan and flashing went well. I was able to use it for a good hour or two until I notice it restarted by it self, then it keeps doing it 10-20 seconds after booting up. I though its the firmware I'm using so I went and look for Oreo version this time I region india (I don't know if region matters). So I flashed it again and tested the device again. I'm still able to use it for a good while till it restarted again. I then keep testing it to see what may be causing the problem. I notice that when the WIFI is on it just crash the phone to reboot so as soon as the phone reboots I turned the wifi off and it didn't crash anymore. I then factory reset the phone cleared everything, wipe cache then installed benchmark tools first. Thing I notice is it crashes when Google Play store is trying to install or download something. I tested it a couple of times to see when it crash and it does crash when downloading or installing something. I was still able to install 3Dmark and run it with wifi off. It completed the test without crashing so it couldn't the processor issue. I then look for another rom and tried flashing it. This time I had issue with it failing at system.img even if I use recent rom that worked. I then keep trying till flashing TWRP worked and flashing the rest of the rom is fine again.
What bothers me is why doesn't it crash during the first couple of hours. I've search similar issues and they say it may have been and app issue. I've already disabled bunch of app but nothing changed. Run the phone in safe mode but this time instead of crashing and rebooting right away it freezes for a few seconds. I suspect if google play or something being an issue since I've tried disabling it and it didn't crash for a couple of hours. Looked for allot of related thread but none of them seam to solve my problem.
I suspect either its the rom that I'm using and it can only be fixed by using the original rom, or its having a memory issue but don't know how to pin point it. Anyone can suggest on how I can debug this? I'm used to debugging things in real time and my knowledge with android is a quite slim but as a programming understanding the errors won't be a problem. I hope.
Edit: Hmm. Does copying kernel log with TWRP work or the kernel logs get overwritten every time the phone reboots? Because I see the kernet logs but don't see anything failing except for something saying SHUTDOWN but I don't think thats it. :S
Still no reply. :S I think its /system dismounting it self while doing a write operation. but it doesn't trigger until a certain amount of time after the phone is flashed or factory reset. I have to go to recovery and mount system back but that only happens on marshmallow. over version it remounts it self after the random reboot. After factory reset I'm able to install COD mobile and play a couple of match. after a long while it just decides to reboot.
I also tried z3x and after reading PIT from phone OK. the phone just reboots and flashing completes without it doing any flashing.
So summary
OOS 9
Magisk 19
Disabled I think is quickswitcher module
Now I just get animation going forever on booting, if I leave it long enough about 20 minutes or so, it reboots itself and goes back to loop.
TWRP is accessible.
I tried MM recovery tool in core only mode but still doesnt boot.
Ideally I need a solution that doesnt involve a factory reset.
Ok the core only mode didnt stick I think, so did it again and the phone is booted.
With no phone app , completely gone off the phone.
It shuts down after about 20 seconds after booting up.
Backing up what I can over USB from TWRP, and this might force me to migrate to my Oneplus 8 pro which has been sitting in its box, but I will still appreciate any input on how to get this running again without a reset so I can properly migrate app settings etc even if its losing magisk.
I managed to keep the phone bpoooted up for ages, and have done things like titanium backups, app setting backups etc.
I then tried to reinstall the phone app from the play store but got a vague "cannot install phone from google".
But at least now I can access settings etc. Take screenshots of settings also. So better baseline for the new phone.
Pretty crazy how all this broke so easily though.
So I dont know how this happened but I managed to recover the phone.
The xXx rom magisk module got wiped when I deactivated the recents module, this removed the google dialer framework and some build.prop changes the rom module puts on the phone.
I initially just added the framework magisk module which allowed the google phone app to reinstall, all my call logs were intact. But the phone was still unstable on booting so had to reinstall xXx which seems to have fixed that, albeit now with added lag.
But I have backed up everything now anyway so will migrate to my newer phone its long overdue, but this post is here now in case anyone else has the same issue.