Re: Thumbnails, and what creates them.

On 2024-11-07 17:35, Andrews wrote:

Java Jive wrote on Thu, 7 Nov 2024 17:02:06 +0000 :
 

I assume you tried copying it already when I gave the commands necessary.

>
16:44:31 D:\Temp>C:\Programs\Samsung\platform-tools\adb.exe root

 Thanks for running the suggested test!
 I'm surprised that command didn't give an error as mine did on my unrooted
Android 13 Galaxy - but I do not know what "adb root" even does.
 Running a search for what does adb root do this comes up
  <https://duckduckgo.com/?va=d&t=hf&q=what+does+adb+root+do>
   *Understanding adb shell su and adb root Commands*
  <https://www.repeato.app/understanding-adb-shell-su-and-adb-root-commands/>
  "the command adb root restarts the adb daemon with root permissions,
   allowing you to execute ADB commands as root without entering the shell."
 Since your "adb root" works, my suggestion is that you may be able to...
1. adb pull the WifiConfigStore.xml file from Android to Windows
2. Edit it on Windows any way you like
3. adb push that now-edited WifiConfigStore.xml back to Android
 

16:45:56 D:\Temp>C:\Programs\Samsung\platform-tools\adb.exe pull
/data/misc/apexdata/com.android.wifi/WifiConfigStore.xml
adb: error: remote object
'/data/misc/apexdata/com.android.wifi/WifiConfigStore.xml' does not exist
>
16:46:09 D:\Temp>
>
There is a data directory visible in explorer under ...
>
    /Internal storage/Android
>
... but adding that to the beginning of the path makes no odds, and in
fact trying to pull a file that I know exists, because I can see it in
Explorer, also fails:
>
16:54:31 D:\Temp>C:\Programs\Samsung\platform-tools\adb.exe pull
"/Internal
storage/Android/data/com.android.systemui/cache/lockscreen_capture_land.png"
adb: error: remote object '/Internal
storage/Android/data/com.android.systemui/cache/lockscreen_capture_land.png'
does not exist
>
Make of that what you will, remembering that I don't believe this device
is rooted, although the adb root command seemed to work.

[snip]
 My advice is that since you can use the "adb root" command, that you can
almost certainly "adb pull" and "adb push" the WifiConfigStore.xml file.
 You just have to find it first. :)

As far as I have been able to establish, it's just not there.
There is a command ...
   <path>\adb backup
... which creates a backup of the phone or tablet on your computer. However, the backup so created, called backup.ab, is a unique tar file format that almost nothing else can read as is, though there are neat workarounds as long as it is not encrypted; however, because my tablet is encrypted, so is the backup, which means that the simple workarounds don't work.
A whole Perl upgrade later, where the biggest problem was actually uninstalling the previous version, to run a Perl script to extract the contents resulted only in a message that it couldn't do anything with this version 4, a version later than that for which it was written.
A whole Java upgrade later, where again the biggest problem was uninstalling the previous JDK and JRE, finally extracted it, but it seems to contain nothing useful that was not available already simply by connecting the phone to the PC in the normal way.
There is a command ...
   <path>\adb shell ls
... which lists the root, I presume, directory as ...
   acct
   bugreports
   cache
   carrier
   config
   d
   data
   default.prop
   dev
   dsp
   efs
   etc
   file_contexts.bin
   firmware
   firmware-modem
   fstab.qcom
   init
   init.carrier.rc
   init.class_main.sh
   init.container.rc
   init.environ.rc
   init.mdm.sh
   init.qcom.bms.sh
   init.qcom.class_core.sh
   init.qcom.early_boot.sh
   init.qcom.factory.rc
   init.qcom.rc
   init.qcom.sh
   init.qcom.syspart_fixup.sh
   init.qcom.usb.rc
   init.qcom.usb.sh
   init.rc
   init.recovery.qcom.rc
   init.rilchip.rc
   init.target.rc
   init.usb.configfs.rc
   init.usb.rc
   init.wifi.rc
   init.zygote32.rc
   init.zygote64_32.rc
   knox_data
   mnt
   oem
   persdata
   persist
   postrecovery.do
   preload
   proc
   property_contexts
   publiccert.pem
   root
   sbin
   sdcard
   seapp_contexts
   sepolicy
   sepolicy_version
   service_contexts
   storage
   sys
   system
   tombstones
   ueventd.qcom.rc
   ueventd.rc
   vendor
   verity_key
... which allows the following batch command to be run ...
   for /f "usebackq tokens=*" %A in (`<path>\adb shell ls`) do @if not %A==proc <path>\adb pull /%A
... and I'm currently waiting for the /sys directory to complete, but a search of those completed so far has found nothing of interest in the others.
I think the truth is the same as with all the other attempts, because the tablet is not rooted, the information I want is not available to me.
Scandalous, really.
--
Fake news kills!
I may be contacted via the contact address given on my website: www.macfh.co.uk