Guess I need to ask for help/idea's.
If I upgrade my "4.3/101" installation to 4.4/230, everything initially works, and then at some point (after a few days) I start experiencing spontaneous reboots. I thought perhaps it was an issue with xposed... so I tried doing this again but removed xposed from my phone prior to upgrading and re-rooting... no real change.
I tried doing a wipe/clean install and then restoring applications & data via TiBu... still have the reboots
I've never had this particular kind of issue before... I expected that a clean install and restoring some key applications via TiBu wouldn't have this issue...
I'm game to try another clean install without restoring anything via Tibu if that would really help...
Is there an on-phone logcat tool that will automatically store logs to my sdcard?
Any other idea's about what might be going on?
Hmmm...
Zero responses, but several views.
Figured out (after looking elsewhere) that I could pull a last_kmsg among others...
Logcat
dmesg
last_kmsg
Can anyone give me some idea's about what's causing my phone to restart?
Just remembered in an attempt to get a different result, I'd actually flashed Gustafo's kernel... hmmm... wonder if I'd get the same results on the stock kernel...
Seems like after a clean install, it's working fine - I'm suspecting this might be some sort of issue with Xposed....
we'll see if it re-manifests...
I just had the same issue fixed. I've had a constant reboot approximately 30 times a day.
I wiped everything including internal SD card, and flashed the 4.4.2 firmware. I was suspecting the Xposed as well but I installed for the heck of it 5 hours after the flesh installation of firmware. I only needed the wakelock terminator for Xposed to prevent battery drain.
After 48 hours even with Xposed, there has been no single reboot so far.
Related
I'm beginning to notice a problem with my EVO of lately, Sometimes when I wake up the phone and then unlock for the lock screen it just reboots itself. I thought it was due to a custom ROM but this has happen with all the ROMs I installed on my phone (Fresh, DC & OMJ). This problem started to happen when I updated to the latest firmware from sprint. I had a hell of a problem regaining root until there was a proper method released by the geniuses in our community. I'm not sure what is going on to cause this and would like to know if anyone else is experiencing this and if so how did you resolve it.
Have you tried wiping and flashing the stock rom just to make sure? Also, if it happens consistently, you could try running logcat and see if you can track down the problem.
elegantai said:
Have you tried wiping and flashing the stock rom just to make sure? Also, if it happens consistently, you could try running logcat and see if you can track down the problem.
Click to expand...
Click to collapse
Actually I did wipe and try a rooted stock ROM but I didn't run stock too long to notice the random reboot problem. I ran logcat but couldn't figure left from right when looking at this thing. I attached my logcat. If you or anyone else on this forum could take a look, I would greatly appreciate it.
Does that logcat include a period where there was a random reboot?
I'm on DC 3.2.3 and with JIT enabled I get the occasional random reboot. Seems to usually happen when I'm typing.
I usually get random reboots in areas with no signal, i remember reading somewhere it was because the battery got too hot... but ever since i loaded an fps "fix" for my phone, i haven't had one, and it's been two weeks
So I have been using this feature of Rom Manager quite a bit lately. I've been getting random fc's on apps and core processes over the last few weeks. Clearing data etc never works but fixing permissions solves the problem every time. My question is why? What is happening to the permissions that they need to be fixed? Most recently I installed Honeycomb Fusion and I couldn't add new contacts due to an fc in android.process.acore. Is there a way to defeat this bug before it happens...as in would it fix it if I wiped and returned to stock and then installed my rom and mods? Or would a full factory reset be required? It isn't a major issue but I am curious.
Yes wiping will help most of the time. Never pull your battery before the vibration signal, and get rid of ROM manager. It does not work with Epic according to Developers here.
Do you BONSAI?
As for why the permisssions need fixed: IDK
However the force closes happen when u have corrupt data from an app (IE: Wifi tether 3.0.0 versions) or powering off incorrectly with a no journal rom.
If ur using wifi tether 3.0.0 version, even if it does not reboot ur phone it can and eventually cause corrupted data.
If ur shutting off ur phone incorrectly:
1. 4 button boot into clockwork while phone is on
2. Battery draining and phone shuts off
3. Pull the battery while its on
4. reboot the three finger combo while phone is on
All these can cause data corruption or a certain app can cause it.
Well I am on Bonsai 4.01 and I believe it is still journaling off...I haven't restored a backup since flashing. I always use the power off option when rebooting just to be safe. I have only pulled the battery once and that was long ago and it didn't help the issues I had then...and have reflashed from scratch since then. As far as Wireless Tether I do have it installed but only tried to use it once several months ago.
I only keep Rom Manager since I paid for it and it has the fix permissions option...I know there is an option in CWM but the RM option seems to work fine. I don't use it for anything else.
I have read around regarding this problem without luck, and hope that someone can advise if I have missed anything.
I used to use this phone and as I liked to tweak it was running a custom rom (think it was Wanams). Anyway I got an upgrade ages ago, and my wife carried on using the phone for a while. As she just needs a standard rom I recently decided to factory reset and use Odin to flash the newest stock rom (N7100XXUFNE1 - UK). This is when the problems started. Initially the Wifi wouldn't come on, but after factory resetting and using the Samsung Updater in Kies I finally managed to get Wifi back. Then, while setting it up and installing apps from the Play store it started freezing and had to be rebooted every 5 or 10 mins. Finally after doing this a couple of times, all the apps were installed and after leaving it to "settle" it seemed to be better. Now however, 2 or 3 times a day, when playing games or using other apps, it will just reboot.
What I have tried is:
* I have tried clearing cache through the stock recovery
* Tried a number of Factory Resets
* After reading about the SDS problem I have tried running the "dummy file generator" to fill the internal memory and this completes ok. I guess this means that although I have memory that is/was susceptible I applied the original SDS fix early enough with the custom rom that all the memory is still ok?
As I have the newest bootloader I can't downgrade that, but as I don't care about triggering Knox I was thinking of rooting and installing a custom rom to see if any of the other Kernels help?
Has anyone got any idea's what could be causing this and what I can do to fix it?
Thanks.
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Might be quicker and easier to back up your required files and just factory reset.
Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.
somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good
somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.