[Galaxy Tab Q&A, Help & Troubleshooting] tehvariance:
I think I'm in the same boat as [MENTION=10618211]fritz.barnes[/MENTION]. I've tried every combination of suggestion here but there's something weird going on.

I have a Samsung Galaxy Tab A 10.1 (2019) with unlocked bootloader, TWRP, and root (Magisk).

It appears as if anytime i replace /system/bin/lpm and put in the suggested shell scripts to trigger a reboot, it appears this isn't running at all or incurring some kind of exception.

I was initially really confused because there were other people saying that the script appeared to be working but that it was booting them into recovery/TWRP, and that appeared to be what was happening to me. But after going through so many scenarios, I think there was a reason for that.

1. When I first made the change to /system/bin/lpm after being in USB debugging and from ADB shell, when I turned the tablet off with cord unplugged, then plugged in cord, I got stuck at the initial lightning charge screen that doesn't have the real battery %, etc.

2. When this just got stuck forever and didn't reboot (regularly or into TWRP), I held POWER + VOL DOWN to reboot, then POWER + VOL UP to get back into TWRP. After getting into TWRP, mounting system, and making the similar changes to /system/bin/lpm, it "appeared" to be working in that after powering off with cord unplugged, it would start up when cord plugged in but go immediately into TWRP.

3. I realized later after trying multiple different versions of this file that all kept going into TWRP, if I rebooted regularly into system first with TWRP, then powered off with cord unplugged, then plugged cord in, I was still stuck at the initial lightning charge screen that doesn't have the real battery %, etc.

After all that, I'm assuming the initial lightning charge screen has nothing to do with /system/bin/lpm, and that this shows regardless of what /system/bin/lpm is. But compared to the original /system/bin/lpm behavior of in a few seconds showing correct battery %, my attempts at the shell script /system/bin/lpm probably just appear to be doing nothing (not rebooting) and just keeping me at the initial lightning charge screen.

As I said, I tried multiple different versions of the script throughout this thread and nothing has seemed to work. I have created the file or copied the file in different ways and also verified EOL characters, etc.

Does anyone have any idea what's going on with my situation (and possibly with [MENTION=10618211]fritz.barnes[/MENTION] having the same or similar issue that I do) or how to debug this? Is there something that has been altered with reboots by TWRP that requires any sort of Android property to be set or anything? I'm not an Android developer, but I see this in the TWRP source in terms of doing a system reboot, but I'm not fully sure what's going on here.

case rb_system:
Update_Intent_File("s");
sync();
check_and_run_script("/sbin/rebootsystem.sh", "reboot system");
#ifdef ANDROID_RB_PROPERTY
return property_set(ANDROID_RB_PROPERTY, "reboot,");
#elif defined(ANDROID_RB_RESTART)
return android_reboot(ANDROID_RB_RESTART, 0, 0);
#else
return reboot(RB_AUTOBOOT);
#endif

Thanks!

---------- Post added at 09:48 PM ---------- Previous post was at 09:21 PM ----------

Not sure if I'm normally supposed to reply to my own post here, but I have some more information that seems interesting.

If I take the original /system/bin/lpm, make a copy and then use the copy as /system/bin/lpm (and move the original to a different file, i.e. /system/bin/lpm.bak), the copied version of the original binary also seems to not work and keep me at the initial lightning charge screen. I am making sure to chmod 0755 and chown root.shell any copied files as you can see below. The original file has timestamp of 2008-12-31, and this specific file appears to be the only one that will work (and go to the normal charge indicator screen).

Not sure if this will further help diagnosis anything, but what's going on here? Why with a copy of the original lpm binary does this also result in me being stuck at the initial lightning charge screen? Any ideas?

I'd be willing to send a $50 bounty via Venmo to whoever can help me get this working.