Database Users

Tracking down reboots

I've been getting reboots semi randomly for the last week or two and I was wondering if I could get some help on trying to figure out why.
Going back two weeks ago I was having some pretty poor battery life compared to some other users so I tried to do a full purge and restart. I went through the file manager on twrp and deleted any folder for any app that I wasn't using in a possibly misguided attempt to curb any file conflicts. After I did this I did a fresh install of cataclysm and Franco. After running into some reboots I tried with Kylo kernel and had the same issue. I then tried full wipe with Ubermallow and Kylo and had the same issue. Then I did a full lock, unlock, flash stock, root and recovery, and fresh install of chroma and Franco aaaaaand it still reboots.
I've had reboots randomly while listening to music but only 3-5 of them and in every install I've done I've had the same two apps do it. Starbucks app will reboot when using auto fill to log in, either through swiftkey or last pass, and Lyft will reboot the phone seemingly randomly.
What I want to know is whether or not this could be a hardware issue and if not how to get this to stop or if anyone else has had the same issue. It's seems so random yet specific and it's happened on so many different installs that I have no idea. I have been rooting my phones since the OG Droid so I have a pretty good idea of what I'm doing but I have never had an issue like this that lasts through so many installs of so many different things.

Info
Gil Smash said:
I've been getting reboots semi randomly for the last week or two and I was wondering if I could get some help on trying to figure out why.
Going back two weeks ago I was having some pretty poor battery life compared to some other users so I tried to do a full purge and restart. I went through the file manager on twrp and deleted any folder for any app that I wasn't using in a possibly misguided attempt to curb any file conflicts. After I did this I did a fresh install of cataclysm and Franco. After running into some reboots I tried with Kylo kernel and had the same issue. I then tried full wipe with Ubermallow and Kylo and had the same issue. Then I did a full lock, unlock, flash stock, root and recovery, and fresh install of chroma and Franco aaaaaand it still reboots.
I've had reboots randomly while listening to music but only 3-5 of them and in every install I've done I've had the same two apps do it. Starbucks app will reboot when using auto fill to log in, either through swiftkey or last pass, and Lyft will reboot the phone seemingly randomly.
What I want to know is whether or not this could be a hardware issue and if not how to get this to stop or if anyone else has had the same issue. It's seems so random yet specific and it's happened on so many different installs that I have no idea. I have been rooting my phones since the OG Droid so I have a pretty good idea of what I'm doing but I have never had an issue like this that lasts through so many installs of so many different things.
Click to expand...
Click to collapse
What about complete stock ROM (official firmware + kernel)? OR CyanogenMOD?
If your phone fine with stock or CM so it s the ROM/Kernel bug u installed and need to report to its developer
:good:

[N910F]Random reboots (links to logs included)

