Fix getting wrong instance when restoring non-config

Bug 36679897

When restoring the non-config fragments, the wrong index was
being used to lookup the fragment fromt the list of active
fragment states.

Test: ran breaking test in google3 and ran fragment tests
Change-Id: I73ea16550a4e7333b90e24f3dc253cad531c8e27
4 files changed