Yes, that’s expected behaviour. The first boot into Android userland will reset get_unlock_ability because that’s the state a new/stock phone should be in.
If everything boots fine you are finished at this point ![]()
Yes, that’s expected behaviour. The first boot into Android userland will reset get_unlock_ability because that’s the state a new/stock phone should be in.
If everything boots fine you are finished at this point ![]()