Hi,
My N910F has recently been acting weirdly. It either randomly reboots itself, or just freezes for several seconds when switching screens or scrolling/tapping buttons. This started a couple of weeks ago on stock 5.0.1 (this version, I think) running Emotion kernel. This was running fine for a while; I didn't flash any new mods during this time, although I did switch between AEL kernel and Emotion once or twice without much success.
Thinking it was just one of those situations that called for a clean slate; I backed up my important stuff, booted into TWRP to wipe all partitions, then flashed stock 5.1.1 via Odin (this version, which I'm currently running). But even before I rooted it once again the phone was displaying the same aforementioned symptoms, both during and after going through the built-in setup wizard. This behaviour continued after flashing TWRP and AEL kernel v8.2, which I'm currently on at the moment. If it makes any difference I've also noticed that the lower my battery level, the more often it reboots itself. The battery level also "yo-yos" sometimes, usually at lower levels.
I've uploaded the relevant logs as advised elsewhere for anyone who can decipher them, as I otherwise don't know what to look for. This includes my last three kmsg dumpstate logs (just in case it's a slightly different cause each time), as well as my logcat and dmesg files (whatever they are lol) which I got using the SysLog app.
Any help would be appreciated, and if you need any more info please let me know.
Thanks .

*bump*

I have the same problem. Help would be highly appreciated. : )

*bump*
[UPDATE]: Once or twice when it's crashed as above, it would try and boot again but then reboot into download mode with the following text at the top of the screen above all the other info:
Code:
Could not do normal boot.
ddi: mmc_read failed
If I then pull the battery and turn it on again, it boots up as normal (at least until the next crash). Is this something that can be fixed with a fresh flash in Odin (or some other method), or is my phone on the way to its death?

Got the same issue + loses Wifi password after random reboot. Sent the phone back to the operator I bought it from 1 week ago and they did a repair. They replaced the USB-flex, did a firmware upgrade(?? ..was already updated to latest) and sent it back. I got it this morning and at first the phone now works fine and no more "mmc_read fail". But after some time the random reboots started again. Not so often now but still 4 times over the day and twice the wifi-password is lost and I had to retype it. Now I'm on the fence and just waiting for the first mmc_read fail" to happen before I complain and send it back for a second repair. I can not imagine this beeing beeing other than a hardware fail coming from a weak spot on the phone. I got the impression many people has the same issue and it really comes to life after upgrading to 5.1.1.
I also think the problem at the service shop ist that they just do a quick system test on a clean wiped phone and can't find the issue and think the phone is fine. After reinstalling my 200 apps and setting up my phone all over again, the workload causes the issue to reappear and I now have to ask the service shop for a deeper check. They accepted this as a warranty fix all though my phone has a knox trip (0-1)x4...

I've also faced random reboots on Lollipop. How i solved that? Simple. I downgraded to Kitkat. Lollipop still having lots of battery drains and bugs even on 5.1.1

[UPDATE]
I've decided to go through my network provider to get a replacement sent out to me, which they were happy to do after going through their line of questioning over the phone ("have you tried turning it off and on again", "did you try taking out your memory card and see if that helped", "did you try doing a factory reset", etc). They say it will get here tomorrow so fingers crossed for the replacement.

The ddi mmc_read fail has not reappeared yet..
It's strange.. Lately the random reboots are not wiping my wifi passwords anymore, but now after every random reboot the multiwindow is enabled and I've got to untick it in quick settings..
Latest: It seems that the random reboot may come from heavy account sync workload. I did have 5 Google accounts syncing on my phone + 6 excange accounts and when i disabled syncing alltogether the phone ran a lot smoother and the reboots stoped. So i deleted all Google accounts except my main account and for now thing seems to be fairly stable. I've also uninstalled all for me unimportant 3'rd party apps, reducing 3'rd party app count from aprx 200 to 150..
If things develop further I'll come back with more
Sent from my ****in' phone!

Thanks fot starting this thread Jointfcfan...i am using 910P and have same issue of your post 1 and 4!!!!
Loosing hope on Samsung, it is really frustrating...
Tried cleaning cash, dalvic, reboots, on latest 5.1.1 k version...frozen all not neede games and apps ...only 1 google and 1 exchange account no auto sync
At next stage while rebooting it sometime going an error stating kernel panic and i have to pull battery to restart

Replacing USB-flex board at service shop has cured the "ddi. mmc_read fail" boot issue for good.
So to me it seems that when many people experiences this, the USB-flex board may have a built in design flaw making it a weak spot on the Note 4.
Also I found that the phone works A LOT smoother if using Nova launcher instead of TW. Random reboot count is way down and phone works almost normally. Still some lag, mostly when unlocking screen, but reboots happens only 2-3 times a day now. Still random rebooting enables "multi window" option every time..
I've also rooted the phone now using CF-autoroot. I've flashed Philz CWM recovery and using it to install Wanam Xposed. So now I can run Greenify properly in Xposed mode and automaticly hibernate apps including system apps..
NB! Be aware, flashing root and custom recovery trips Knox counter 0x1 permanently and MAY void warranty
I have also mailed my operator asking them to take in the phone a second time for check/repair, alt. replacing the phone. I guess when they did system check 1st. time without issues after replacing the USB-flex, it was done when phone was reset to factory and under no significant workload.
Sent from my ****in' phone!

Nexus 6p Bootloop Fix/Workaround

After upgrading to Andriod N on the 6p, many of us have been plagued by the Bootloop of Death and/or random reboots. Some have tried RMAs, have purchased new devices or moved to backup devices. Huawei has claimed software is the culprit and Google has stated that it's the hardware. Personally I've tried a clean install of the ROM, Dirty flashing the ROM, clearing the caches, etc.
Nothing has worked... Until now!
I'm days in without a single random reboot or Bootloop.
This advice is provided without warranty or any guarantee that it'll work for you but it may work.
I'm not a developer and I've not tried multiple devices.
Steps:
*Note I'm on the latest Pure Nexus build.
1. If you're currently stuck in a Bootloop, then leave your 6p to Bootloop until it actually starts or until the battery dies. If it starts skip to step 3.
2. If it Bootloops, then intervene occasionally by getting the device to boot into the bootloader (Hold down power and volume down). Once there, attempt to reboot recovery. It'll probably keep Bootlooping but occasionally the device will start up.
3. Once your 6p starts, download the ElementalX apk from the Google Play Store. Don't do anything else. I've only tried this app so it's the only one that I recommend for this "fix".
4. Download the ElementalX kernel through the ElementalX app and follow the prompts in order to install the kernel. Allow it to reboot. *You may be able to complete the following steps with the stock kernel.
5. Once your device has rebooted, open the ElementalX app and click the leaf icon in order to enable power saving. This will lower your CPU's freq, GPU's freq, and most importantly, it will disable the BIG CPU cluster.
After these steps were completed I haven't experienced any random rebooting​ or Bootloops. Yes, this ”fix" hobbles your device but it is still quite functional. I think that on Nougat the constant switching between the two processor clusters causes random restarts and Bootlooping​.
There may be an alternative that will allow you to disable the little CPU cluster instead and not lower the GPU performance. I've not tried any other methods yet.
Specs added thanks to @510jungleboy
Nexus 6p 128 GB
ROM: Pure Nexus 7.1.2 r6
Kernel: ElementalX
Bootloader: Unlocked
Recovery: TWRP
Warranty: Expired
Please comment with results.

Multiple people have reported getting the boot loop of death while on Marshmallow. I think the idea that Nougat is causing the problem was discredited long ago, the fact that its a hardware issue with these phones is widely accepted and that the age of the phone is much more of a factor than the operating system you are running. Most of these phones are experiencing the boot loop of death shortly after the warranty expires, when the phone is 12-14 months old. Your phone is generating less heat since you ramped down the CPU which is likely why it isn't currently bootlooping.

Well...
jhs39 said:
Multiple people have reported getting the boot loop of death while on Marshmallow. I think the idea that Nougat is causing the problem was discredited long ago, the fact that its a hardware issue with these phones is widely accepted and that the age of the phone is much more of a factor than the operating system you are running. Most of these phones are experiencing the boot loop of death shortly after the warranty expires, when the phone is 12-14 months old. Your phone is generating less heat since you ramped down the CPU which is likely why it isn't currently bootlooping.
Click to expand...
Click to collapse
You may be right but I didn't notice any Bootloops or random reboots until I upgraded to Nougat. After putting this "fix" in place my device still gets pretty warm under load but it doesn't exhibit random reboots or Bootloops... Heat didn't seem to be the issue since my phone would reboot into a Bootloop while just sitting on my desk at work with only background tasks running. Regardless, this workaround works for me and it may work for others.

Mine just reboots over and over, for days and days, my bootloader is locked and usb debugging is off.

HOW would one install APk from playstore if their phone can't even load up, aka bootloop of death ? You need to be more specific , like locked bootloader , unlock bootloader ..etc.... smh

Once battery dies what i have to do? (my phone dies two hours ago when I was with a 3% of charge and its bootlooping over and over) Full charge? Another thing?
Note:
1)I'm on the latest Pure Nexus build, stock kernel, unlocked bootloader
2)When i connect to the charger one hour ago the phone shows battery charge mode but stills bootlooping. I'm waiting to battery dies

