From Newsgroup: comp.mobile.android

Marion, 2025-07-22 18:39:

On Tue, 22 Jul 2025 16:42:33 +0200, Arno Welzel wrote :

If a user mounts the Android file system as a drive letter on Windows,
(which I've done a billion times and which requires nothing more than a
free no-registration no-ads webdav server running on Android), then you can >>> see on Windows more of the Android file system than you can see on Android. >>> <https://i.postimg.cc/6371SxNd/mountandroidonwindows.jpg>

You can see stuff in the Android root file system for example.
Like the Android HOSTS file.

Note: On Windows, ADB can also see the root Android file system.

See, maybe - but not *access* it without root permissions.

Hi Arno,

I'm not sure what you mean by "access" because there are (at least) two different types of "access", one of which is "read access", which you have.

Correct. However, some folders are not readable using ADB without root permissions. For example all folders inside /data/data since this is the protected storage of apps.

And the most important point: you first have to install ADB on your
computer *and* get your device connected, which is not that simple for
many people.

[...]

Using CxFileExplorer or FTP is a terrible kluge, IMHO, for example.

Why? It doesn't need any extra software besides the app itself. Even FTP
can be used in Windows without any extra tools - it may not show up as
"drive letter" but you can still add the FTP server provided by
CxFileExplorer as network location in Windows and just use it.

All those "MyPhoneExplorer" style kluges are ridiculously absurd, I feel.

Compared to the sheer simplicity of simply mounting Android to Windows as a drive letter (or to the even simpler use of the Windows file explorer).

What is "simple" in using a command which you have to know first
compared to a menu in the Windows explorer which to add a network
location? How many average Android and Windows users even know what "net
use" means if you don't tell them first?
--
Arno Welzel
https://arnowelzel.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On 2025-07-22 23:57, Arno Welzel wrote:

Marion, 2025-07-22 18:39:

On Tue, 22 Jul 2025 16:42:33 +0200, Arno Welzel wrote :

[...]

Using CxFileExplorer or FTP is a terrible kluge, IMHO, for example.

Why? It doesn't need any extra software besides the app itself. Even FTP
can be used in Windows without any extra tools - it may not show up as
"drive letter" but you can still add the FTP server provided by CxFileExplorer as network location in Windows and just use it.

All those "MyPhoneExplorer" style kluges are ridiculously absurd, I feel.

Compared to the sheer simplicity of simply mounting Android to Windows as a >> drive letter (or to the even simpler use of the Windows file explorer).

What is "simple" in using a command which you have to know first
compared to a menu in the Windows explorer which to add a network
location? How many average Android and Windows users even know what "net
use" means if you don't tell them first?

I tried "Cx File Explorer" FTP the other day. It is fine and easy for transferring photos, but it transferred 23331M while simple-mtpfs
transferred 56257M. Many files, mostly in the /Android directory, were
not copied.
--
Cheers, Carlos.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

On Tue, 22 Jul 2025 23:57:54 +0200, Arno Welzel wrote :

I'm not sure what you mean by "access" because there are (at least) two
different types of "access", one of which is "read access", which you have.

Correct. However, some folders are not readable using ADB without root permissions. For example all folders inside /data/data since this is the protected storage of apps.

Hi Arno,

I do agree with you on this for visibility of unrooted Android files.
There seem to be three situations.

a. Files/folders which are read/write to everyone
b. Files/folders which are read only to privileged apps like webdav/adb
c. Files/folders which are locked from reading by even privileged apps

And the most important point: you first have to install ADB on your
computer *and* get your device connected, which is not that simple for
many people.

Well.... we did it so many years ago that we forgot what it took. :)
(I use adb every day, all day, since scrcpy requires adb to mirror.)

Using CxFileExplorer or FTP is a terrible kluge, IMHO, for example.

Why? It doesn't need any extra software besides the app itself. Even FTP
can be used in Windows without any extra tools - it may not show up as
"drive letter" but you can still add the FTP server provided by CxFileExplorer as network location in Windows and just use it.

Well. OK. I've tried them all. Every single one. I prefer WebDAV.
However, some people take the train, others take the bus while others fly.
It all works in the end where it boils down to individual preferences.

BTW, with FTPUse you can get a drive letter out of unrooted Android.
<https://www.ferrobackup.com/map-ftp-as-disk.html>
"The FTPUSE command maps a remote share (FTP server) as a local drive,
so you can use the FTP server of your choice as a local hard drive.
FTPUSE is a free application which was developed during production
of the endpoint backup solution Ferro Backup System, but disks
mapped using FTPUSE can be accessed by any application
(e.g. Windows Explorer, Total Commander, MS-DOS command shell)."

Even though FTPUse allow mounting of Android as a drive, I prefer
to use WebDAV to mount Android as a drive letter on Windows.

All those "MyPhoneExplorer" style kluges are ridiculously absurd, I feel.

