this post was submitted on 20 Aug 2025
69 points (96.0% liked)
Technology
74265 readers
4193 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yesssssss!
Ehhhhh.... Maybe I'll wait a bit...
It is indeed a risk AND you must pin your current OS version, so no new update including no new feature (not sure which one one would need for now though) but more importantly no security updates.
That being said... if you do not actively try to mess it up, i.e. doing precisely what has been warned against NOT doing, it should be safe.
In doubt, if you can't afford another headset, have no actual need for rooting and have never done that before, definitely safer to wait.
Actually, those steps are the ones necessary to recover from a hard brick (re: the device is unusable because you did something you shouldn't have as root).
The actual process to root the device is simply running a few
adb
commands (so a prereq is having Developer Mode enabled).Once you have ran the exploit, your root escalation is temporary until the device is rebooted or you take additional steps to persists your root privileges (thus, potentially leading you towards a hard brick).
source: The docs