jhs39 said:
Multiple people have reported getting the boot loop of death while on Marshmallow. I think the idea that Nougat is causing the problem was discredited long ago, the fact that its a hardware issue with these phones is widely accepted and that the age of the phone is much more of a factor than the operating system you are running. Most of these phones are experiencing the boot loop of death shortly after the warranty expires, when the phone is 12-14 months old. Your phone is generating less heat since you ramped down the CPU which is likely why it isn't currently bootlooping.
Click to expand...
Click to collapse
510jungleboy said:
HOW would one install APk from playstore if their phone can't even load up, aka bootloop of death ? You need to be more specific , like locked bootloader , unlock bootloader ..etc.... smh
Click to expand...
Click to collapse
Sorry that I wasn't more specific. My bootloader is unlocked and I'm rooted. Users may not need to be in order to get back the device's functionality.
It's a shot in the dark but if a user that is having the Bootlooping issue follows my steps, then they may get back up and running. I've yet to have another random reboot or a Bootloop since...

RyomaEchizen said:
Once battery dies what i have to do? (my phone dies two hours ago when I was with a 3% of charge and its bootlooping over and over) Full charge? Another thing?
Note:
1)I'm on the latest Pure Nexus build, stock kernel, unlocked bootloader
2)When i connect to the charger one hour ago the phone shows battery charge mode but stills bootlooping. I'm waiting to battery dies
Click to expand...
Click to collapse
Since it's died, you'll need to power it on once it's charged for a while. When you power on and it starts Bootlooping, boot into the bootloader and follow my steps. If it Bootloops continuously, boot into the bootloader again and try to get into recovery. It will probably continue to Bootloop. That's what happened to me. I'd come back to it from time to time, boot to the bootloader, prompt it boot to recovery... over and over again. Eventually, it would fully boot up instead (not into recovery).
If it starts DON'T check messages or try to use your phone normally. Instead, follow the steps. Seriously. I made that mistake over and over again.
FYI: This process can take a looong time. Not days but sometimes it was hours until I figured my solution out. I don't know exactly how long it takes because I'd leave the phone Bootlooping and come back to it later in the day.

