Timeline for TWRP recovery: "pm install /path/to.apk" not working
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15, 2017 at 14:04 | comment | added | bur | I see. Maybe I will try it that way. I'm guessing usually apks have the correct filename when downloaded, so all I have to do is add them to the zip. | |
| May 15, 2017 at 8:03 | comment | added | Andy Yan | I have included tens of apps in my own flashable zip and Terminal Emulator seems to be the only anomaly. That said, when I intend to add apps into the zip, I always first assume that they don't need the libs, and expel the anomaly afterwards (the anomaly will force close upon being opened, a good sign something's wrong). | |
| May 15, 2017 at 7:57 | comment | added | bur | Thanks for the info. I'm working from a clean install so updates aren't an issue, but it's probably easier to write a batch script for adb in cmd than to figure out which apps need libraries extracted etc. I can at least install a launcher and a file manager right away so that I have a working barebone install to work from. | |
| May 15, 2017 at 2:26 | comment | added | iBug |
Extract lib/armeabi and lib/armeabi-v8a for ARM and ARM64 devices, respectively.
|
|
| May 15, 2017 at 2:22 | comment | added | Andy Yan | @iBug Problem is, I have both ARM and ARM64 devices which need different sets of libs, but from the log output of the app, it seems to look for the libs in the same folder regardless of arch. Can't bother figuring out how to pre-determine the arch just to install such one minor app. If you have surefire details on how to do it, just edit it in, I'm open to experiment. | |
| May 15, 2017 at 2:06 | comment | added | iBug |
Extracting libs is as simple as issuing an unzip command. Then chmod & chown correctly and it'll work.
|
|
| May 15, 2017 at 0:24 | history | answered | Andy Yan | CC BY-SA 3.0 |