Path: ...!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Andrews <andrews@spam.net>
Newsgroups: alt.comp.os.windows-10,comp.mobile.android
Subject: Re: Extracting WiFi Passwords - SOLVED AT LAST!
Date: Sat, 9 Nov 2024 14:02:53 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <vgnq2c$2mp0$1@nnrp.usenet.blueworldhosting.com>
References: <1ktfijp2bp4fisefbf95ptanhve79ab2od@4ax.com> <vg8ufv$hoo4$1@dont-email.me> <8b3gij5v1lhafk4bqa3f3iquuns3gnbskt@4ax.com> <vg9cpt$oua4$1@dont-email.me> <lor6jbFd6ktU1@mid.individual.net> <vgamqi$ujq$1@nnrp.usenet.blueworldhosting.com> <vgaqga$10q2u$1@dont-email.me> <vgb223$746$1@nnrp.usenet.blueworldhosting.com> <vgb7lh$1idh$1@nnrp.usenet.blueworldhosting.com> <vgctte$1g9ct$1@dont-email.me> <vgdq8h$17dm$1@nnrp.usenet.blueworldhosting.com> <vgg82t$2732h$1@dont-email.me> <vggekq$1ksn$1@nnrp.usenet.blueworldhosting.com> <vggkqn$295tf$1@dont-email.me> <vgglhr$2utg$1@nnrp.usenet.blueworldhosting.com> <vgirqm$2o2ft$1@dont-email.me> <vgitog$1ch3$1@nnrp.usenet.blueworldhosting.com> <vgm951$3dr8g$1@dont-email.me> <vgmc8i$3e9fd$1@dont-email.me> <vgmd4c$3eclt$1@dont-email.me> <vgmpu1$1rhd$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Injection-Date: Sat, 9 Nov 2024 14:02:53 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="88864"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:ae+ENWlYzfVfDHSyQfZFRevtrnA= sha256:wUWdeAQnZoIIooiCu5CDGX8qpSe2FAN3YonyztfupNg=
	sha1:S2qwUujgHnDxjKaj6ZJrXzNQ7/s= sha256:L8w0HXXOxOkrjQvz2mZKTLN9Y4hM+YjEUutVqVlxoX4=
Bytes: 4785
Lines: 59

Andrews wrote on Sat, 9 Nov 2024 04:54:25 -0000 (UTC) :

> Single app backup (the app has to actually be installed already).
>  C:\app\editor\android\scrcpy> adb restore myAndroidBackup.ab

Bear in mind, for those who don't already know it, Android *never* deletes
the actual installer that was used to install an app, so it's there.

You just have to find it.

Also, note it's far easier to manage Android from Windows than from the
phone (for so many obvious reasons, I won't even list them for you).

So let's assume we want a backup on Windows of osmand~ *and* its data.

First you have to find the package name if you don't already know it.
 C:\> adb shell pm list packages | findStr /i "osmand" 
      package:net.osmand.plus

Then you have to find the location of the APK stored on your phone.
 C:\> adb shell pm path net.osmand.plus
      package:/data/app/~~k-jK7n2qHWcW_giNy6oVEA==/net.osmand.plus-6ws8wQWIkEi8vVgL5q3EdA==/base.apk

Then you can copy that APK manually if that's what you really want to do.
 C:\> adb pull /data/app/~~k-jK7n2qHWcW_giNy6oVEA==/net.osmand.plus-6ws8wQWIkEi8vVgL5q3EdA==/base.apk

Since *every* stored APK on Android is named, "base.apk", rename it:
 C:\> move base.apk net.osmand.plus_bck.apk

But nobody would copy an apk that way (unless they're writing scripts).
That's why they made all those free Android APK extraction tools.
 <https://play.google.com/store/apps/details?id=de.onyxbits.listmyapps>
 <https://play.google.com/store/apps/details?id=com.jenos.shareapkfile>
 <https://play.google.com/store/apps/details?id=sk.styk.martin.apkanalyzer>

Now that you have the APK backed up, it's time to use adb's data backup:
 C:\> adb backup -f net.osmand.plus_bck.ab net.osmand.plus
      WARNING: adb backup is deprecated and may be removed in a future release
      Now unlock your device and confirm the backup operation...

Now you have both the installer & the data on your Windows system:
 C:\> dir *osmand*
      11/09/2024  05:45 AM       146,644,539 net.osmand.plus_bck.apk
      11/09/2024  05:50 AM                47 net.osmand.plus_bck.ab

Note that I'm not sure what is in that data ball of string since the help
for adb backup says you need to copy over some things manually from your
sdcard. I suspect that's the internal sdcard they were referring to since
some people don't have an external sdcard.

To find where sdcard information is installed, I will *guess* it's in the
information that is spit out with a query using adb. Maybe this query?
 C:\> adb shell pm dump net.osmand.plus > net.osmand.plus_bck.txt

That file is over eight thousand lines long, so I'm not sure if it tells us
where the map data is stored & whether or not that's backed up.

Anyone know how to find the map data for osmand if it's stored on your
external sdcard? (Of course, you know where you put it - but this is for
general use where the user is backing up a device so they might not know.)