Many thanks!
Its work for my nexus 6p too
My nexus work normal in interval 1-5% of charge. If charge increase 11% - bootloop...
After enable powersave elementalx, charging to 100% and work well

I have a smartphone. Automatically went into reboot, but did not boot. It constantly reboots. First, the test is reflected that I've been unlocked by the bootloader, and then the Google inscription, and after that the smartphone reloads again. The recovery menu does not enter.

Thanks! Finally something that worked! The big cluster is indeed the problem. I had the porblem that the phone freezes and gets stuck in the bootloop when the battery is above 10-12%. I guess that the cpu disables the big cluster when you are underneath that threshhold(?).
One big problem I am still facing is that I can't reboot my phone and I have to make it discharge until I can boot it up again. Do you have have something that prevents that?
Big thanks again!

Still bootloops
haieb said:
Thanks! Finally something that worked! The big cluster is indeed the problem. I had the porblem that the phone freezes and gets stuck in the bootloop when the battery is above 10-12%. I guess that the cpu disables the big cluster when you are underneath that threshhold(?).
One big problem I am still facing is that I can't reboot my phone and I have to make it discharge until I can boot it up again. Do you have have something that prevents that?
Big thanks again!
Click to expand...
Click to collapse
I followed all the steps but my Nexus 6P still bootloops after crossing 10% charging. Is it possible for you to share your Kernel Manager settings screenshots please?

