Database Develop

The Boot Loop of Death (BLOD)

Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....

Reserved for future use

My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.

I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done

wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.

I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.

I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.

I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)

The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.

While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.

I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.

I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.

cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.

I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.

DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.

MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?

DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.

I have this on stock 2.1u1 EPE54B

I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.

tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?

Weird Issue with random freezes and failure to boot

So I had been running the same ROM without any issue for almost 18 months. The note 4 is my backup phone so I do not mess with it too often. I did use it almost every day though for a media remote for my family room. However the other day the phone rebooted after seeing a weird error message pop up. It was not like any I had seen before, looked like an error related to the hardware.
Now no matter what ROM I flash onto it I it struggles to boot. If it does boot the ROM is really slow and choppy and often freezes or gives me the black screen of death and I have to pull the battery. I have tried multiple ROMs both TW and AOSP base and all are having the same issue. Even using ODIN to go back to stock did not fix the issue.
Is it possible the phone just had a hardware failure and is toast? Just curious if anyone has had this issue and if they have any ideas on how to fix it.
Thanks!

ShrekOpher said:
So I had been running the same ROM without any issue for almost 18 months. The note 4 is my backup phone so I do not mess with it too often. I did use it almost every day though for a media remote for my family room. However the other day the phone rebooted after seeing a weird error message pop up. It was not like any I had seen before, looked like an error related to the hardware.
Now no matter what ROM I flash onto it I it struggles to boot. If it does boot the ROM is really slow and choppy and often freezes or gives me the black screen of death and I have to pull the battery. I have tried multiple ROMs both TW and AOSP base and all are having the same issue. Even using ODIN to go back to stock did not fix the issue.
Is it possible the phone just had a hardware failure and is toast? Just curious if anyone has had this issue and if they have any ideas on how to fix it.
Thanks!
Click to expand...
Click to collapse
Many have had similar issues, for example:
http://forum.xda-developers.com/note-4-tmobile/general/marshmallow-updates-issues-t3415914
http://forum.xda-developers.com/note-4-tmobile/help/major-phone-issues-reboots-freezes-t3440870
A proposed solution has been to downgrade to LP, although some people have reported it not fully fixing the issues.

Any future way to address corruption due to random reboots?

I've never had data corruption due to random reboots before using Magisk. Now, it's fairly frequent. It seems if my Nexus 6 reboots randomly, then struggles to boot back up again, something gets corrupted and I need to factory reset or restore a backup to fix it. I haven't seen much discussion about this and it makes me feel like I'm the only one. I'm not sure how widespread this is, if it's device specific, or what. But I would hope that the future of Magisk can take measures to address this.
Most common issues I've had are if I flash a module that doesn't work or boot. If I reboot during boot so I can remove the module from TWRP, it's highly likely my SustemUI gets corrupted. I've been a lot more cautious about what I flash because of this.
However, this morning, something else in the form of corruption occurred .My Nexus 6 tends to have an overheating problem -- not related to Magisk. It's from navigating, streaming music, and charging in the car. Sometimes, it reboots due to the heat. I try to unplug it when it gets hot and avoid it, but it's not always easy to notice while I'm driving. That was the case this morning. So it rebooted. Then it took agonizingly long to reboot. And when it did, it was incredibly slow and unresponsive, then rebooted again. And during next boot, my phone was all sorts of messed up. Data connection was "turned off" and turning it on did nothing. Notifications never displayed. Quick Settings tiles wouldn't display. System settings were factory default. Apps behaved strangely. Lots of issues. I'm assuming there was some level of corruption. I ended up having to factory reset since I didn't have a current backup (my fault).
This is quite annoying. Is there any possibility to focus development on preventing data corruption during boot or reboot? Has only been a problem since using Magisk. I've had heat-related reboots or mod-related bootloops before, never have had data corruption once resolved.

I have not yet had the opportunity to really troubleshoot this issue, but I did experience it on my N6 as well. It's on my todo list, but there are so many more things above it on the list.
The SystemUI has stopped issue could be 100% reproduced by merely backing up the data partition in TWRP. This happened on stock, Pure Nexus and Vanilla. Since then my N6 have kind of died and is now not suited for daily use, just for testing stuff.
The only thing I've found (and that might be of some kind of use) is that since completely wiping the device and NOT restoring anything to it (either through Google or Titanium Backup) the issue is no longer there and I can't reproduce it at all.

