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 .ab file?
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 bmgr of 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.
com.qualcomm.timeserviceis an internals service you don't need to recover. I would extract the backup data using abe, delete the data for this package, rebuild the backup file and try again to recover the data. – Robert Feb 10 '23 at 08:05jackpal.androidtermfunction properly on rooted-devices only, no?) Also, is not locking the bootloader [as of] yet — a good-thing, no? Is it insignificant/immaterial/irrelevant? And do I have to create a newer backup-file and necessarily wipe the cache and system partitions, if not necessarily a wholesome clean-reinstall for the 6½th time? – maazkalim Feb 11 '23 at 03:10adb.exe, a-gain download as part of standalone SDKplatform-toolskit, had gone wholesomely corrupt but unlike the in-depth explanation at XDA, it hadn't reduced to "0KB" or anywhere remotely-near it. B) If it helps, frighteningly, turns out the very same case was with my.abfile in question — but I managed to 'miraculously' recover it full-&-proper when I regained my composure. C) One bad, one good — you say? Not that soon, ... – maazkalim Feb 13 '23 at 11:04.jarfile — as mandated by your tool. So I tried to install that "bestest-ever, open-source Java" programme from that.netofficial-web but in spite of installing the certificate separately, I still couldn't get it to installation. So we went to the OGs,Sun® MicrosystemsOracle® and after having expended twice the amount of time and more importantly, the – maazkalim Feb 13 '23 at 11:11abe.jar[ through Windows® PowerShell® from the "Downloads" folder"] within the hostile/unhelpful environment taking the toll on my mind, and when I finally managed to do so i.e. convert that successfully-recovered.abfile, your recommended-tool turned-out to be profoundly useless for editing.taraka, a misnomer of sorts. Since the conditions weren't conducive to me, I didn't have umpteenth hours to go find... – maazkalim Feb 13 '23 at 11:17cmd.exe, the former or Java® could help in editing.tarfolders as pre-installed freemium WinRAR® was oh-so-surprisingly appeared cruel towards us in that month. So I had no choice but to put my research-skills into motion yet a-gain, and finally found a sorta-reliable tool going bypeazip.exewhich did the trick through one of the 3 baffling deletion-types, since the rest of 2 were about deleting the whole.tarin and of itself which I had managed to extract after so much chore. D) So I managed to repack the updated.tarinto.adbafter – maazkalim Feb 13 '23 at 11:22WinRAR.exe, including but not limited to thecom.qualcomm.timeserviceone you overtly asked me to delete( there were othercom.qualcomm.[…]folders which I've no qualms to admit, was I significantly inclined towards ridding of them all but I guess to enhance my misery further down the order, I stuck to only-&-only "following down the orders like a robot/institutional-drone of neoliberal world-order. But waiiittt..! This was no-... – maazkalim Feb 13 '23 at 11:32.exegiven the recurrence ofAccess is denied.errors withplatform-toolsonly SDK, and after downloading and installing about fucking ~1GB of a file, turns out it was a mere shell( not necessarily in IT connotations) as I had to install discretionally needed "plugins" for total 3 so-called AOSP [sub-]releases given both of my phones, for starters. It took additional several-hours since – maazkalim Feb 13 '23 at 11:39adb restoreis not good. To fuck with brothafucking cockknuckle – maazkalim Feb 13 '23 at 11:45PowerShell-7.3.2-win-x64.msiin-folder within theplatform-toolssub-folder hidden insideAndroidfolder of hidden root-folderAppDatacame across like the Best choice. And it was quite more helpful in suggesting corrections than MSDOS-era Command Prompt ever has been. Nothing else, IG? – maazkalim Feb 14 '23 at 02:59powershell.exev5.1 in-folder within the sub-subfolderplatform-tools, itself under the sub-folderLocalwithin the folderSdkof main-folderAndroidwithin the hiddenAppDataroot-folder came* There! FTFM ♂️ Nothing latest except the fact that in cookie-cutter length, that I've created a single.txtfile of.\adb.exe logcatwith the added-bonus of-v -timesuffixed-in there, for at least the last 2 restoration attempts. Thought given my STML-addled memory, think I could give an idea as to how USB link suddely disconnects-&-immediately-reconnects that way. – maazkalim Feb 14 '23 at 18:59