Compared to the sheer simplicity of simply mounting Android to Windows as a >> drive letter (or to the even simpler use of the Windows file explorer).

What is "simple" in using a command which you have to know first
compared to a menu in the Windows explorer which to add a network
location? How many average Android and Windows users even know what "net
use" means if you don't tell them first?

Well, OK. I've tried every method ever suggested on this ng (AFAIK) that doesn't require an account and which has no ads and which is free.

Some people walk, some run, some ride bikes, others drive cars.
Use whatever method floats your boat.

I was simply distinguishing between the methods, where some are
simpler and more robust than others.

Here's something I wrote years ago when testing all possible solutions.

1. You can connect the Android phone to Windows 10 by Bluetooth,
by Wi-Fi (over the LAN or by ad hoc Wi-Fi) or by USB cable.

Most people just plug the phone into Windows (just like any other
USB device) and Windows automatically installs the driver for it.
*Install OEM USB drivers*
<https://developer.android.com/studio/run/oem-usb>

If the correct driver isn't installed, every manufacturer provides it.
Acer -> https://www.acer.com/worldwide/support/
Alcatel -> https://www.alcatelmobile.com/support/
Asus -> https://www.asus.com/support/Download-Center/
Blackberry -> https://swdownloads.blackberry.com/Downloads/entry.do?code=4EE0932F46276313B51570F46266A608
Dell -> https://support.dell.com/support/downloads/index.aspx?c=us&cs=19&l=en&s=dhs&~ck=anavml
FCNT -> https://www.fcnt.com/support/develop/#anc-03
HTC -> https://www.htc.com/support
Huawei -> https://consumer.huawei.com/en/support/index.htm
Intel -> https://www.intel.com/software/android
Kyocera -> https://kyoceramobile.com/support/drivers/
Lenovo -> https://support.lenovo.com/us/en/GlobalProductSelector
LGE -> https://www.lg.com/us/support/software-firmware
Motorola -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/
MTK -> http://online.mediatek.com/Public%20Documents/MTK_Android_USB_Driver.zip
Samsung -> https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Sharp -> http://k-tai.sharp.co.jp/support/
Sony -> https://developer.sonymobile.com/downloads/drivers/
Toshiba -> https://support.toshiba.com/sscontent?docId=4001814
Xiaomi -> https://web.vip.miui.com/page/info/mio/mio/detail?postId=18464849&app_version=dev.20051
ZTE -> http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442

2. Either way (BT, Wi-Fi or USB) there are a multitude of connection tools.
Offhand, some of the Android/Windows file-sharing solutions are
AirDroid <https://www.airdroid.com/personal/>
ADB <https://developer.android.com/tools/adb>
AFT MTP client <https://whoozle.github.io/android-file-transfer-linux/>
DirectNetDrive <http://www.directnet-drive.net/>
FTPUse <https://www.ferrobackup.com/download/FtpUseInst.exe>
Ftpuse <https://www.ferrobackup.com/map-ftp-as-disk.html>
Fb-adb Android Linux shell <https://github.com/facebook/fb-adb>
Go-mtpfs MTP FUSE filesystem <https://github.com/hanwen/go-mtpfs>
Gphotofs Camera Linux mount <http://www.gphoto.org/proj/gphotofs/>
JMTP FS <https://github.com/JasonFerrara/jmtpfs>
KDEconnect <https://play.google.com/store/apps/details?id=org.kde.kdeconnect>
Kies Connect <https://www.samsung.com/africa_en/support/kies/>
LibIconv <http://gnuwin32.sourceforge.net/packages/libiconv.htm>
LibMTP <https://github.com/hanwen/go-mtpfs>
LibMTP <https://sourceforge.net/projects/libmtp/>
LibMTP library MTP implementation <http://libmtp.sourceforge.net>
LibUSB Win32 <http://libusb-win32.sourceforge.net/>
LibUsbK <https://sourceforge.net/projects/libusb-win32/>
LibiConv <http://gnuwin32.sourceforge.net/packages/libiconv.htm>
MTP support on KDE <https://cgit.kde.org/kio-mtp.git>
MTPDrive <http://mtpdrive.com/download.html>
MTPSync <https://www.adebenham.com/mtpsync/>
MTPdude <http://mtpdude.sourceforge.net>
MTPfs FUSE filesystem <https://www.adebenham.com/mtpfs/>
NetDrive 1.3.2.0 <https://filehippo.com/download_netdrive/12615/>
NetDrive 3.6.571 <http://netdrive.net/ (deprecated)
Nitroshare <https://play.google.com/store/apps/details?id=net.nitroshare.android>
PhoneLink <https://www.samsung.com/us/support/answer/ANS00083910/>
SFTP Net Drive <https://www.nsoftware.com/sftp/netdrive/>
SideSync <https://play.google.com/store/apps/details?id=com.sidesync.freeapp>
SMB Cifs (client) X-Plore <https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore>
SMB Cifs (root) <https://play.google.com/store/apps/details?id=com.imperioustech.www.sambaserver>
Scrcpy/sndcpy <https://github.com/Genymobile/scrcpy>
Termux copy <https://github.com/termux>
WebDav <https://play.google.com/store/apps/details?id=com.theolivetree.webdavserver>
WebDrive <https://webdrive.com/download/>
XNJB Mac OS X GUI <http://www.wentnet.com/projects/xnjb/>
(this is mostly offhand so I likely missed as many as I listed)

