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 fragment cts tests
Change-Id: Ic862fd9670408dab09ab5817cdec21e91aef001b
1 file changed