I too began to experience the boot loop issue literally 8 days after my warranty expired which was 11 days ago today! Have tried flashing several factory images from MM to N and even a saved backup I made from day 1 of having the phone. This method of disabling the big cluster thru ExK has definitely been the furthest I have gotten. Me and my friend(da guy) did find out that in order for the phone to boot up at all, the battery has to be at approx. 6% or lower. In that time is when you must quickly download ExK and activate power saver mode. I just called Huawei support and they did absolutely nothing to help me in this manner. I really do hope that this lawsuit wins in our favor. Speaking of which, does anybody know where we can check for status of this current litigation?
Update: Ordered a new battery and installed it... still bootlooping. This is very frustrating as i have been forced to use my ancient Moto Droid X2 as my daily

I wonder if someone could compile a kernel that always disables the big cluster for those with bootloop problems. Then you could just flash the kernel and not have to try repeatedly to get the phone to boot long enough to install the app.
Sent from my Galaxy S8 using Tapatalk

inneyeseakay said:
I wonder if someone could compile a kernel that always disables the big cluster for those with bootloop problems. Then you could just flash the kernel and not have to try repeatedly to get the phone to boot long enough to install the app.
Sent from my Galaxy S8 using Tapatalk
Click to expand...
Click to collapse
is this possible?

headcreepz said:
is this possible?
Click to expand...
Click to collapse
I'll have to look into kernel building, but I'd imagine if you built a kernel that had powersaving as the default profile, it would work.

Got into recovery long enough to flash pure Nexus and root, but haven't been able to get it to boot yet.
Looking forward to one day being able to use it again. ?
Sent from my Galaxy S8 using Tapatalk

A little help!
nicotinic said:
After upgrading to Andriod N on the 6p, many of us have been plagued by the Bootloop of Death and/or random reboots. Some have tried RMAs, have purchased new devices or moved to backup devices. Huawei has claimed software is the culprit and Google has stated that it's the hardware. Personally I've tried a clean install of the ROM, Dirty flashing the ROM, clearing the caches, etc.
Nothing has worked... Until now!
I'm days in without a single random reboot or Bootloop.
This advice is provided without warranty or any guarantee that it'll work for you but it may work.
I'm not a developer and I've not tried multiple devices.
Steps:
*Note I'm on the latest Pure Nexus build.
1. If you're currently stuck in a Bootloop, then leave your 6p to Bootloop until it actually starts or until the battery dies. If it starts skip to step 3.
2. If it Bootloops, then intervene occasionally by getting the device to boot into the bootloader (Hold down power and volume down). Once there, attempt to reboot recovery. It'll probably keep Bootlooping but occasionally the device will start up.
3. Once your 6p starts, download the ElementalX apk from the Google Play Store. Don't do anything else. I've only tried this app so it's the only one that I recommend for this "fix".
4. Download the ElementalX kernel through the ElementalX app and follow the prompts in order to install the kernel. Allow it to reboot. *You may be able to complete the following steps with the stock kernel.
5. Once your device has rebooted, open the ElementalX app and click the leaf icon in order to enable power saving. This will lower your CPU's freq, GPU's freq, and most importantly, it will disable the BIG CPU cluster.
After these steps were completed I haven't experienced any random rebooting​ or Bootloops. Yes, this ”fix" hobbles your device but it is still quite functional. I think that on Nougat the constant switching between the two processor clusters causes random restarts and Bootlooping​.
There may be an alternative that will allow you to disable the little CPU cluster instead and not lower the GPU performance. I've not tried any other methods yet.
Specs added thanks to @510jungleboy
Nexus 6p 128 GB
ROM: Pure Nexus 7.1.2 r6
Kernel: ElementalX
Bootloader: Unlocked
Recovery: TWRP
Warranty: Expired
Please comment with results.
Click to expand...
Click to collapse
I really want this to work. Can you please share your settings? I'm not getting passed 10-12% charge. It makes a loud noise and bootloop till around 6% but runs fine if it's below 10%. I can watch videos and listen to music

