This is a follow-up troubleshooting question to this one here in this very same forum.
After repeatedly confirming the connection through both of
adb devices -l and
fastboot devices -l tantamounting to at least ~5½ of overall sessions for the restore command of a 7.95GB-heavy backup file, whenever there's a successful prompt after proper command-execution of the following:
adb restore <filepath>
But I managed to notice the constant: The restoration always gets stuck on
com.qualcomm.timeservice quite oddly till time-immemorial, since I understand that I might be at fault somehow, somewhere — but in spite of that, if the latest builds of so-called AOSP do not support alarm-ringing during device shutdown [not caused by battery-drainage], I can safely conclude that the alarm did work during switch-off state of my device at least once. Doesn't that translate to the package working fine, instead of having gone corrupt by the time I created the
More details for those who un-stereotypically can digest in-depth text, they may get better context over there with some back-citation to key comments in that preceding question over here.
But other than the exact package which gets stuck, I should also note that I did try
adb push <PC's .ab filepath> <device's root-directory path> after 1-2 trials-&-errors to determine which one is exactly it. It went upto 100% in
ADB Enabled recovery mode, and then.. Failed to be stored by the time I booted the device last-time I clean-reinstalled the latest-build[ as I originally send this] of LineageOS 19.
The rest of the context is summarised there, except that I haven't tried
adb shell 'cus using
bu help wasn't much of a help, so it slipped my mind to try creating backup through that method — nevermind restoring.