The other day I installed v13 of the AOSP as an update over v11. I don’t recall if this was from play store (unlikely) f-droid, or apkmirror. When I attempted to run it, it flashed and crashed. No worries, I thought, I use a different keyboard anyway.
Then I rebooted, and now I cannot unlock my phone on first boot.
Is there a way I can uninstall the update using adb
in recovery mode?
Info:
ROM: LineageOS-19.1
Device: Google Pixel 3 (blueline)
Bonus question – please only answer if you also answer my main question: I managed to get the play store to push SwiftKey to my phone, but the keyboard selection screen with AOSP and SwiftKey as radio buttons only flashes, then is replaced by the password/unlock prompt. Any way to select the functional keyboard from lock screen?
EDIT: I tried using adb install -r aosp11.apk
to install the old version, but it seems to be hitting a wall with write access:
$ adb install -r ./aosp11.apk
adb: failed to run abb_exec. Error: closed
adb: retrieving the default device installation mode failed: closedPerforming Streamed Install
adb: failed to run abb_exec. Error: closed
adb: connect error for write: closed
EDIT2: After the following, I gave up and factory reset: booted temporarily into twrp recovery [no touchscreen to unlock] flashed twrp [would not decrypt], and couldn’t locate bad kybd updates used asb shell [data wouldn’t mount]
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It’s fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities: