Random Reboots on lineage-21.0-20240723 build

[MiZantr0pe]

Hi, penglezos!

I've been using the firmware for about a month. I installed it according to your instructions, used Lineage recovery, mindgaps, without installing additional magisk modules and other root stuff. During this time, there have already been 3 random reboots - one while using one of the messengers when starting the keyboard for typing, two reboots occurred in a state of rest, when the phone was just lying next to me on the table.

I attached the logcat.txt file, but I made it right after the phone rebooted. Sorry, but I don't know how to make a file that will show the problems that preceded the reboot of the device. Can you tell me how I can do this next time?

The guys from the 4pda forum also have reboots. Some have 5-7 reboots a day, while others (like me) - only after 100+ hours of stable operation.

logcat.txt

[penglezos]

Hi, thanks for your report!

First of all, you are not on the latest release, so please make sure you update accordingly. Regarding the "random reboots" from the logcat you posted I can't find anything problematic that can cause sudden reboots yet. I've been driving my LineageOS 21 builds daily for months without "random reboots" but we need to monitor it for sure. Did you by any chance changed the default kernel? are you encrypted or decrypted? did you flashed "legacy to dynamic" zip? Can you also provide the installed apps you have? Maybe you have an application that crashes the system I've seen that in the past with Skype (strange I know).

The guys from the 4pda forum also have reboots. Some have 5-7 reboots a day, while others (like me) - only after 100+ hours of stable operation.

I don't know what 4pda is neither I can accept that as a form of report.

[MiZantr0pe]

First of all, you are not on the latest release

Ok, about an hour ago I updated to the latest Lineage rom version. I'll watch its behavior.

Did you by any chance changed the default kernel?

Nope, there is default kernel, default lineage recovery from your installation guide and mindthegapps-package

are you encrypted or decrypted?

Im see "Encrypted" in "Encryption & Credentials" menu, and also I didn`t flash "legacy to dynamic" zip - because it wasn't in your installation guide, is it correct or not?

Can you also provide the installed apps you have?

Ok, let`s see files attached

screenshots.zip

[penglezos]

Yes you are encrypted. Holy shit there are so many apps installed. Let see how this release goes for you.

[MiZantr0pe]

Holy shit there are so many apps installed.

These screenshots also have system apps :D and I forgot to delete two pictures that duplicate the others

Can you tell me how I can export a list of applications as a TXT file without having to create a lot of screenshots?

Let see how this release goes for you.

You mean I should look at the behavior of the latest ROM version from August 20th? OK

but I don't know how to make a file that will show the problems that preceded the reboot of the device.

Can you please tell me how I can create a logcat.txt file next time so that it shows the problems that happened BEFORE rebooting the smartphone?

[Tfviktor]

I also have random reboots on 20240723.

[MiZantr0pe]

@Tfviktor hello! Let's help the developer - please answer his previous questions to me

[Lazarus00001]

I also faced random reboot previous build and latest build also, I didn't report because i didn't find any log on /sys/fs/pstore/

[penglezos]

I think it's safe to say that after 8 plus days of consistent uptime (on this test) that there are NO random reboots occurred.

[MiZantr0pe]

I think it's safe to say that after 8 plus days of consistent uptime (on this test) that there are NO random reboots occurred.

Hello! I have the same, 200 hours of stable work. But I'm not sure about stability yet - on the previous version the first reboot occurred after 500 hours uptime.

[penglezos]

I think it's safe to say that after 8 plus days of consistent uptime (on this test) that there are NO random reboots occurred.

Hello! I have the same, 200 hours of stable work. But I'm not sure about stability yet - on the previous version the first reboot occurred after 500 hours uptime.

Understandable my recent screenshot was just an example. I've been running my LineageOS 21 builds since mid November with more hours uptime without any random reboots whatsoever. 20 days of uptime on your previous result is in fact an indication of stability in my opinion. Based on the other non valid reports (here on Github) I can't do much. I've asked other users who use my builds if they experienced any random reboots and none of them had one.