[solved] [SM-T813] Random Reboots. Works for days then for not even a minute

Hi,
first of all sorry for my bad english and screenshots with german text .
The situation:
I have a total of two Tab S2 (T-813). The first is 4 years old, the second is less than 2 years old. The newer is now causing problems.
The reboots occur:
- When using the tablet. Definitely with a high load, but also sometimes with only light loads
- When it is charging
- completely random
Edit1: reboots are not related to the battery percentage
Edit2: never experienced a reboot while in TWRP.
I didn't really find anyone with the same problem on the Internet. It is not a boot loop. Sometimes you can use the tablet for hours/ days. Then again not at all, because it starts again after a minute. To narrow down the problem, I formatted both tablets and installed the same lineage version and firmware. Since it restarts, log files are unusable, right?
Is there any way to narrow down the error?
I suspect overheating, but I would like to know if I have any way to isolate the fault exactly. Maybe there is also another (hardware) forum, which can help better in this case, then I would also be grateful for a tip.
I would have no problem opening the tablet. I've already done this with my smartphones.
Thx for your time.
Solution:
It is an overheating problem if you have exactly the same problems as I had.
You can test it simply like this: fill a plastic bag with cold water and some icecubes. Use it like a pillow for your tablet so it can rest on the bag while you use it. I had no problems at all while doing this.
I send it to Samsung and they repaired it.
It's just as new now.

I actually have the same problem, just only when its at 15 or less battery

Hi.
Well, it sounds for me like a different problem, cause it's battery related. My battery is fine and I have reboots not related to battery status.
Have you tried anything (factory reset, newest lineage and firmware,...)?

Hi,
same here. A SM-T813 running LineageOS that started with random freezes and reboots about a week ago. Sometimes I can use it for about half an hour without problems, next time it reboots while rebooting ...
Seems to be completly random, only thing I noticed that it never reboots while in TWRP.
Cleared and reinstalled LineageOS, but didn't change anything. First time rebooted while still in the setup wizard, next time I could finish the wizard and install serveral apps before the next reboot.
Maybe a problem with the memory?

Yes, that is exactly the same.
I never experienced a reboot in TWRP. No problem with reinstalling lineage.
But while reinstalling Android, it reboots while configuring and while reinstalling apps.
The last days I could watch Amazon prime every evening. Now it reboots after a minute even without using it. I shut it off and hope it will work this evening again.

I have the same issue, sent it in for repair asked to flip battery and swap mainboard. Got it back. Worked a few days, then had random reboots again. I am 100% sure it is a battery issue, and when you get under a specific voltage, maybe when it gets under 30% or so, the chance for reboots rise dramatically, with high cpu or flash memory usage. It happens more often when doing a update in Google Play store for example. So totally have no idea, if Samsung flipped the battery or not, but this was my last Samsung product ever. I would assume there is an issue with too much current drain and then it reboots, and the battery used in them are not designed for the units properly.

same to me. i was on stock rom. never root or anything. and got random reboots most of them when i open google play or google chrome. now im on lineage and same. also i notice that the tablet didnt reboot until i install gapps. and the tablet never reboot on recovery or TWSR. reboots on high or low battery. and if it was overheating maybe the tablet will reboot on recovery. dont know its weird. i will try lineage with out gapps to see what happend.

just testing lineage without gapps no reboot. run browser and netflix with no problems. then i install youtube from aptoid store. and reboot start again. o unistall youtube and no reboot for now.

Same here. I have random reboots but also wifi disconnections (unable to reconnect until i reboot the device)...
Not evident cause...

Someone got a solution for this?
Have the same problem on my T813

You can find the solution for the problem I described at the end of the first post.

Random shut down

Mypixel 4xl sometimes randomly shuts down I think an app, may be responsible.
Ampere says my battery is good.
im bootloader unlocked running 12 beta.
but it was shutting down before 12 beta i wiped everything.
was fine for 2 weeks now its doing it again.
anyway to arrange apps by date,so i can see what may be causing this?

I would flash factory stock again and wait a while before installing any root apps. It may be hardware related, or battery connection related. Meanwhile keep an eye on battery temp. Any chance you were outside in the heat when the phone shut down? The other thing you could try would be to put it in safe mode. If it does it in safe mode it is more likely hardware.

So I have a similar problem after installing the latest security update... My phone pixel 4 xl was just fine prior, but now it will turn off randomly when the screen goes off (or is locked to turn the screen off). I can only turn the phone back on after I plug it in to a charger. Interestingly, the battery and phone will keep running and the battery will drain normally so long as I keep the screen/interaction active. Ideas? Thinking about flashing a custom ROM. This phone is stock and nothing has been done to it. I also reset to factory to see if that was the fix, but no joy. Help?

@Springcrime
If the problem remains after a factory reset, you very likely have a hardware issue. The two main battery related issues are 1) the battery connection issue (abnormal or stuck battery percentages) , and 2) the swollen battery issue (no wireless charging, back glass separation (it's not easy to see). Flashing a custom ROM will only add multiple variables that will not solve the problem over restoring the phone to factory stock like you have already. As a last ditch effort, you could flash the phone with a full image and letting it wipe (don't edit the flash-all.bat). If that doesn't fix it you probably need to starting thinking any warranty options, or repair.

v12xke said:
@Springcrime
If the problem remains after a factory reset, you very likely have a hardware issue. The two main battery related issues are 1) the battery connection issue (abnormal or stuck battery percentages) , and 2) the swollen battery issue (no wireless charging, back glass separation (it's not easy to see). Flashing a custom ROM will only add multiple variables that will not solve the problem over restoring the phone to factory stock like you have already. As a last ditch effort, you could flash the phone with a full image and letting it wipe (don't edit the flash-all.bat). If that doesn't fix it you probably need to starting thinking any warranty options, or repair.
Click to expand...
Click to collapse
Normally I'd agree with that advice, but this literally and noticeably occured immediately after installing the latest security update. As a test, I've been running the battery down with videos, so long as I ensure I don't manually lock or turn the screen off, the battery has drained normally. No crashes or shutdowns while actively using the phone. Wireless charging works fine, and no visible swelling. Any other ideas? I joined the beta 12 program for the hell of it to see if that changes anything... Currently waiting for the push to my phone so I can download it.

Springcrime said:
So I have a similar problem after installing the latest security update... My phone pixel 4 xl was just fine prior, but now it will turn off randomly when the screen goes off (or is locked to turn the screen off). I can only turn the phone back on after I plug it in to a charger. Interestingly, the battery and phone will keep running and the battery will drain normally so long as I keep the screen/interaction active. Ideas? Thinking about flashing a custom ROM. This phone is stock and nothing has been done to it. I also reset to factory to see if that was the fix, but no joy. Help?
Click to expand...
Click to collapse
Try disabling the screen lock.
Double check all security settings.
As for all updates, if the OS is running fast and stable... leave it be.
Pie and above are pretty secure unless you do something stupid. As you can see a malware forced factory reset be less trouble than an update induced one. In 7 years of using mostly outdated android OS's never once did I need to do a factory reset because of malware.
My current Pie load is over a year old running fast and stable. It hasn't been updated in over 1.5 years... and it won't be.

It's impossible to get BH to install the latest ROM, and even I don't wanna judging from Google crappy OTA updates.
I only update for security not anything else though.

blackhawk said:
Try disabling the screen lock.
Double check all security settings.
As for all updates, if the OS is running fast and stable... leave it be.
Pie and above are pretty secure unless you do something stupid. As you can see a malware forced factory reset be less trouble than an update induced one. In 7 years of using mostly outdated android OS's never once did I need to do a factory reset because of malware.
My current Pie load is over a year old running fast and stable. It hasn't been updated in over 1.5 years... and it won't be.
Click to expand...
Click to collapse
So far so good on the screen lock. I wonder if it has anything to do with the facial recognition feature (which I enabled at the same time after the update). We'll see how this goes!

Springcrime said:
So far so good on the screen lock. I wonder if it has anything to do with the facial recognition feature (which I enabled at the same time after the update). We'll see how this goes!
Click to expand...
Click to collapse
Meh, play with it. Usually you'll figure out what's going on... they are complicated little devils.