Personally, for myself, I'd mount the entire Android filesystem onto
Windows as a read/write Windows drive letter over Wi-Fi using WebDav.

See also FTPUse above which also creates a Windows networked share.

Or, if I'm running commands from Windows to disable, install or
otherwise manipulate applications, I use adb over Wi-Fi or USB.

If I'm already using adb, then I may as well use screencopy and
soundcopy to do _all_ the Android manipulations from the PC alone.

But most people just plug the Android phone into Windows to drag and
drop any file in the user partition between the devices using that PC.

3. Of those, plenty are ad hoc Wi-Fi & USB file-sharing solutions.
Kies Connect <https://www.samsung.com/africa_en/support/kies/>
Nitroshare <https://play.google.com/store/apps/details?id=net.nitroshare.android>
KDEconnect <https://play.google.com/store/apps/details?id=org.kde.kdeconnect>
FTPUse <https://www.ferrobackup.com/download/FtpUseInst.exe>

I've used every single one of them, where my suggestion is NitroShare
because of its simplicity (but all work, just in different ways).

4. You can set up Android to act differently whenever you connect to USB
Android12 Settings > Developer options > Default USB configuration
(o) Transferring files <---- AFAIK, this is the default
(_) USB tethering
(_) MIDI
(_) Transferring images
(_) Charging phone only
I wouldn't change this from the default of "Transferring files).

5. Of course, you can do everything using just adb (on Wi-Fi or USB).

First, find the name of the desired package:
C:\> adb shell pm list packages | findStr /i "osmand"
C:\> adb shell pm list packages <--- list all packages on the device
C:\> adb shell pm list packages -f -3 <--- list third-party packages
C:\> adb shell pm list packages -d <--- list only the disabled packages
C:\> adb shell pm list packages -s <--- list only the system packages
C:\> adb shell pm list packages -u <--- list only uninstalled packages
C:\> adb shell dumpsys package packages <--- list package information
C:\> adb shell pm dump net.osmand.plus <--- list info on a package

Find out the full path to the desired package:
C:\> adb shell pm path net.osmand.plus

Copy the installer (which is always saved on Android!) to Windows.
C:\> adb pull /data/app/long-nasty-path-net.osmand.plus/osmand-base.apk

With this method you can copy all the APKs over in one robocopy command.
C:\> adb shell dumpsys package packages | findStr /i ".apk$"
The result is every app ever installed gets a Windows backup of its APK.

Stop the desired package:
C:\> adb shell am force-stop net.osmand.plus

Disable the desired package:
C:\> adb shell pm disable-user --user 0 net.osmand.plus

Remove the desired package:
C:\> adb shell pm uninstall --user 0 net.osmand.plus

Note if adb can see it, then adb can copy it over to Windows.
C:\> adb pull "/data/data/com.pkg.test/files/" .

Even if you're not rooted (most people aren't) you can copy your
Windows HOSTS file to Android if you know a few of the tricks.
<https://superuser.com/questions/938751/i-am-trying-to-push-the-file-using-adb-to-my-android-device>

Note also that "local adb" eliminates the need for the Windows PC.
<https://play.google.com/store/apps/details?id=com.draco.ladb>

5. Most Android phones have an sdslot so another option is to use
Android to put the video onto that sd card and pop it into the PC.

Having tested every single file copy method ever proposed on both
the Windows and Android newsgroups, my recommendation is simple:
a. Connect your Android phone to Windows by USB (for KISS simplicity).
b. If the phone doesn't show up in "My Computer" install OEM drivers.
c. Usually that works

If you can't get the OEM drivers to work, then I'd try the WebDav
servers on Android (unfortunately SMB servers on Android have issues).

If you can't get the WebDav servers to work, then I'd use adb with scrcpy/sndcpy which completely mirrors the phone onto the PC.

That's mostly what I do all day every day.

One advantage is my phone becomes 20 inches tall by 9 inches wide
on my computer monitor - and I can use the mouse, keyboard & clipboard.

Also, the sound is the one coming out of the computer and not the
phone - so I can loudly watch all the YouTube videos I want using either NewPipe or PipePipe (which is YouTube but without ever seeing an ad).
<https://newpipe.net>
<https://f-droid.org/en/packages/org.schabi.newpipe/>
<https://github.com/InfinityLoop1308/PipePipe>
<https://f-droid.org/en/packages/InfinityLoop1309.NewPipeEnhanced/>
--- Synchronet 3.21a-Linux NewsLink 1.2