You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, I was looking for TWRP password protection, and I read the FAQ, but I had another use case that wasn't addressed by it:
I'm just looking for a way to make it harder for nontechnical users (imagine elderly parents, grandparents, toddlers, etc. who may not even understand everything on the screen) to accidentally boot into a recovery mode like TWRP and wipe their data by tapping/swiping on the wrong screen. This is for users who already trust the family member who administers their device and who would desire this kind of feature, not as a security mechanism, but as a safety mechanism for themselves.
In such scenarios, the ability to bypass the password via physical access would be a feature, not a bug—the goal is explicitly not to allow technical people to bypass it if they really need to. I think this would be a very valuable feature for such scenarios, so I thought I would post it here, as the FAQ seemed to focus solely on security and not consider other cases.
The text was updated successfully, but these errors were encountered:
Hi there, I was looking for TWRP password protection, and I read the FAQ, but I had another use case that wasn't addressed by it:
I'm just looking for a way to make it harder for nontechnical users (imagine elderly parents, grandparents, toddlers, etc. who may not even understand everything on the screen) to accidentally boot into a recovery mode like TWRP and wipe their data by tapping/swiping on the wrong screen. This is for users who already trust the family member who administers their device and who would desire this kind of feature, not as a security mechanism, but as a safety mechanism for themselves.
In such scenarios, the ability to bypass the password via physical access would be a feature, not a bug—the goal is explicitly not to allow technical people to bypass it if they really need to. I think this would be a very valuable feature for such scenarios, so I thought I would post it here, as the FAQ seemed to focus solely on security and not consider other cases.
The text was updated successfully, but these errors were encountered: