Hi Guys, just bought meself a new 16gb micro sd card.
How can I transfer or make an image of the old card to the new one? I have many installed applications on my old card, I don't want to go through the daunting process of having to reinstall every single application.
Any help would be appreciated.
Copy the contents of the old card to your computer, then write them back to the new card.
Everything should work just the way it did before.
as above, just copy everything to the new card, , , just make sure you have hidden and system files visible before you copy/paste them.
erosennin said:
Hi Guys, just bought meself a new 16gb micro sd card.
How can I transfer or make an image of the old card to the new one? I have many installed applications on my old card, I don't want to go through the daunting process of having to reinstall every single application.
Any help would be appreciated.
Click to expand...
Click to collapse
Although you can transfer an image from one card to another its really not recommended for the stable running of the device especially after a ROM flash.
pa49 said:
Although you can transfer an image from one card to another its really not recommended for the stable running of the device especially after a ROM flash.
Click to expand...
Click to collapse
Moving your stuff from one card to another has absolutely no influence on how the device runs. Unless the new card is defective, of course
Thanks guys, am abroad at the moment. The moment I get home, I'll try as you suggested.
Thanks again
kilrah said:
Moving your stuff from one card to another has absolutely no influence on how the device runs. Unless the new card is defective, of course
Click to expand...
Click to collapse
That's just wrong!
You may get away with it but all settings and associations will be for the previous ROM and could be totally inappropriate!
WTF, we are on about moving stuff from one card to another.
Nothing to do with ROMs!
Your storage card is only for storage - ie it does not matter if you copy your files from (lets say) a smaller SD to a bigger one.
possible complications: having programs installed on the sd card.... here you could get error messages when you take the card out for the copy process. Nevermind them though as you take the card out, do your copying and then shove the new card back in....
after that just do a safety reboot and you should be fine
pa49 said:
That's just wrong!
You may get away with it but all settings and associations will be for the previous ROM and could be totally inappropriate!
Click to expand...
Click to collapse
Then you obviously didn't read what the thread was about.. The guy just has a new card and wants to copy the contents of the old one to it. Nothing about ROMs, settings etc...
Put my old card into the comp, copied everything, pasted into a folder on the desktop then dropped it all onto my new card, put it back in the phone, turned it on and everything works fine
hollinshead said:
WTF, we are on about moving stuff from one card to another.
Nothing to do with ROMs!
Click to expand...
Click to collapse
The OP mentioned installed apps on a mem card and excuse me but that DOES have something to do with ROMs.
Now you are wrong!
And before this goes any further you all believe what you want and do what you want because there's none so blind as those who will not see.
I shall not be posting further after those sort of comments, hollinshea!
pa49 said:
The OP mentioned installed apps on a mem card and excuse me but that DOES have something to do with ROMs.
Now you are wrong!
Click to expand...
Click to collapse
No! A storage card is just that, a disk with a filesystem and files on it. If you copy the same files onto another card, there's no way the system can even see anything has changed, apps or no apps. It's not about deleting/adding stuff, just having exactly the same data.
We don't "believe" anything - it's just how it is.
kilrah said:
No! A storage card is just that, a disk with a filesystem and files on it. If you copy the same files onto another card, there's no way the system can even see anything has changed, apps or no apps. It's not about deleting/adding stuff, just having exactly the same data.
We don't "believe" anything - it's just how it is.
Click to expand...
Click to collapse
+1 on this.
This may be in the wrong forum so mods please feel free to move it.
I am at work and needed some images from my Nexus's camera that were stored on the microsd card. I didn't have my cable with me so I removed the card from teh phone and inserted it in the card reader port on my laptop to copy the images. When I opened the sd card I noticed that all folders belonging to android were gone. All downloads DCIM everything. Most files that are just on the sd card without a directory are untouched. I put the card back in my phone to check for sure and everything is gone.
I'm currently using a recovery tool to try to get back my images and videos.... Hopefully I don't lose too much.
I have no idea why this would happen. Does anyone have a clue what would cause this? I have never had any trouble using a microsd card from a phone in my computer before.
Any clue how/why this happened and how to prevent it in the future?
Thanks!
Bad dismount. You probably pulled the battery without shutting down the phone first.
Did you try putting it back into the N1 to confirm lost files/folders, before further risk/modification from your computer?
HTCinToronto said:
Did you try putting it back into the N1 to confirm lost files/folders, before further risk/modification from your computer?
Click to expand...
Click to collapse
Says so right in his post.
Anyone else having SD card issues after the update?
Since the update my photos are saving to the phone's internal memory and if I change camera to save to the SD it stays until I take a photo, then it says there was a problem saving to the SD and writes to the phone again.
Using FX I can see the "Media Card" but when I click on it it says "Access Was Denied" however I can use System/ and see the SD Card folder and access it that way.
If I unmount and remount the SD card in Settings it works again for a short while both for accessing and saving photos to and then goes back to being seen but not able to be written to for photos along with looking at my gallery and seeing none of the photos saved to it.
I am going to back it up here to be safe but do I need to do a full format of it or has anyone had similar issues and fixed it?
Did you do the edit to platform.xml I got that when trying to back up TB Try flashing this then see if it helped, this is for a 910W8 but should work on any N4
Thanks mate.
I assume that is for rooted phones, yeah?
Mine is stock, not rooted.
I think it is just a bunk SD card, ah well time to warranty it with ADATA.
Udonitron said:
Thanks mate.
I assume that is for rooted phones, yeah?
Mine is stock, not rooted.
Click to expand...
Click to collapse
The zip I posted is flashable but it could be the card I had the same problem. I did a clean through diskpart on windows
Yeah it is really weird.
If I manually delete the info on the card it appears gone but when I go to format it, all that info comes back.
I did the regedit and diskpart trick and neither worked.
ADATA told me to download the SD Card Formatting exe and it tells me it is write protected when it clearly isn't.
Hence why it is not accessible on my phone and cannot be written to...no clue how to reverse it or why it happened in the 1st place.
I can't write to my card after jumping to 5.1.
Sent from my SM-N910T3 using Tapatalk
When the Samsung Galaxy S5 (SM-G900F) received official Android 6.0.1, I have manually installed that firmware on my device. Within few weeks ago it shows that my microSD card (64GB) corrupted. At that time if i connect to the PC I can access the SD card without any error. When I tap on "fix it" it format the SD and again it shows the exact same issue.
If I connect this sd card to a PC or a another Android device (runs ICS), these devices are not detect any error. Then I rebooted my S5 into a safe mode and again it shows that issue. However, this issue will fix if I reset the phone. After few days left it again appear that error.
So how do I fix this matter?
My wifes phone has the same issue.
Non rooted phone - 100% stock. Never messed with it.
After the MM update the sdcard just says corrupted.
As soon as a photo is stored or if google play music downloads a track to it it is corrupted.
Really annoying.
Going to try a full wipe now but I'm glad it's not just her phone. I thought the SD card had died and we haven't had it long.
Looks like it's something samsung have done.
Tried formatting the SDCard with a PC?
My SDCard is the same one I've had since I got the phone, through KitKat > Lollipop > MarshMallow, and has never been wiped or formatted, still got the very first photo I ever took with the phone on it
ownjoouk said:
My wifes phone has the same issue.
Non rooted phone - 100% stock. Never messed with it.
After the MM update the sdcard just says corrupted.
As soon as a photo is stored or if google play music downloads a track to it it is corrupted.
Really annoying.
Going to try a full wipe now but I'm glad it's not just her phone. I thought the SD card had died and we haven't had it long.
Looks like it's something samsung have done.
Click to expand...
Click to collapse
No need to wipe SD. Connect that SD to a PC and copy all the files.
*Detection* said:
Tried formatting the SDCard with a PC?
My SDCard is the same one I've had since I got the phone, through KitKat > Lollipop > MarshMallow, and has never been wiped or formatted, still got the very first photo I ever took with the phone on it
Click to expand...
Click to collapse
I think this issue caused by some sort of app or its a firmware issue.
Yeah it's been formatted. I did pop it into a pc to try and save everything but it demanded a wipe.
So I did.
It worked for a little bit and corrupted again. Now when I pit it in the pc it struggles to read it and the phone won't "fix it" either.
Tried to wipe it in a few different programs but it appears the card is corrupted.
It's a 64gb Samsung card. Only had it since January this year. Bought brand new from amazon.
I have another in my note 3 and that is still perfect.
The only saving grace is that Google photos had all the photos synced.
So i'm going to email Samsung about it as there has been no issues with the card until the moment the MM update hit.
ownjoouk said:
Yeah it's been formatted. I did pop it into a pc to try and save everything but it demanded a wipe.
So I did.
It worked for a little bit and corrupted again. Now when I pit it in the pc it struggles to read it and the phone won't "fix it" either.
Tried to wipe it in a few different programs but it appears the card is corrupted.
It's a 64gb Samsung card. Only had it since January this year. Bought brand new from amazon.
I have another in my note 3 and that is still perfect.
The only saving grace is that Google photos had all the photos synced.
So i'm going to email Samsung about it as there has been no issues with the card until the moment the MM update hit.
Click to expand...
Click to collapse
Try MiniTool Partition Wizard
Delete all partitions on the card > create new primary partition > Format to FAT32
MiniTool Partition Wizard free
https://www.partitionwizard.com/free-partition-manager.html
Used that to repair SDCards and USB drives a few times
You can also do it manually with elevated CMD: (Hit enter after each)
------------
diskpart
list disk
select disk x (x = being the disk number of your USB drive/card)
clean
create partition primary
active
format fs=fat32 quick
assign
exit
--------------
Try the card again
*Detection* said:
Try MiniTool Partition Wizard
Delete all partitions on the card > create new primary partition > Format to FAT32
MiniTool Partition Wizard free
https://www.partitionwizard.com/free-partition-manager.html
Used that to repair SDCards and USB drives a few times
You can also do it manually with elevated CMD: (Hit enter after each)
------------
diskpart
list disk
select disk x (x = being the disk number of your USB drive/card)
clean
create partition primary
active
format fs=fat32 quick
assign
exit
--------------
Try the card again
Click to expand...
Click to collapse
Already tried diskpart. No dice.
Just tried MiniTool Partition Manager. Still nothing. It lets you delete the partition and then creates a new partition instantly.
It has however now loaded in windows and shows 4 android folders but even after a delete on the partition and create new it makes no changes to the card.
It also wont let me add anything. Almost as if it is locked to read only.
So thanks for the advice as I can now see the card in windows "sort of". It's really slow though. But I can't put anything on it or wipe it or do anything with it really!
Windows 10 also says there are errors and when you let it error check it just stops responding.
ownjoouk said:
Already tried diskpart. No dice.
Just tried MiniTool Partition Manager. Still nothing. It lets you delete the partition and then creates a new partition instantly.
It has however now loaded in windows and shows 4 android folders but even after a delete on the partition and create new it makes no changes to the card.
It also wont let me add anything. Almost as if it is locked to read only.
So thanks for the advice as I can now see the card in windows "sort of". It's really slow though. But I can't put anything on it or wipe it or do anything with it really!
Windows 10 also says there are errors and when you let it error check it just stops responding.
Click to expand...
Click to collapse
If it still shows android folders on it, then none of the partition commands you've used, nor minitool have done anything, as you'll know, deleting all partitions on a disk completely wipes it
With MiniTool, it works a weird way, you have to basically tell it what you want to do, all steps, and then hit apply at the top, once you hit apply, it then performs the steps it looked like you had already done manually
EDIT - Just a thought, a live Linux CD/DVD/USB might have more luck, Linux doesn't care about permissions etc
*Detection* said:
If it still shows android folders on it, then none of the partition commands you've used, nor minitool have done anything, as you'll know, deleting all partitions on a disk completely wipes it
With MiniTool, it works a weird way, you have to basically tell it what you want to do, all steps, and then hit apply at the top, once you hit apply, it then performs the steps it looked like you had already done manually
EDIT - Just a thought, a live Linux CD/DVD/USB might have more luck, Linux doesn't care about permissions etc
Click to expand...
Click to collapse
I see... I have used Partition Magic in the past and if I recall you had to do this back in the old version. Completely forgot.
I've done that and it's trying to do it. It's going very sloooooooow. But it is getting further than diskpart did!
Will update when it decides to finish.
Good luck, might find it takes a few runs to undo whatever the phone/droid did to it
Unless of course it is physically damaged, but I've not had any problems with MM and my SD
EDIT - Found this from way back in 2010 in my repair folder, "Pen drive repair"
Code:
https://mega.nz/#!XdAW2R5I!sSVna0O4av5rnkTPpGuh_bkXatZpcfmr6X-R-3yjrzw
I tend to keep random programs that have fixed something difficult in the past, and put them in that repair folder, worth a shot
*Detection* said:
Good luck, might find it takes a few runs to undo whatever the phone/droid did to it
Unless of course it is physically damaged, but I've not had any problems with MM and my SD
EDIT - Found this from way back in 2010 in my repair folder, "Pen drive repair"
Code:
https://mega.nz/#!XdAW2R5I!sSVna0O4av5rnkTPpGuh_bkXatZpcfmr6X-R-3yjrzw
I tend to keep random programs that have fixed something difficult in the past, and put them in that repair folder, worth a shot
Click to expand...
Click to collapse
Will take a look at that tomorrow.
It formatted the card but as soon as it finished and mounted it Windows popped up and said there was a problem and it needed scanning.
Once it opened there were still 4 android folders on it....
Annoying.
Yea very, well it's definitely not deleting the partitions if it's still got all the old folders on it
Running the tool as Admin?
It does sound like it's physically damaged, but I thought that about a 16GB flash drive I had, and another 8GB I'd left in a tub on my desk for years because it was dead, then I used diskpart and repaired both of them the same day, and since then, minitool has fixed them
Tell you what you could try, Win32DiskImager, grab any image, say a Raspberry Pi image, and use Win32DiskImager to write the image to the card, I think that uses disk/device rather than partitions to write to, so it should overwrite absolutely everything
Then you can use Minitool to wipe and format back to FAT32 (Hopefully)
*Detection* said:
Yea very, well it's definitely not deleting the partitions if it's still got all the old folders on it
Running the tool as Admin?
It does sound like it's physically damaged, but I thought that about a 16GB flash drive I had, and another 8GB I'd left in a tub on my desk for years because it was dead, then I used diskpart and repaired both of them the same day, and since then, minitool has fixed them
Tell you what you could try, Win32DiskImager, grab any image, say a Raspberry Pi image, and use Win32DiskImager to write the image to the card, I think that uses disk/device rather than partitions to write to, so it should overwrite absolutely everything
Then you can use Minitool to wipe and format back to FAT32 (Hopefully)
Click to expand...
Click to collapse
The trouble with that is I can't write anything to it. It gives an i/o error ever time I try.
I'm tired now so i'm going to head to bed but tomorrow when I have a fresher head i'll take another look.
Will let you know how I go on. Will try that other tool you suggested.
The way Win32DiskImager writes to the disk is different to how Windows tries to write to it, basically like burning an ISO, vs copying files to a DVD
Yea, get some shut-eye, things are usually much simpler after a good nights sleep
Hi, i lost a kingstom 9GB after take out this card from a Samsung. I formatted, and after a few days , i disvovered, that card was set to be encrypted inside the phone, if someone takes out, and formats without unencrypt, on 2 or 3 cycles mor, the card will die, or lock, io root, i never found a solution for this, in my case, the card was locked, (ro), without any error in the partition.
Sent from my XT687 using XDA Premium 4 mobile app
---------- Post added at 11:33 PM ---------- Previous post was at 11:08 PM ----------
Sorry, i wrote wrong, is 8Gb, was the second sdcard lost by me, the first, was a 2Gb used on a nokia e7, that, after format this card the card was locked (ro) at all on all type of sdcard reader , usb, pc. The name, i found, is Cyclic Redundance Error, (formatted without unencrypt the filesystem)
Sent from my XT687 using XDA Premium 4 mobile app
*Detection* said:
The way Win32DiskImager writes to the disk is different to how Windows tries to write to it, basically like burning an ISO, vs copying files to a DVD
Yea, get some shut-eye, things are usually much simpler after a good nights sleep
Click to expand...
Click to collapse
Pen Drive Repair does nothing. Can't even find it.
Tried it another 2 times in MiniTool but still goes through all the motions but returns with the same four folder on the card.
I did a surface test and it found no errors. So reading it is fine. It's the writing to it where it fails.
EDIT: What I have just noticed is MiniTool states:
Capacity 59.64 Used 59.64 Unused 0B
So the card thinks it's full but there is nothing on it.
EDIT 2: And now in MiniTool is just says BadDisk. Looks like it is completely dead.
Well, there's nothing to lose by trying Win32 DI, unlikely to work,. but might as well try before writing it off
*Detection* said:
Well, there's nothing to lose by trying Win32 DI, unlikely to work,. but might as well try before writing it off
Click to expand...
Click to collapse
Gave it a shot. It wont even let me pick it as a device. Windows has stopped adding it to the "My Computer" list also.
I've wasted enough time with it. Only bought it in January this year so I've emailed Samsung both about the warranty on it and also that there is a possibility the upgrade to MM caused it on the S5.
It seems to have happened to the OP and me so I thought I would mention it to them in case.
I am not the author of this, it is from https://android.stackexchange.com/q/174799/146132 but it has some great info I thought I would share... My thanks to the author.
About a month ago the Moto G (3rdGen) of my wife was not able to recognize the SD-card 32GB Trancend premium 400x (which was formatted as adoptable storage) anymore. On this card were very important pictures and movies for us (of our new born baby). As of a certain Android version the adoptable storage is also encrypted and reading it on a PC or other phone is not possible without the encryption key. Since the phone was also not rooted it was also not possible to get the encryption key from the /data/...something directory... (see https://nelenkov.blogspot.ch/2015/06/decrypting-android-m-adopted-storage.html) So I almost gave up hope...
I bought the exact same type SD-card, also 32GB, only about a year later. Hoping that I would be able to make an exact clone of the card and I would be able to start some experiments with it without the risk of destroying something on the original card and losing all the data. When I mounted the original card under Linux it shows two partitions 17MB and about 31GB. Cloning the card with some Linux command line tools didn't gave me the same result. Next thing I tried was cloning it using HDDrawCopy, first write the entire card to an image on my harddrive. When I copied the data to my new 32GB card I noticed that the new card did not have the same capacity of the image file (image was 32.22GB, new card shows capacity of 31.11GB) so hmmmm that trick doesn't work... Luckily I also happen to have a 64GB SDcard (same type) which should have enough space for this test. So using HDDrawCopy I wrote the image to this card. Checked under Linux if I see the same partition as with the original card and this happens to be (of course it also shows about 32GB of free space not partitioned).
So I thought lets see if the Moto shows the same error with my new card in the phone and that I made an image on which I can start to try to hack the encryption off(now or in the future). To my surprise the Moto shows immediately that the transcend 32GB volume is mounted! I went to the gallery of the phone and IT SHOWS OUR PICTURES AND MOVIES again!!!
So in short when this happens buy a larger volume SD-Card (to make sure that there are enough data-block available). Use HDDrawCopy to make a bit-wise clone/image of the original card. Write the image to your new card and check if it can be read by your phone.
Never do the following or your data will be lost:
Format the cardSet your phone back to factory default (destroys your encryption key)Make the phone to forget/unmount the storage location (also destroys encryption key)upgrade to a newer version of Android (or any other major system update).
(of course make sure to make backups or cloud syncs to prevent this situation at all)
I hope this can help someone out there who might ended up in the same situation.
Unfortunately I have clicked on forget the card. Can anything be done?
Unfortunately I have clicked on forget the card. Can anything be done?
ajparag said:
Unfortunately I have clicked on forget the card. Can anything be done?
Click to expand...
Click to collapse
Unfortunately, no... When you click "Forget" the unlock token is erased and not recoverable by normal means. The daya stored on an internal SD csrd is now lost forever.
Hi, I am in a similar situation. I have a marshmellow phone with an sd card set up as adopted storage, but the phone stopped working and I needed the memory card somewhere else so I took an image backup of the SD card Partition. This is the mistake I did, should have taken the entire disk image backup. So now when I restored the image and the phone is fixed, the phone doesn't recognizes the memory card even though it still has the encryption key.
Any ideas?
The partition table is correct, the first partition "android_meta" probably has the wrong info