Privacy

31224 readers

967 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

Chat rooms

[Matrix/Element]Dead
Discord

much thanks to @gary_host_laptop for the logo design :)

founded 4 years ago

MODERATORS

Switching to custom rom on android device with data (infosec.pub)

submitted 10 months ago by 03wlrb@infosec.pub to c/privacy@lemmy.ml

25 comments fedilink hide all child comments

Hello all,

Currently I am debating whether or not to switch to a (preferably private/secure) custom rom on my device, however said device had been in use for a while now.

My question is the following: For those who have been in this situation, how have you dealt with the existing data on the device in terms of migration? After all, switching ROM usually involves a factory reset. Creating backups of everything is a bit tedious and timeconsuming and there is always the possibility of forgetting something.

you are viewing a single comment's thread
view the rest of the comments

[–] loganb@lemmy.world 2 points 10 months ago (5 children)

As installing a custom ROM typically involves using ADB anyways, I would suggest that you back up your device normally (copy files over to a folder on your computer), and then use the built-in backup function in ADB to make a secondary complete backup.

Also, depending on your threat model, you might not want to move any files from your old installation to your new one. Its possible that the old files, applications, and linked accounts could compromise your new installation privacy / security. I also generally enjoy starting with a clean slate after a new OS install.

[–] miss_brainfart@lemmy.ml 2 points 10 months ago (4 children)

Huh, why have I never thought of checking that. It seems obvious that you can do that with ADB, but it never came to mind.

Thank you

[–] BearOfaTime@lemm.ee 3 points 10 months ago (3 children)

ADB backup must be supported by an app for it to work, sadly. So not all app devs checked the box saying "support ADB backup". It's a bit hit and miss.

[–] loganb@lemmy.world 1 points 10 months ago (1 children)

I stand corrected, its been quite a few years since I needed to use the ADB backup so I guess back then it was more complete.

Found a good detailed explanation here.

Shame that it seems to be getting phased out for cloud backup solutions. Makes sense that google would want to control more of your data and make you pay for it.

[–] BearOfaTime@lemm.ee 2 points 10 months ago* (last edited 10 months ago)

As much as the whole "no local data, everything in the cloud" frustrates me, there is a logic to it: if everything is server-based, losing/destroying a phone isn't a problem. (Well, thats the logic we can use, Google's logic is "we want your data").

For me then, the answer becomes build more self-hosting, then getting a new phone is simply reinstalling my self-host clients and logging in.

So my short-term solution is to sync everything to home with Syncthing, using apps local backup if it supports it (some apps will backup/export to a folder on the phone), or just ensuring important data is in folders that get sync'd.

Long term is to switch to self-hosted apps as much as possible.

load more comments (1 replies)