[MiZantr0pe]

@penglezos After ~210 hours of work, the smartphone rebooted last night. It was just lying next to me, I was not using it at that moment. It was a complete reboot with the display of the Lineage OS logo. Please tell me how I can provide you the necessary information for analysis? The events in the logcat.txt file I created now no longer include events before the reboot that happened last night.

[penglezos]

@penglezos After ~210 hours of work, the smartphone rebooted last night. It was just lying next to me, I was not using it at that moment. It was a complete reboot with the display of the Lineage OS logo. Please tell me how I can provide you the necessary information for analysis? The events in the logcat.txt file I created now no longer include events before the reboot that happened last night.

That's sad to hear. Can you grab console-ramoops logs from /sys/fs/pstore ?

adb shell cat /sys/fs/pstore/console-ramoops-0 > console-ramoops.txt

[MiZantr0pe]

That's sad to hear. Can you grab console-ramoops logs from /sys/fs/pstore ?

adb shell cat /sys/fs/pstore/console-ramoops-0 > console-ramoops.txt

@penglezos I did what you said using adb:

cat: /sys/fs/pstore/console-ramoops-0: No such file or directory ^ the result of the command in the console looks like this. Am I doing something wrong?

[penglezos]

That's sad to hear. Can you grab console-ramoops logs from /sys/fs/pstore ? adb shell cat /sys/fs/pstore/console-ramoops-0 > console-ramoops.txt

@penglezos I did what you said using adb:

cat: /sys/fs/pstore/console-ramoops-0: No such file or directory ^ the result of the command in the console looks like this. Am I doing something wrong?

@MiZantr0pe and everyone willing to debug this please flash this kernel image in fastboot:

Link: https://we.tl/t-kTuGZNb91N

• fastboot flash boot boot.img
• restart phone
• verify that kernel is installed
• reboot to system once again
• verify that console-ramoops log is captured: adb shell cat /sys/fs/pstore/console-ramoops-0 > console-ramoops.txt

Next time you face "random reboot" immediately capture and send the log here via this command: adb shell cat /sys/fs/pstore/console-ramoops-0 > console-ramoops.txt or adb shell cat /sys/fs/pstore/console-ramoops > console-ramoops.txt

@MiZantr0pe in your case unfortunately this log never generated. Please if it's possible, flash this kernel run the command and send me the results, we might get lucky and capture any suspicious activity resulting in your random reboots. Personally I can't because I didn't faced yet nor other people that I asked.

Thanks for your time to report this, I'm trying to figure out why this happens only to limited amount of people but I don't have enough feedback.

Random reboots usually happen on a kernel panic and the only way that can be captured is this as far as I know that's why you can't capture it via logcat.

[MiZantr0pe]

@penglezos can you explain this boot.img that needs to be installed, - what is the difference between the default boot.img? Is it suitable for everyday use and can I not be afraid that it will not cause unstable work by itself? Because earlier you dont recommended change ROM's kernel 😅

• verify that kernel is installed

How can I verify this?

[penglezos]

@penglezos can you explain this boot.img that needs to be installed, - what is the difference between the default boot.img? Is it suitable for everyday use and can I not be afraid that it will not cause unstable work by itself? Because earlier you dont recommended change ROM's kernel 😅

• verify that kernel is installed

How can I verify this?

Nothing has changed its my own build kernel (same as the default) with working console-ramoops.

About phone > Android version

[MiZantr0pe]

@penglezos Unfortunately, capturing the log file does not work on your kernel, screenshots are attached

[Lazarus00001]

@MiZantr0pe after flash boot.img and reboot into system enable usb debuging and after that u need to wait until random reboot happen again, then try to capture ramoops log

[MiZantr0pe]

@penglezos @Lazarus00001

u need to wait until random reboot happen again

I have another one reboot - no logs again! The reboot occurred when I unlocking phine, the unlocking animation froze and the smartphone turned off.

[penglezos]

@penglezos Unfortunately, capturing the log file does not work on your kernel, screenshots are attached

@MiZantr0pe

I assume you have adb debugging enabled and latest adb & fastboot tools installed.

Try to enable "Rooted debugging" from the developer settings.

Open command line and type:

• adb root
• adb remount
• adb shell ls /sys/fs/pstore

what is the output?

[MiZantr0pe]

@penglezos

what is the output?

just nothing :( output is empty Rooted debugging have already enabled before today's reboot

[penglezos]

• adb shell cat /sys/fs/pstore/console-ramoops-0 > console-ramoops.txt

It should look like this:

and the log file:

I don't know what's wrong with your setup mines as you can see works. Are you using the latest SDK Platform-Tools from https://developer.android.com/tools/releases/platform-tools or something else?

[MiZantr0pe]

. Are you using the latest SDK Platform-Tools from https://developer.android.com/tools/releases/platform-tools or something else?

@penglezos I just downloaded platform-tools for windows from your link. Disabled developer options on the phone. Rebooted the phone. Enabled developer options again. Enabled the root debugging flag. Launched the terminal in the platform-tools folder, entered your 3 commands - the result did not change. Screenshots in the attachment.

[penglezos]

. Are you using the latest SDK Platform-Tools from https://developer.android.com/tools/releases/platform-tools or something else?

@penglezos I just downloaded platform-tools for windows from your link. Disabled developer options on the phone. Rebooted the phone. Enabled developer options again. Enabled the root debugging flag. Launched the terminal in the platform-tools folder, entered your 3 commands - the result did not change. Screenshots in the attachment.

I don't know what else to say mate mines working perfectly as you can see from the screenshots attached previously. Something is screwed at your end. Did you tried to flash stock ROM and clean flash LineageOS?

[MiZantr0pe]

Did you tried to flash stock ROM and clean flash LineageOS?

@penglezos no, I didn't do that because I think your flashing guide eliminates any issues that might have been caused by the previous ROM's junk. If I install the stock miui 12 ROM using miflash tool, need I to unlock the bootloader again or not?

[penglezos]

Did you tried to flash stock ROM and clean flash LineageOS?

@penglezos no, I didn't do that because I think your flashing guide eliminates any issues that might have been caused by the previous ROM's junk. If I install the stock miui 12 ROM using miflash tool, need I to unlock the bootloader again or not?

There's no need to reunlock the bootloader just make sure to apply the correct options. Check out the internet for instructions.

[MiZantr0pe]

@penglezos ok I'll try reflash the stock ROM and install your 20th august's Lineage today

[MiZantr0pe]

@penglezos ok, I re-flashed ROM v20.08.2024 over the official stock MIUI12, there were no reboots so far (~130 hours of work). I will continue to observe. I did not install your modified kernel just in case - everything is by default. I won't install the latest version from today for now - I hope that reboots on the version from August 20 will disappear, and then I will be able to use more recent versions of the firmware with complete confidence.

[penglezos]

@penglezos ok, I re-flashed ROM v20.08.2024 over the official stock MIUI12, there were no reboots so far (~130 hours of work). I will continue to observe. I did not install your modified kernel just in case - everything is by default. I won't install the latest version from today for now - I hope that reboots on the version from August 20 will disappear, and then I will be able to use more recent versions of the firmware with complete confidence.

I advise you to update straight to the latest release.

[penglezos]

I'm also have reboots first hour of usage. And after that - the most stable work possible.

I'm sorry dude but I can't help you like that. Read the discussions on the following page and provide the necessary information and logs.

[KrustyKrabCoder]

I encountered a similar issue. In my case, the phone seemed to reboot (showing the boot logo and everything), but when I checked the uptime, it hadn't actually reset to zero. Occasionally, it would fully reboot, requiring me to enter the SIM card code, and the uptime would reset to zero. This occurred randomly, whether the phone was in standby or in use.

I fixed the problem by flashing the complete Xiaomi ROM using fastboot (not just the firmware). You can download it here (choose the second option on the page labeled "fastboot"): Xiaomi ROM for Raphael global (V12.5.2.0). Flashing only the firmware via recovery didn't seem to update all the necessary partitions, especially since I had previously installed LineageOS 17.1, which may have corrupted some areas of the phone.

After flashing the full Xiaomi ROM and waiting for it to boot up, I rebooted into fastboot mode, installed the latest Lineage recovery, and then flashed the latest LineageOS release. My phone has now been stable for over 100 hours without any issues.

I recommend updating the instructions from "Installing device firmware from recovery" to "Installing the latest Xiaomi ROM and firmware via fastboot." This provides a more reliable starting point for flashing LineageOS, ensuring all partitions are correctly updated.

Important: Be sure to use the flash_all.sh or flash_all.bat script, not flash_all_lock.sh, as the latter would lock the bootloader, causing unnecessary delays while waiting to unlock it again.

Installation steps:

Step 1: Boot into Fastboot Mode

• Power off your device.
• Hold the volume down and power buttons simultaneously.
• Keep volume down pressed until the Fastboot screen appears.

Step 2: Connect and Flash Xiaomi ROM

• Connect your phone to a computer using a USB-C cable.
• Download the Xiaomi ROM for your device
• Xiaomi ROM for Raphael Global (V12.5.2.0)

• Xiaomi ROM for Raphael China (V12.5.6.0)

  • Be sure to choose the option labeled with type "fastboot" on the download page (second option on the page).
• Extract the downloaded .tgz file.
• Run the appropriate flashing script based on your operating system:
  • Windows: Run flash_all.bat
  • Linux/macOS: Run flash_all.sh
• Ensure that you have platform tools (like adb and fastboot) installed before running the script.

Step 3: Complete First Boot

• Wait for the device to complete the first boot until the initial setup screen appears.
• After this, reboot into Fastboot mode again by holding volume down and power as before.

Step 4: Flash LineageOS Recovery

• Using Fastboot, flash the latest LineageOS recovery to your device.

Step 5: Flash LineageOS ROM

• Reboot the device into Recovery Mode by holding volume up and power buttons.
• Once in LineageOS recovery, flash the LineageOS ROM file.

Step 6 (Optional): Flash GApps and/or Magisk

• If desired, flash GApps and/or Magisk (for root access) using LineageOS recovery before rebooting.

The phone should now be stable with the latest LineageOs build (20240909 at the time of writing).

[martinpl]

Could anyone reupload debug boot.img, i still have that "reboots" but uptime don't reset for me. I have those from LOS 20 but it don't bother me so much because the mostly happened when I don't use phone. I tried preflashing MIUI and keeping ROM clean (no Magisk).

[penglezos]

Could anyone reupload debug boot.img, i still have that "reboots" but uptime don't reset for me. I have those from LOS 20 but it don't bother me so much because the mostly happened when I don't use phone. I tried preflashing MIUI and keeping ROM clean (no Magisk).

If you are on the latest September build there is no need to search for this kernel version, commits already present.

[martinpl]

Logs: phone was ringing (phone call) and after 0.5s i saw LineageOS boot animation, uptime wasn't reset console-ramoops.txt

[penglezos]

Logs: phone was ringing (phone call) and after 0.5s i saw LineageOS boot animation, uptime wasn't reset console-ramoops.txt

Hi @martinpl,

Finally a user provids actual logs. To clear things up if uptime does not reset that's not an actual reboot that's a SystemUI restart. Looking at the logs you provided I identified this denial spamming a lot:

SELinux: avc: denied { find } for pid=4767 uid=90069 name=content_capture scontext=u:r:isolated_app:s0:c512,c768 tcontext=u:object_r:content_capture_service:s0 tclass=service_manager permissive=0

I'm not sure how this is triggered or if it's responsible for any reboots, but I silenced it for the next release.

For the record my current uptime before I rebooted my device yesterday intentionally for flashing purposes was 500+ hours (20 days+) and before that, while I was in August release was approximately 300 hours so more or less 30 days of stable operation.

Thanks for your time reporting this.