A strange one this. I have got myself into a situation where I think that a single apk is causing boot to fail. I have the same situation on a Nexus 4 and Nexus 7 running 4.4.

Running adb install <com.myapp.package> would hang - then the device would reboot - then would get stuck on Android is upgrading...Optimising app 1 of 1.

I can list packages through adb shell at this point - but uninstalling with

pm uninstall <com.myapp.package>

will just hang - presumably as the current process is doing something with that apk already.

If i try to boot into recovery at this point i get a dead android with a "no command" message.

Fastboot is locked on the device and its not rooted.

My only option at this point i think is to unlock fastboot but was wondering if im missing something.

EDIT: I just wiped via fastboot on one device and it works again - dont really want to do this on other device if poss


  • Start it in safe mode and remove your app.
    – 323go
    Mar 19, 2014 at 13:38
  • @323go "If i try to boot into recovery at this point i get a dead android with a "no command" message."
    – Dori
    Mar 19, 2014 at 15:04
  • 1
    No. Not recovery. Safe mode. Google it.
    – 323go
    Mar 19, 2014 at 15:21
  • 1
    Have you tried it? support.google.com/nexus/answer/2852139?hl=en - You can also take a powered-off device and hold volume-down after the logo appears to enter safe mode.
    – 323go
    Mar 19, 2014 at 16:41
  • 1
    Good luck. It's never fun when they break.
    – 323go
    Mar 19, 2014 at 17:04

1 Answer 1


The application apk will be stored in /data/app/ or system/app/ you can navigate there and rm .apk, then reboot

  • 1
    that requires root - have updated question to state the device is not rooted
    – Dori
    Mar 19, 2014 at 14:49

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .