From Newsgroup: comp.mobile.android
Maria Sophia wrote:
I was running the last known good version 7.0.57 by TeslaCoil
because Nova Launcher was sold by TeslaCoil to Branch Metrics,
who was bad, but then it was sold to Instabridge who is much worse.
How the heck did it get updated to the latest version w/o my permission?
Something happened today with the Nova Launcher that it updated (somehow)
to the Instabridge Nova Launcher version 8.6.8 (86800) which made the
home screen not only gone, but whatever was left was completely unusable.
The entire home screen is shockingly and suddenly completley destroyed.
It's hard to describe, but it's completely locked up in a strange way.
So it's time to start over.
I downloaded the last known good version of Nova free 7.0.57 by TeslaCoil
<
https://tinyurl.com/nova-launcher> last known good version 7.0.57
<
https://mobile.softpedia.com/apk/nova-launcher/>
<
https://mobile.softpedia.com/apk/nova-launcher/7.0.57/>
<
https://mobile.softpedia.com/apk/dyn-postdownload.php/8b21f6f729320222bb5f58052aa5045a/6a6c4ad0/d0/4/1d915>
<
https://us.softpedia-secure-download.com/dl/e225364b176a7e7fdb683772e4081e74/6a6c3cdf/800000208/apk/Nova7-7.0.57.apk>
C:\software\launcher\nova\Nova7-7.0.57.apk
Name: Nova7-7.0.57.apk
Size: 8687773 bytes (8484 KiB)
SHA256: FAC38E0B6EEC04F56116ABC1CB876DBA3203E50F168436473D7C6753E21264FD
Luckily, the desktop adb was able to find Muntashirakon App Manager.
adb shell pm list packages | findstr /i muntashirakon
package:io.github.muntashirakon.AppManager
I launched Muntashirakon App Manager outside of the home screen
adb shell monkey -p io.github.muntashirakon.AppManager 1
In Muntashirakon, I uninstalled the InstaBridge Nova Launcher
& back in adb, I re-installed the last known good version.
adb install C:\software\launcher\nova\Nova7-7.0.57.apk
Performing Streamed Install
Success
In adb, I set the default home screen to nova launcher.
adb shell cmd package set-home-activity com.teslacoilsw.launcher/.NovaLauncher
Success
Since the update destroyed the app data, I cleared that crap.
adb shell pm clear com.teslacoilsw.launcher
Success
Then, I suspended the app to pause execution.
adb shell pm suspend com.teslacoilsw.launcher
Package com.teslacoilsw.launcher new suspended state: false
Then I prevented Android from auto-revoking Nova's permissions.
adb shell cmd appops set com.teslacoilsw.launcher AUTO_REVOKE_PERMISSIONS_IF_UNUSED ignore
And to prevent the play store from updating apps again, I disbled it.
adb shell pm disable-user com.android.vending
Package com.android.vending new state: disabled-user
Checking the status, I see the auto-revoike is set to ????
adb shell cmd appops get com.teslacoilsw.launcher
... (stuff) ...
AUTO_REVOKE_PERMISSIONS_IF_UNUSED: ignore
Then I checked that the intaller is NOT set to the play store.
adb shell cmd package list packages -i | findstr com.teslacoilsw.launcher
package:com.teslacoilsw.launcher installer=null
If the installer column shows "com.android.vending",
the app was installed through Play Store and can be auto-updated.
If it shows "null", the app has no installer association
(and even if the play store is re-enabled, it won't update it).
--- Synchronet 3.22a-Linux NewsLink 1.2