Database Users

Random reboots - help needed

Hi,
I have problems with self reboots of my X8 since I got it.
I had problems with stock ROM, upgraded stock ROM and all custom ROMs and kernels.
I couldn't find any pattern why and when is this happening.
sometimes it doesn't happen for weeks (at least I don't notice), and then it starts happening every few minutes, and then it slows down again.
only pattern I noticed is that since I flashed Alfs kernel, phone reboots when I try to make skype call. but this is probably complitely different problem.
full wipe or ROM reinstall helps to slow it down if it is happening to often.
I would really like to find out what is causing this.
today I noticed than phone rebooted while standing still on the desk. after it booted I entered terminal emulator and wrote this:
su
logcat -d > mnt/sdcard/logcat1711.txt
dmesg > mnt/sdcard/dmesg1711.txt
I hope this is the right way to do this cause I don't understand much this logcat and dmesg or linux in general.
logcat and dmesg are always written in some kernel buffers? when I write this I only print it to txt document? How long to history is always written it those buffers?
OK. the real question is can somebody take a look in these documents and see if some conclusion what causes self reboots can be made from them.
Thank you!

Razr M keeps rebooting

I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).

rocksolidsr said:
I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).
Click to expand...
Click to collapse
could be a ROM/Kernel pairing. have you tried wiping system/data/internal storage - reboot recovery, then flashing a new ROM?
the static screen is common on custom 4.2.2 ROMs, but it's usually a quick flash. I don't get any random reboots though.

I've tried many different rom's along with the Vanquishkitties kernal but still random reboots

I noticed my phone acting weird, specifically it would not play any audio, I noticed this because when I was in the dialer it was going really slow. Then I tried to play some notifications and none worked. I rebooted my phone and all seemed ok, I've attached two logs the first one being while audio would not work and the second after the reboot. I'm not really sure what to look for in the logs but thought someone here might.

This might be something...
E/AudioStreamOutALSA( 300): pcm_write returned error -5, trying to recover
Or this, just a warning though...
W/AudioTrack( 692): obtainBuffer timed out (is the CPU pegged?) 0x63d72108 name=0x6user=00001000, server=00000000
Sent from my Nexus 7 using Tapatalk HD

Just noticed that when in the dialer and the phone starts working very slow, if I turn the sound all the way off, the phone becomes responsive

two more logcats for anyone interested in helping this time one is when trying to use google voice actions, I actually get an error message that says can't open microphone and the other is when someone called me and I did not have any ringtone but I answered and I could not hear them and they could not hear me, shortly after my phone rebooted, I did not catch the reboot in the logcat.
Also when it reboots it doesn't reboot all the way it boots to the boot logo screen and then hangs and I have to hold all three buttons until it reboots again, is there a way to get it to just reboot on its own?
After the reboot everything seems to be fine until I experience the same issues again

Which ROM are you on right now? That sounds like a kernel level issue
Sent from my XT907 using Tapatalk 4 Beta

I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.

rocksolidsr said:
I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.
Click to expand...
Click to collapse
Has your issue been resolved? I am almost facing the same issues of random rebooting with my phone and was searching for a solution....

Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?

5318008 said:
Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?
Click to expand...
Click to collapse
Im having this issue and Im on kitkat.

Deleted

Deleted

SirOxyGems said:
Good day, This is my first time ever posting a thread on this site and new to custom ROMs on Android devices. I currently have Samsung Galaxy Note 4 (T-Mobile) and a friend suggest I flash it with some custom ROMs. I did, indeed, tried all the compatible ROMs for this phone and they all boot up find (despite the long hang time after finishing the boot setup), but I ran into some problems after doing everything, step-by-step, correctly. I've done light research on how to fix these issues but was afraid if my phone may brick again and do another Emergency Recovery using Samsung Smart Switch. To get to the point, the following issues that are occurring are these below,
- WiFi continuously says "Wifi turning on" and never stops
- Settings will sometimes crash when entering "Security" and then backing out of it
- Camera quality remains blur and can't find any settings to get the camera to focus properly
- LTE/Mobile Data does not apply on boot (when restarting or turning it on) and it requires to fully reboot again
- Uninstalling a application forces the phone to do a soft reboot
- Sometimes multiple background apps will pop-up a error message stating, "Unfortunately, (App) has stopped"
I currently have the Resurrection Remix v5.7.1 (which is the latest I've found) build on the phone, but at the moment using Stock Marshmallow as I'm witting this. If there is anyone on the forums that can help me resolve these issue so i can have a stable flashed ROM, I would greatly appreciated the help. Thanks for your time and have a bless day.
Click to expand...
Click to collapse
Did you have all of these issues on every ROM that you flashed or just a specific ROM?
Sent from my Nexus 6 using XDA-Developers mobile app

Deleted

[Q] Systemless Root causing boot loop - T-Mobile N900T

Hey everyone.
Like many Android users, I've been struggling to find a ROM and systemless root combo that passes SafetyNet (ever since Pokemon GO 0.37 update). I eventually found a ROM that can be unrooted cleanly (AryaMod S7 Edge port), and managed to get SafetyNet working via Phh's Superuser (first with Magisk + r251, now using hidesu version r266).
However, I soon ran into a problem: The systemless root appears to be causing my phone to bootloop. There seems to be a gradual degradation of the bootimage somehow caused by systemless roots; my phone would work fine for a while, then gradually apps would force close or the phone would freeze. If I try to reboot, the phone then gets stuck in a boot loop (which occurs before the ROM even starts loading). I am very sure this is caused by an error in the bootloader because this bootloop behavior persists through nandroid restore or clean ROM installations. The only way to fix it is to flash the stock bootloader via ODIN.
I noticed a few users in the dev threads of ROM's I've tried reporting the same issue, but in the dev thread for Phh's Superuser there seems to be a lack of mention of this issue (likely model-specific, as I am using Phh's Superuser on my wife's Note 4 and her phone isn't bootlooping). Just wondering if anyone has experienced the same problem and found a solution?

Try the TMobile forum .
Sent from my SM-N930F using XDA-Developers mobile app

I also have an N900T, and magisk v7 + phh is working fine for me if I don't install any extra systemless modules. When I installed the better battery stats module, I started getting bootloops, so there are definitely some issues with it.
Magisk is still being worked on, so it's probably only at alpha or beta status right now. Hopefully it will get more stable in the future.
btw.. I'm running the latest stock Samsung 5.0 rom (N900TUVSFPH3), which has the latest bootloader, since it seems the most stable to me.

(Magisk) Phone randomly stuck on boot issue

Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?

Happened to me too. Got rid of magisk for now so running stock un rooted until this gets sorted. Haven't ran into the issue since un rooting.

BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.

Rowdyy Ronnie said:
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.
Click to expand...
Click to collapse
I flashed 16.0 too, but I have to say the issue became real even before I installed Xposed. Guess it's something Magisk-related

Try older Magisk, for example 15.3.

Same to me. Just reboot and it´s fine.

BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Same. I don't have Xposed or other mods, so I think it's a Magisk's issue.

Made over 20 reboots in order to find the"right" combination of substratum themes the last two days.only 2-3 times i had stucked in reboot. I have magisk, xposed ,gravitybox .

Huh, I get this sometimes too. So it's Magisk v16 you say?
TrueMS said:
Try older Magisk, for example 15.3.
Click to expand...
Click to collapse
Good idea, will give that a go. I don't use any modules anyway, only use it for Safetynet-friendly root.

Same problem here.
I Will follow the topic.

Double post, Sorry!

With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5

laugeek57 said:
With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5
Click to expand...
Click to collapse
Currently testing 16.4b and no boot issues atm!
Must have been topjohnwu's boot operations code change.
Thank you really much