Troubleshooting

From Android Open Pwn Project
Jump to: navigation, search

Updating Old Platform

It is possible to encounter a Metasploit framework package error while trying to update from an old Pwnix version (e.g. 1.5.12d on the Pwn Pad 2014) to the latest stable release.


Error:

    *lots of error noise* STDERR: E: There are problems and -y was used without --force-yes ---- *lots of error noise continued*

Fix:

    apt-get -q -y --force-yes --no-install-recommends install metasploit-framework=4.11.4-2015071402-1kali0


Failed chef run due to metasploit package Next Step Fix Next Step Re-run the Pwnix update

Pwnix Environment

Installation

Having issues installing the Pwnix Environment? Did you take all available OTA's before starting? (You should).

Issues Downloading

The environment bundle is not large but does require a stable network connection. If you are on a network with a choppy connection you may see the download notification disappear and reappear as AOPP handles the connection state change and then resumes the download. This may happen multiple times and is nothing to worry about; after the download is complete the Pwnix environment bundle is verified to ensure integrity before prompting you to start the installation process.

All known issues downloading the environment are related to bad network connectivity / slow network. If you are sure this is not the case and are still having issues please contact [email protected]

Installation never starts after hitting start

Chances are you looked away just long enough to miss both SuperSU permission prompts that are underneath the notification shade. Reboot the device and start again - you will not have to redownload the environment; AOPP will detect the downloaded environment, verify it and then prompt you to start the installation.

Installation never finishes

Depending on the device, there is a chance that the framework's aggressive sleeping may kill our worker thread out from under us. There are many states your environment be in coming out of this issue. The fix is a factory reset. If you encountered this, make sure you install any available AOPP OTAs before retrying. You can also work around this by watching your device through the installation process with the screen on (don't let it sleep) .

Performing Manual Updates


By default the PxInstaller will check every 24 hours for a Pwnix update. Checking manually is not required. It will check as long as sync is left on. In the event you would like to check for an update "manually" you can toggle the sync option on the PxInstaller account to force a check.

Steps:

  1. Starting from Settings tap Accounts
  2. Tap PxInstaller
  3. Tap the switch to turn off sync
  4. Tap the switch again to turn on sync - (it will sync immediately once turned on)


Pwnix update notification Next Step Pwnix Updating Next Step Pwnix update complete Next Step Pwnix update complete Next Step Pwnix update complete

The service should now sync and the new last sync date updated on screen. You will receive a Pwnix update notification at this time if there is an available update for your environment.

AOPP

Updating

For information about keeping AOPP and Pwnix up to date see this section.

Factory Reset

Android Host


In the event that you would like to return your AOPP device back to its out of box state you can do so with the Factory Reset functionality built into AOPP.

Steps:

  1. Starting from Settings tap Backup and Reset
  2. Tap Factory data reset
  3. Tap Reset Tablet to start factory reset


Backup and Reset Next Step Factory Reset Next Step Reset Tablet

Pwnix Chroot Environment


Pwnix factory reset coming soon.

External Adapters

External adapter not recognized

    Quick Fixes / Troubleshooting steps to try:
  1. Unplug OTG + adapter, reattach ensuring proper seating
  2. Reboot device
  3. Confirm OTG cable functional with USB drive or other known working USB adapter
  4. Confirm adapter functional with another device

Connectivity

More coming soon.

SSH


Login issues

Unstable connection

Please take Wakelock and Wifilock in Terminal Emulator and see if the issue persists.

Device Specific Information

Coming soon.