Same issue !
haieb said:
Thanks! Finally something that worked! The big cluster is indeed the problem. I had the porblem that the phone freezes and gets stuck in the bootloop when the battery is above 10-12%. I guess that the cpu disables the big cluster when you are underneath that threshhold(?).
One big problem I am still facing is that I can't reboot my phone and I have to make it discharge until I can boot it up again. Do you have have something that prevents that?
Big thanks again!
Click to expand...
Click to collapse
Did u ever figure it out? Also can u show me some screenshots of your settings?

Got mine up and running!! [emoji41]
Here are my settings:
Sent from my Galaxy S8 using Tapatalk

Random & Persistent Reboots

Hi all,
For the last 3/4 weeks my Moto X Style XT1572 has been randomly rebooting, usually this is when it is not in use and either in my pocket or desk.
I was running AICP and tried a couple of factory resets. This did not help.
I then factory reset and installed Dirty Unicorns (last weekly). Again this hasn't helped. No overclocking, undervolting, just stock kernels and I have tried handbag kernel.
Still rebooting.
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks

rowlers said:
Hi all,
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks
Click to expand...
Click to collapse
Flash the newest stock 6.0.1.
Without botloader, gpt, no oem commands(don't lock BL).
You need stock system to recognize: hardware or software problem.

I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.

I seem to have resolved the issue by using the Chill governor. Fingers crossed, but I've not had a reboot for 2 days now...

radon222 said:
I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.
Click to expand...
Click to collapse
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.

JustLok said:
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.
Click to expand...
Click to collapse
Moto X Style , Android 6.0 , Not rooted, pure stock, exact same symptoms as you guys with the random reboots while not in use , losing Bluetooth pairings... Did a factory reset, didn't change a thing. Sometimes, I can get 2 days without reboots, then have 2 in the same hour the next day. It sucks. I'm hoping the Nougat update will fix this, if it ever gets released for my version...

Got 1 doing the same stuff, all stock, gets warm, reboot itselfs, wrong date and time, and no bt pairing

Mine is still doing it too. Not as bad as it was but at least once per day, when idle, sleeping it just reboots for no apparent reason. Not ROM, Kernel and I have factory reset.

Persistent rebooting issues

Hi
Firstly, thanks for taking the time to read this
I am stock ROM and RECOVERY.
Problem
For the past few weeks my phone has been freezing and rebooting (or sometimes after a minute I'm forced to restart manually)
This happens at different times, different battery percentages, apps, and even just locked in my pocket. With lots of app and even minimal apps installed.
I have reinstalled rom and rec twice now - all official. And wiped all options at least twice.
I really am at my wit's end now (https://dictionary.cambridge.org/dictionary/english/at-your-wits-end)
Again, thanks for reading.
Any advice would be great, I'm confident doing any software changes necessary.
Regards,
Josh

Vitamin--X said:
Hi
Firstly, thanks for taking the time to read this
I am stock ROM and RECOVERY.
Problem
For the past few weeks my phone has been freezing and rebooting (or sometimes after a minute I'm forced to restart manually)
This happens at different times, different battery percentages, apps, and even just locked in my pocket. With lots of app and even minimal apps installed.
I have reinstalled rom and rec twice now - all official. And wiped all options at least twice.
I really am at my wit's end now (https://dictionary.cambridge.org/dictionary/english/at-your-wits-end)
Again, thanks for reading.
Any advice would be great, I'm confident doing any software changes necessary.
Regards,
Josh
Click to expand...
Click to collapse
Do you have root to pull out these files from within that directory sys/fs/pstore
They'll might help to identify the random reboot issue. Pull them out after the random reboot happens. It's a log of what forced the reboot.

cutomer bringed few weeks ago op5 with same issue. had to fully reflash with ufs repartition, restored imei by box (was wiped out by repartition, twrp backup didn't worked). pretty common issue after 8.0 update.

strongst said:
Do you have root to pull out these files from within that directory sys/fs/pstore
They'll might help to identify the random reboot issue. Pull them out after the random reboot happens. It's a log of what forced the reboot.
Click to expand...
Click to collapse
No root, unfortunately . What about OEM logs or bug capturing