XPost: comp.sys.mac.system, alt.comp.os.windows-10, comp.mobile.android
From: marion@facts.com
On 15 Apr 2025 13:18:40 GMT, Frank Slootweg wrote :
> This PC\Frank's Galaxy A51\Internal storage\Android\data\net.o
mand.plus\files
>
> But 'This PC\Frank's Galaxy A51\Internal storage' is only accessible
> in File Explorer, it's not part of the normal file system, nor
> accessible as a Network Share, so you can't use normal copy or backup
> utilities. (Perhaps in Windows PowerShell one can 'program'/control File
> Explorer? No idea.)
I will agree with anyone who says anything logically sensible, where I
agree with Frank that there must be a DIY backup mechanism to Windows.
On the one topic of the paradoxical observation that both Frank Slootweg
and I have experienced of what can be "seen" by the PC vs the phone...
Windows can see Android root!
I also have been surprised when the PC can see *far* more of the Android
file system than the (non rooted) Android device itself can see.
Look at /etc/resolv.conf
Sure, we all know ADB can back up the system /etc/hosts file but even
without ADB, I can read (and write) to far more of the Android file system
from the PC than from the phone itself. From the Windows command line!
cmd line access to /etc
For example, when I mount the Android as a Windows drive letter, I can read
"almost" the entire system (not all of it - but a lot more than you'd
expect). And I can write to some of the system filesys too I think.
Look at the dnsproxy file
In summary, given my observation that when mounting an Android filesystem
as a drive letter on Windows that you can see far more than you'd expect to
see, one possible backup mechanism might be to use a Windows copy script.
Windows root access!
--- SoupGate-DOS v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
