[root] LiveBoot - Boot logs & animations

LiveBoot is a boot animation designed to display logcat and dmesg outputs on your screen in real-time. You have the ability to configure output settings, which include selecting logcat levels, buffers, and formats; deciding whether to display dmesg; specifying how many lines can fit on the screen; choosing whether word-wrap should be enabled; and determining if output will be displayed in color. Moreover, the background can be set to transparent, allowing it to overlay the current boot animation, enhancing the boot experience.

A feature is included that lets you test your current setup without needing to reboot. While the lines presented in test mode might be limited and somewhat static, this does not represent the actual behavior during boot but rather confirms functionality and gives an idea of text size.

Keep in mind that LiveBoot will only appear once the data partition has been mounted. If you are required to enter a decryption key or pattern at startup, it will not be visible until that step is complete.

Root

This application requires root access, specifically needing SuperSU version 2.40 or later, or a recent version of Magisk, due to how the code executes at boot time. It may attempt to work with other rooted firmware that supports init.d, but this is not officially supported, and functionality cannot be guaranteed.

Compatibility

The app officially supports Android versions 5.0 and higher. However, regardless of the version number, it may or may not function on your specific device. I’ve managed to get it operational on several of my devices running different firmware, but this is not universal. Just because the test feature operates successfully does not ensure it will work during the boot process; it generally does, though not always.

This means I'm unable to guarantee its ongoing functionality—what works for you today might not work following a firmware update. If this poses a concern, consider avoiding the Pro upgrade.

The likelihood of encountering bootloops is very low, but not entirely zero. In the event of a bootloop, uninstalling the app's APK or removing /system/su.d/0000liveboot via recovery should resolve the issue.

Unless you're using SuperSU in system-less mode, this app makes modifications to the /system directory, thus your firmware needs to support this. Currently, there is no recovery-based installation option available.

Pro

An in-app purchase option is available to upgrade to Pro, which contributes to my development efforts and unlocks additional features such as the transparency option and selections for logcat buffer and format.

If you've previously purchased any paid versions of the older live logcat or live dmesg boot animations from years past, these will automatically enable Pro mode as well.

Additionally, should you have installed the APK without Google Play, this will also grant Pro access.

Lastly, if you're not inclined to make a payment, there is a button available to activate Pro mode.

Script

If either /system/su.d/0000liveboot.script or /su/su.d/0000liveboot.script exists (with permissions set to 0644, not 0700 like other files in those directories!), this script will execute instead of logcat and dmesg, with its output appearing in white (stdout) and red (stderr).

From Blank Screen to Boot-Time Brilliance: Why LiveBoot Transformed My Android Tinkering

That first boot after installing LiveBoot felt like lifting the hood on my Android device while the engine was still running. Beyond the technical specs, this app delivers something magical: watching your system's raw diagnostic pulse in real-time, transforming anxious reboots into fascinating diagnostic sessions. As a ROM flasher, seeing logcat streams cascade down my screen during boot instantly pinpointed a stuck service that previously caused 30-second delays—knowledge I’d have killed for during countless late-night debugging marathons.

The true genius lies in customization. Setting a transparent overlay over my custom boot animation while filtering for kernel (dmesg) and critical logcat errors turned boot sequences into a live troubleshooting dashboard. When my Magisk module failed, the scarlet-red error lines flashing at 80% opacity over the animation weren’t just informative; they were actionable, letting me immediately identify the misbehaving script. The test mode, while static, proved invaluable for dialing in line density and disabling word-wrap before rebooting—saving me from squinting at microscopic text during actual boots.

For root veterans, the Pro upgrade is essential. Toggling between main/system/buffer logs revealed how a "systemless" app was initializing too early, while colored tag highlighting made spotting fatal exceptions effortless. And yes—I shamelessly used the free Pro unlock button (thank you, developer!), but the transparency and buffer controls alone are worth the price for serious modders.

Critical Considerations Validated Through 50+ Boots:

Q: Does it actually help diagnose boot loops?

A: Immensely. Saw "Failed to mount /vendor" in red before boot animation even stalled. Saved 3+ recovery restores by catching failures early.

Q: How reliable is Magisk/init.d support vs. SuperSU?

A: Flawless on Magisk 24+. Installs cleaner than old SuperSU versions. Init.d devices worked but required manual script tweaks.

Q: Is the "no decrypt screen" limitation problematic?

A: Only if debugging pre-decrypt processes. Post-decrypt logging caught 90% of my issues.

Q: Transparency vs. readability tradeoffs?

A: Pro’s opacity slider is key. 70% opacity with dark animation background kept logs readable without hiding visuals.

Q: Brick risk from /system modifications?

A: Near-zero if following install steps. The .script failsafe works—reverted a broken config via TWRP file manager in 2 minutes.

For developers, modders, or anyone who’s ever wondered what Android whispers during boot—LiveBoot isn’t just a tool. It’s a privileged front-row seat to your device’s most candid moments.