Groups | Search | Server Info | Login | Register


Groups > comp.mobile.android > #153856

Re: Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux)

From Maria Sophia <mariasophia@comprehension.com>
Newsgroups alt.comp.os.windows-10, alt.os.linux, comp.mobile.android
Subject Re: Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux)
Date 2026-05-09 01:24 -0600
Organization BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID <10tmng2$2qur$1@nnrp.usenet.blueworldhosting.com> (permalink)
References <10tk3hv$313u$1@nnrp.usenet.blueworldhosting.com> <10tlinb$36s18$1@dont-email.me> <10tlu96$2tdk$1@nnrp.usenet.blueworldhosting.com> <10tmenc$3drm7$1@dont-email.me> <10tmk6i$2c8j$1@nnrp.usenet.blueworldhosting.com>

Cross-posted to 3 groups.

Show all headers | View raw


Maria Sophia wrote:
> However, I have to admit I have no idea where my current driver came from.
> It may just as well have been that years ago, I installed an OEM driver.

I just checked if my PC is using a Samsung OEM ADB driver, or WinUSB,
(where I ran this while scrcpy was mirroring my Android on the PC monitor).

 C:\> pnputil /enum-drivers | findstr /i winusb
     (reported nothing)

 C:\> pnputil /enum-devices /connected | findstr /i adb
      Instance ID:  USB\VID_04E8&PID_6860&ADB\6&421596b&8&0003
      Device Description: SAMSUNG Android ADB Interface

Apparently:
 a. VID_04E8 = Samsung
 b. Device Description = Samsung

Apparently If it were WinUSB, it would say something like:
 a. Android ADB Interface or 
 b. WinUSB Device
 c. and the driver provider would be Microsoft.

 C:\> pnputil /enum-drivers | findstr /i samsung
      Provider Name:      SAMSUNG Electronics Co., Ltd.
      Provider Name:      SAMSUNG Electronics Co., Ltd.
      Class Name:         SAMSUNG Android Phone
      Provider Name:      SAMSUNG Electronics Co., Ltd.
      Class Name:         SAMSUNG Android Phone
      Provider Name:      SAMSUNG Electronics Co., Ltd.
      Class Name:         SAMSUNG Android Phone
      Provider Name:      SAMSUNG Electronics Co., Ltd.
      Provider Name:      SAMSUNG Electronics Co., Ltd.

 C:\> pnputil /enum-drivers /drivers | findstr /i oem
        pnputil /add-driver c:\oem\*.inf
        /delete-driver <oem#.inf> [/uninstall] [/force] [/reboot]
        pnputil /delete-driver oem0.inf
        pnputil /delete-driver oem1.inf /force
        /export-driver <oem#.inf | *> <target directory>
        pnputil /export-driver oem6.inf .
        Enumerate all OEM driver packages:

 C:\> pnputil /enum-drivers | findstr /i ssud
        Original Name:      ssudbus.inf
        Original Name:      ssudadb.inf
        Original Name:      ssudadb.inf
        Original Name:      ssudadb.inf
        Original Name:      ssudmdm.inf
        Original Name:      ssudrnds.inf

 C:\> pnputil /enum-drivers | findstr /i winusb
       (reports nothing so WinUSB isn't being used)
 C:\> pnputil /enum-drivers | findstr /i android_winusb
       (reports nothing so Google USB isn't being used)

 C:\> wmic path Win32_PnPSignedDriver where "DeviceName like '%ADB%'" get DeviceName,DriverProviderName,DriverVersion,InfName
       DeviceName DriverProviderName DriverVersion InfName
       SAMSUNG Android ADB Interface SAMSUNG Electronics Co., Ltd. 2.19.1.0 oem56.inf

This confirms Lawrence is likely correct, as is Paul, that I prolly' 
installed a Samsung OEM adb driver at some point in the life of this PC
although it's just as likely that Windows update installed it perhaps.

To see who installed the driver, I ran this command.
 C:\> pnputil /enum-drivers
        ... stuff ... 
       Published Name:     oem56.inf
       Original Name:      ssudadb.inf
       Provider Name:      SAMSUNG Electronics Co., Ltd.
       Driver Version:     09/26/2022 2.19.1.0
       Signer Name:        Microsoft Windows Hardware Compatibility Publisher
        ... stuff ... 

This proves the driver came from Microsoft's driver catalog, so
it's most likely Windows installed it automatically the first time
I had plugged the phone into the PC USB port (as far as I can tell).

Back to comp.mobile.android | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux) Maria Sophia <mariasophia@comprehension.com> - 2026-05-08 01:32 -0600
  Re: Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux) Maria Sophia <mariasophia@comprehension.com> - 2026-05-08 12:35 -0600
  Re: Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-08 20:57 +0000
    Re: Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux) Maria Sophia <mariasophia@comprehension.com> - 2026-05-08 18:14 -0600
      Re: Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux) Paul <nospam@needed.invalid> - 2026-05-09 00:55 -0400
        Re: Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux) Maria Sophia <mariasophia@comprehension.com> - 2026-05-09 00:28 -0600
          Re: Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux) Maria Sophia <mariasophia@comprehension.com> - 2026-05-09 01:24 -0600
            Re: Tutorial: How to install split spoofed APKs on Android using only your PC (Windows or Linux) Paul <nospam@needed.invalid> - 2026-05-09 08:37 -0400

csiph-web