@shawin Then again, you shouldn’t get that error if you’re restoring to 4.2.1..