[APP][5.0+][ROOT][2020.12.21] LiveBoot (Logcat/Dmesg Boot Animation) v1.84

Search This thread

m0b

Senior Member
Apr 14, 2010
382
135
35
Kiev
Pretty much everything Magisk related is stored in /data/adb. So, having a Magisk module that doesn't touch /data is going to be quite difficult (read: doesn't work like that)...
Strange, there was "post-fs" boot stage "happens after the most partitions are mounted, except /data". Modules stored in /cache/magisk_mount/system.
https%3A%2F%2Fi.imgur.com%2F4UgbRUI.png

But it`s gone now. Is it because google killed /cache partition on A/B devices?

https://github.com/topjohnwu/Magisk/blob/master/docs/details.md

My Galaxy A50 still got /cache!
 
Last edited:

Didgeridoohan

Senior Moderator / Developer Relations
Staff member
May 31, 2012
11,546
12,023
Gothenburg
Google Nexus 4
Nexus 6

christantoan

Senior Member
  • Oct 9, 2015
    197
    87
    OnePlus 3T
    OnePlus 7 Pro
    I have a LG V30 (H930) running Liquid Remix Pie ROM. For me the live boot works but only shows up in the top left quarter of the display. This happens during boot as well as during the test from the ui. Any idea how to solve this? I did not find any options to set the resolution.
    I have the same case with my OnePlus 7 Pro running Oxygen OS 9.5.5 BA (EU variant). In my case, I have the option to change the resolution.

    The test run has the same result in QHD+ resolution (only displays at top left corner of the screen) (screenshot attached) while in FHD+ it works fine.

    The problem still happens at boot though.

    I've tried to reinstall the Liveboot script on both display resolution but the problem persists. Screenshot_20190527-121031.jpg

    Sent from my OnePlus 7 Pro using Tapatalk
     

    Lukalion

    Senior Member
    Apr 1, 2016
    114
    31
    Darmstadt
    I have the same case with my OnePlus 7 Pro running Oxygen OS 9.5.5 BA (EU variant). In my case, I have the option to change the resolution.

    The test run has the same result in QHD+ resolution (only displays at top left corner of the screen) (screenshot attached) while in FHD+ it works fine.

    The problem still happens at boot though.

    I've tried to reinstall the Liveboot script on both display resolution but the problem persists. View attachment 4766465

    Sent from my OnePlus 7 Pro using Tapatalk

    +1. have the exact same problem with oneplus 7 pro
     
    • Like
    Reactions: f2bacon

    spinsupreme

    Member
    Dec 22, 2016
    19
    7
    Oklahoma City
    I have the same case with my OnePlus 7 Pro running Oxygen OS 9.5.5 BA (EU variant). In my case, I have the option to change the resolution.

    The test run has the same result in QHD+ resolution (only displays at top left corner of the screen) (screenshot attached) while in FHD+ it works fine.

    The problem still happens at boot though.

    I've tried to reinstall the Liveboot script on both display resolution but the problem persists. View attachment 4766465

    Sent from my OnePlus 7 Pro using Tapatalk

    i also have this problem
     

    maumaus

    Senior Member
    Aug 13, 2008
    119
    16
    Hmm something is weird with LiveBoot on my Samsung S7. It's oldskool rooted with SuperSU for a year now.
    After a reboot SuperSU asked to update binaries. Which was a bit strange. (Probably something got corrupted).
    Didnt go well... so I just flashed Super SU v2.82 again and everything was fine again.
    Accept for Liveboot. So I reinstalled it. It has SU rights. Opened the app and it gave installing message...
    But after multiple tries and reboots... no Liveboot :(

    Does anybody had any idea how I can fix it?
     

    neshipda

    Member
    Jun 8, 2017
    18
    5
    pixel 3a xl

    Que ?

    LiveBoot is a boot animation that shows you logcat and dmesg outputs on-screen as they happen. Output configuration includes logcat level, buffer and format selection; whether to show dmesg; the amount of lines that should fit on your screen, whether word-wrap should be employed, and if output should be color-coded. Additionally the background can be set to transparent to overlay the existing boot animation, which looks awesome during boot.

    A feature is built-in to test your current configuration without rebooting. The lines shown in test mode may be limited and relatively static, this does not reflect exact boot time behavior as much as it just shows you that it works and how big the text will be.

    Note that LiveBoot will only show up after the data partition is mounted. If you need to enter a decryption key or pattern at boot, it will not show up until you have done so.

    Root

    This app does not only require root, it requires specifically SuperSU version 2.40 or newer, or a recent Magisk, due to how the boot-time code is launched. Alternatively, the app will try to function for otherwise rooted firmwares that support init.d, but this is not officially supported and it cannot be guaranteed to work.

    Compatibility

    Officially the app supports 5.0+ and newer. Regardless of version, the app may work on your device or it may not. I've gotten it to work on a bunch of my own devices on various firmwares, but not on all. Even if the test run functionality works, this does not necessarily mean it will actually work during boot. It usually does, but not always.

    This does indeed also mean I cannot guarantee continued operation - even if it works for you today, it may fail your next firmware update. If that is an issue for you, then you should definitely not update to Pro.

    The risk of bootloops is extremely low, but not completely non-existent. Should a bootloop occur, removing either the app's APK or /system/su.d/0000liveboot through recovery should fix the problem.

    Unless you are using SuperSU in system-less mode, the app writes to /system, as such your firmware must allow this. There is no recovery-based install option at this time.

    Pro

    There's an in-app purchase to upgrade to Pro, which supports my developments, and unlocks the transparency option as well as logcat buffer and format selection.

    Of course, if you have one of the paid variants of the old live logcat or live dmesg boot animations from all those years ago installed, this will also enable Pro mode.

    Like some of my other apps these days, if you don't have Google Play but still managed to install the APK, this will also enable Pro mode.

    Last but not least, if you simply don't want to pay for it, there's also a button to enable Pro mode (the 'freeload' option)

    Script

    If /system/su.d/0000liveboot.script or /su/su.d/0000liveboot.script or /sbin/supersu/su.d/0000liveboot.script exists (chmod 0644, not 0700 like other files in /system/su.d/ or /su/su.d/ !), this script will be run instead of logcat and dmesg, and its output will be shown in white (stdout) and red (stderr).

    Download

    Google Play

    or see attachment below

    Screenshots
    (1.14: 7646; 1.20: 5826; 1.30: 3999; 1.40: 1512; 1.50: 16710; 1.60: 25034; 1.70: 9446)


    couldn't resist from testing it :) and if someone like me was wondering... on pixel 3a xl it works like a charm!
    and thanks Chainfire!
     
    • Like
    Reactions: ipdev

    rage302

    Senior Member
    May 29, 2012
    188
    123
    OnePlus 8T
    First of all... I love this App and your work @Chainfire.
    As a long time user of LiveBoot on many devices, I was curious to find out if it is working on my recently updated OnePlus 7 Pro to Android 10 (Open Beta1) with Magisk 19.3.

    It was not so smart to think it will work, because of the Android 10 changes.

    So... but now I can confirm... It does not work on Android 10.

    I hope famous Dev @Chainfire will update this App the one or the other day. Because it is not just beautiful and "nerdy" but also really helpful in case of boot problems or bootloops.

    Best, rage
     
    • Like
    Reactions: omartrox and SMS786

    elhennig

    Senior Member
    Feb 21, 2011
    957
    231
    I have the same case with my OnePlus 7 Pro running Oxygen OS 9.5.5 BA (EU variant). In my case, I have the option to change the resolution.

    The test run has the same result in QHD+ resolution (only displays at top left corner of the screen) (screenshot attached) while in FHD+ it works fine.

    Any news on the QHD+ display problem? There should be more and more devices with that resolution...
    A fix would really be appreciated
     
    • Like
    Reactions: f2bacon

    smartman_ru

    Member
    Feb 26, 2012
    26
    7
    27
    Moscow
    Crdroid Poco F1 Android 10 dont work, dont test
    log
    Code:
    10-18 15:32:38.848  4708  4708 I Thread-236: type=1400 audit(0.0:13877): avc: denied { getattr } for path="/system/lib64/bootstrap" dev="sde48" ino=2208 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:system_bootstrap_lib_file:s0 tclass=dir permissive=1 app=eu.chainfire.liveboot
    10-18 15:32:39.083  3847  3847 D SHELL_IN: magisk --sqlite 'INSERT INTO logs (from_uid,to_uid,from_pid,package_name,app_name,command,action,time) VALUES(10104,0,15051,"eu.chainfire.liveboot","LiveBoot","/system/bin/sh",1,1571401959081)'
    10-18 15:32:39.174  3847  3847 D SHELL_IN: magisk --sqlite 'INSERT INTO logs (from_uid,to_uid,from_pid,package_name,app_name,command,action,time) VALUES(10104,0,15058,"eu.chainfire.liveboot","LiveBoot","/system/bin/sh",1,1571401959172)'
    10-18 15:32:39.261  3847  3847 D SHELL_IN: magisk --sqlite 'INSERT INTO logs (from_uid,to_uid,from_pid,package_name,app_name,command,action,time) VALUES(10104,0,15065,"eu.chainfire.liveboot","LiveBoot","/system/bin/sh",1,1571401959260)'
    10-18 15:32:39.381 15129 15129 I eu.chainfire.liveboot:root: Core platform API reporting enabled, enforcing=false
    10-18 15:32:39.497 15129 15129 W eu.chainfire.liveboot:root: ClassLoaderContext shared library size mismatch. Expected=1, found=0 (PCL[]{PCL[/system/framework/org.apache.http.legacy.jar*2680228128]} | PCL[])
    10-18 15:32:39.497 15129 15129 I eu.chainfire.liveboot:root: Failed to add image file Rejecting application image due to class loader mismatch: 'Mismatch in shared libraries'
    10-18 15:32:39.508 15129 15129 W eu.chainfire.liveboot:root: JNI RegisterNativeMethods: attempt to register 0 native methods for android.media.AudioAttributes
    10-18 15:32:39.512 15129 15129 D AndroidRuntime: Calling main entry eu.chainfire.liveboot.a.d
    10-18 15:32:39.551  3847  3847 D SHELL_IN: magisk --sqlite 'INSERT INTO logs (from_uid,to_uid,from_pid,package_name,app_name,command,action,time) VALUES(10104,0,15108,"eu.chainfire.liveboot","LiveBoot","/system/bin/sh",1,1571401959549)'
    10-18 15:32:39.687 15129 15129 I eu.chainfire.liveboot:root: System.exit called, status: 0
    10-18 15:32:39.717   542   542 I ServiceManager: service 'eu.chainfire.liveboot#0#daemonize' died
     
    • Like
    Reactions: Kürt Enes

    NuclearNautilus

    New member
    Nov 2, 2019
    1
    2
    Razer Phone 2 problem

    There is a problem on my Razer Phone 2. When the screen resolution is set to 1440p, LiveBoot only occupies a portion of the screen. When I change the screen resolution to 1080p, LiveBoot displays as expected.
     
    • Like
    Reactions: Sk1t and f2bacon

    Top Liked Posts

    • There are no posts matching your filters.
    • 316
      [APP][5.0+][ROOT][2020.12.21] LiveBoot (Logcat/Dmesg Boot Animation) v1.84

      Que ?


      LiveBoot is a boot animation that shows you logcat and dmesg outputs on-screen as they happen. Output configuration includes logcat level, buffer and format selection; whether to show dmesg; the amount of lines that should fit on your screen, whether word-wrap should be employed, and if output should be color-coded. Additionally the background can be set to transparent to overlay the existing boot animation, which looks awesome during boot.

      A feature is built-in to test your current configuration without rebooting. The lines shown in test mode may be limited and relatively static, this does not reflect exact boot time behavior as much as it just shows you that it works and how big the text will be.

      Note that LiveBoot will only show up after the data partition is mounted. If you need to enter a decryption key or pattern at boot, it will not show up until you have done so.

      Root

      This app does not only require root, it requires specifically SuperSU version 2.40 or newer, or a recent Magisk, due to how the boot-time code is launched. Alternatively, the app will try to function for otherwise rooted firmwares that support init.d, but this is not officially supported and it cannot be guaranteed to work.

      Compatibility

      Officially the app supports 5.0+ and newer. Regardless of version, the app may work on your device or it may not. I've gotten it to work on a bunch of my own devices on various firmwares, but not on all. Even if the test run functionality works, this does not necessarily mean it will actually work during boot. It usually does, but not always.

      This does indeed also mean I cannot guarantee continued operation - even if it works for you today, it may fail your next firmware update. If that is an issue for you, then you should definitely not update to Pro.

      The risk of bootloops is extremely low, but not completely non-existent. Should a bootloop occur, removing either the app's APK or /system/su.d/0000liveboot through recovery should fix the problem.

      Unless you are using SuperSU in system-less mode, the app writes to /system, as such your firmware must allow this. There is no recovery-based install option at this time.

      Pro

      There's an in-app purchase to upgrade to Pro, which supports my developments, and unlocks the transparency option as well as logcat buffer and format selection.

      Of course, if you have one of the paid variants of the old live logcat or live dmesg boot animations from all those years ago installed, this will also enable Pro mode.

      Like some of my other apps these days, if you don't have Google Play but still managed to install the APK, this will also enable Pro mode.

      Last but not least, if you simply don't want to pay for it, there's also a button to enable Pro mode (the 'freeload' option)

      Script

      If /system/su.d/0000liveboot.script or /su/su.d/0000liveboot.script or /sbin/supersu/su.d/0000liveboot.script exists (chmod 0644, not 0700 like other files in /system/su.d/ or /su/su.d/ !), this script will be run instead of logcat and dmesg, and its output will be shown in white (stdout) and red (stderr).

      Download

      Google Play

      or see attachment below

      Screenshots
      (1.14: 7646; 1.20: 5826; 1.30: 3999; 1.40: 1512; 1.50: 16710; 1.60: 25034; 1.70: 9446; 1.81: 2564, 1.83: 23762)
      81

      Why ?

      I always liked the old logcat and dmesg boot animations on 2.x. Unfortunately the code doesn't port well to newer Android versions. They were starting to cause more issues for users than they were provide coolness, so I pulled them from Play (together with a number of other apps) some time ago.

      While working on the next generation of Mobile ODIN, I've started using some techniques that I realized could be used to bring this back. Aside from being as cool as it is, this app actually serves as a testbed for these techniques.

      Tech

      The code is launched by a daemonsu bootscript immediately after /data is available. It then pulls an overlay surface from SurfaceFlinger through native code. It proceeds by running Java code that spins threads that catch logcat / dmesg / script output with libsuperuser. That output is then rendered by the Java code with OpenGL to the surface and shown on-screen.
      57
      SAUCE AVAILABE AT GITHUB - https://github.com/Chainfire/liveboot

      Changelogs

      2020-12-21 - v1.84

      - Android 11
      - Removed links to Google Plus (hehe)
      - (c) 2020

      2019-12-31 - v1.83
      - Android 10

      2019-03-13 - v1.81
      - (c) 2019
      - Fix script reinstalling every launch
      - Fix display not working on some Pie ROMs
      - Fix test run not working on some devices

      2019-01-06 - v1.80
      - Magisk: support /data/adb paths
      - Magisk: delay startup if /data not available
      - Fix script uninstall not working
      - Use librootjava's Daemon mode

      2018.11.16 - v1.70
      - Android 9.0 Pie support
      - Improved 64-bit support
      - Fix files dir not existing automagically
      - Migrated libcfsurface from C hijacks to Java reflection as much as possible (4.2 --> 5.0 minimum support)
      - Magisk support
      - Adaptive icon
      - Updated compile and target API levels
      - (C) 2018

      2017-09-11 - v1.60
      - Add compatibility with Android Oreo
      - Add compatibility with SuperSU in SBIN mode
      - Fix toolbox/toybox detection on 64-bit, could cause animation to keep running

      2016-12-20 - v1.50
      - [email protected]: stop animation when Android is up
      - (C) 2017

      2016-10.30 - v1.40
      - Android N 7.1 file-based-encryption support

      2016-05-19 - v1.30
      - Android N Preview 3 support

      2015-10-30 - v1.20
      - Android 6.0 support

      2015-01-03 - v1.14
      - Force remove old boot scripts before placing new one
      - Added another watchdog to prevent the animation from never quitting
      - (C) 2015
      - Note: some devices need SuperSU v2.42 or newer to work

      2014-12-21 - v1.13 - BETA
      - Use alternative shell if default not available (fx HTC One m7, m8)
      - Workaround b/7188322 hack (fx Shield Tablet)
      - Fixed minor script issues

      2014-12-20 - v1.12
      - ProGuard (reduce APK size)

      2014.12.20 - v1.11 - BETA
      - Added option to disable logcat color coding
      - Another possible fix for premature exit

      2014.12.20 - v1.10 - BETA - RELEASE NOTES
      - Possible fix for only showing for two seconds during boot on some devices
      - Fixed some typos
      - Made logcat buffers configurable (pro)
      - Made logcat format configurable (pro)
      - Made word wrap configurable
      - Added option to darken the background
      - Added option to save logs
      - Added reboot option

      - Added capability to use init.d if not using SuperSU, but this is not officially supported. It might make the app work on more firmwares, but it should be noted that init.d behavior differs between firmwares, and unlike su.d provided by SuperSU, no guarantees are made as to the state of the /data partition or SELinux policies when init.d scripts execute. Therefor it is impossible to officially support - it might work, it might not, and this will differ between firmwares.

      2014.12.18 - v1.05
      - Fixed number of lines being interpreted as hexadecimal
      - Fixed various load and display issues on 4.3 and 4.4

      2014.12.17 - v1.00
      - Initial release
      18
      Here's another test version, let me know if that helps.

      Script uninstall now also works properly, sorry about that.

      I'm running DeluxeROM 9.4 (Oreo 8.0) on my Note 8 with the latest unofficial release of Magisk. LiveBoot seems to install and the test works fine but doesn't seem to do anything during boot.

      I'm not sure where the scripts have copied to or if I need to do something in Magisk to get it working...

      I see this in the Magisk Logs:

      Exactly the same behavior. Nexus 5X, 8.1 (November stock image), Magisk 17.3. Magisk log shows
      Code:
      post-fs-data.d: exec [0000liveboot]
      but nothing is displayed, only the stock boot animation.

      PS, "test run" works fine, but starts approx. 20 seconds after clicking the menu item.

      Hi,

      Tried LiveBoot v1.70 but it's not working on my LG (H910) V20 phone running Nougat 7.0. Hopefully it will in a future update? I'd be happy to test.

      Thanks

      On pixel 3xl. It was working initially, now nothing when I restart. Occasionally works when I power off.
      Uninstall through the app does is not working either

      It will not work on redmi note 4 10.0.1 stale rom..
      I liked this app on soo many other devices, installed via play store.
      My device is unlocked and magisked 17.1


      not working on samsung j200gu 5.1.1 stock rom touchwiz :( test run works but when i reboot it only shows the standard bootanimation please help :(
      Here are attachments for more details


      Update: It worked using v1.60. Before I installed the v1.70 I had a back up so i wiped my data etc then restore it and then instead of v1.70 I used v1.60 and it worked like magic! :victory:
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone