Android

27905 readers

364 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules

1. All posts must be relevant to Android devices/operating system.

2. Posts cannot be illegal or NSFW material.

3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.

4. Non-whitelisted bots will be banned.

5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.

6. Memes are not allowed to be posts, but are allowed in the comments.

7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.

8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.

Community Resources:

We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.

Our Partner Communities:

!android@lemmy.ml

founded 1 year ago

MODERATORS

MargotRobbie@lemmy.world

Rooki@lemmy.world

Thekingoflorda@lemmy.world

L3s@lemmy.world

_MoveSwiftly@lemmy.world

[SOLVED] Accidently damaged an MicroSD by pulling it before it had fully ejected (discuss.tchncs.de)

submitted 4 months ago* (last edited 4 months ago) by Upstream7564@discuss.tchncs.de to c/android@lemmy.world

6 comments fedilink hide all child comments

~~I accidentally removed a MicroSD card from an Android device running Android 12 while it was being ejected. This happened because it took longer than usual (less than a few seconds), and I pulled it out without looking at the notification. Now, when I insert the MicroSD card into any Android device, it tells me to format it to use it, as a problem has occurred. It also gives me the option to format it and extend the internal storage. The third option is to skip both and do it later, which keeps the SD card unreadable by the system. The MicroSD card contains a lot of data that's important to me, and unfortunately, I had no backup, as I always considered my MicroSD as an external storage medium for such data. I would really appreciate any help on how I can resolve this issue and make the SD card data accessible again by Android. Thank you for reading! 🥲~~

Edit: Don't ask me why or how. But I put the SD Card into a phone running Android 14, and booted it. The SD Card could be actually read by the phone after it finished booting. I turned the phone off again, pulled the SD card out and put it back into it's original running Android 12 and magically it works again! My theory is that the Android 14 recognized and automatically fixed what was wrong and this made the card readable again to older Android versions.

Thanks to everyone who commented!

top 6 comments

sorted by: hot top controversial new old

[–] JohnnyCanuck@lemmy.ca 24 points 4 months ago (1 children)

I had no backup, as I always considered my MicroSD as an external storage medium for such data.

I know you're not looking for advice that would have been great before things went wrong, but... When they say to have a backup up on external storage, they don't mean make the backup and then delete the original. Then the "backup" is just the original.

Also, I don't think that microSD life expectancy is that great. I wouldn't it trust it as a sole keeper of backups.

Good luck.

[–] LostXOR@fedia.io 3 points 4 months ago

This. The way I think of it, if data isn't backed up, that data doesn't really exist. At a bare minimum, keep important data backed up in two separate locations. Ideally you should follow the 3-2-1 backup rule (a main drive, backup drive, and cloud backup fulfill the requirements).

[–] joyjoy@lemm.ee 17 points 4 months ago (1 children)

If you can load it on a linux vm, you can use fsck -v /dev/mmc0 to try to repair it.

via https://askubuntu.com/a/277867/121452

[–] Enkers@sh.itjust.works 19 points 4 months ago* (last edited 4 months ago)

Might also want to make an image of the device with dd if=/dev/DEVICE-NAME conv=sync,noerror bs=128K > sd_card.img first. It's often a good practice to make a raw backup before doing anything that changes the device.

[–] catloaf@lemm.ee 9 points 4 months ago

If it's that important, send it to a data recovery company and pay them. I'm sure this would be an easy job.

[–] MangoPenguin@lemmy.blahaj.zone 1 points 4 months ago

For important data I'd say utilize a data recovery company. IMO it' s too risky to try doing something yourself and making it worse.