'Seeing' Android phone from Windows PC

I'm not suggesting for one moment that you've led me into the mire. As I said, I am currently regarding it as a coincidence that the card gave up shortly after being accessed via FTP. I've used FTP on my temporary replacement 4GB card with no problems so far - and it appears that Android devices can produce the "card unexpectedly removed" message under all sorts of circumstances not related to FTP.

Incidentally, my sloooow (24 hour) backup of the card seems to have worked because I have copied all the files from the backup onto my 4GB card and the on-card Apps are now working again.

Reply to
Roger Mills
Loading thread data ...

Thanks, but the standard Windows formatter did absolutely nothing - and just sat there like a lemon. What are the chances that anything else would be any different?

Reply to
Roger Mills

Unlikely. The card was actually supplied with a dash cam - and has had

16GB of data on it. But it became spare when I bought a 32GB card for the cam - so I re-formatted it and used it in the phone. It's been ok in the phone for quite a few months - until now!

Now, it won't let me re-format it - so something has gone awry.

Reply to
Roger Mills

On Sun, 31 May 2015 17:15:52 -0400, tlvp suggested ... :

More details on the nature of the problem and its solutions at .

HTH. Cheers, -- tlvp

Reply to
tlvp

Fair to excellent, as a matter of fact :-) . Cheers, -- tlvp

Reply to
tlvp

Immense. Windows itself just sits there like a lemon...

Reply to
The Natural Philosopher

It?s broken. Chuck it in the bin.

No.

Reply to
Richard Kettlewell

Surely you mean take it to the WEEE recycling centre?

Reply to
Andy Burns

I recall reports of some class 10 uSD memory cards doing strange things in certain phones (including Moto G) but I though it had been fixed now. See:

formatting link

and

formatting link

(with 4.4.4 and I thought these bugs were now long gone)

Struggling to read blocks of data with CRC errors very probably.

Allocation table mangled beyond all recovery. Might be worth running one of the file recovery programs on it to see if the manufacturers diagnostics can make any sense of what remains. Or a third party tool.

Most likely the card is a bit too quick for the phone and OS combo. (very similar faults were reported a year ago elsewhere)

Reply to
Martin Brown

The most likely explanation is that the partition table is corrupted and you will need to repartition, not just reformat. I believe that the "official" formatter from the SD Association does this . Alternatively, here is an explanation of how to do it using the partition utilities supplied with Windows, Linux and Mac OS .

FTP is no more, or less, risky than any other way of writing to the card. I suggest that you don't use the card for any data that you cannot replace easily because it seems likely that you will have the same trouble again.

How can anyone, including me, tell if we meet that criterion? Were you willing to wait for a response from an engineer at the SD Association?

Reply to
Gordon Levi

Just general side note hint for file transfer:

I use a convenient way of WiFi syncing between Android 4.3 and my PC over the WPA2 Wifi router by SyncMe android utility.

I have shared a dedicated PC folder \WIFISH and I defined for SyncMe several syncing profiles defining ways of syncing and synced Android folder.

Reply to
Poutnik

Anything's possible on this group ...

Owain

Reply to
spuorgelgoog

Yes l-)

Reply to
Richard Kettlewell

thanks - but it's probably easier to throw the card in the bin and get a new one.

Reply to
Roger Mills

I think that's the best solution!

I couldn't see how it could have done - it's strange that the problem occurred immediately after using FTP - but was almost certainly just a coincidence.

Reply to
Roger Mills

I don't think an item that size will be too much of a problem in landfill!

Reply to
Roger Mills

Yes, other sources suggested that there may be a problem with Class 10 cards. The one I have on order is a Class 6.

Reply to
Roger Mills

Not having much joy there. I've downloaded and unzipped the installer - but it then complains that it can't read the resulting .msi file!

No luck there, either. I can use DISKPART to identify and select the SD card but when I tell it to clean, it just sits there like a lemon.

Yes, I'm 99% sure that the problem *wasn't* caused by using FTP.

My phone has only 8GB if internal storage - so I *do* need a card for additional storage. I have been putting as much as possible on the card

- including all my photos and music, plus those Apps which allow themselves to be transferred to the card. I was beginning to think that that might have been a mistake. But - having eventually (it took 24 hours!) copied all the data off the failed card and restored it to a different card, all the on-card Apps work again - so the philosophy doesn't seem too bad, as long as I keep backups. Being able to access the card using FTP makes backups easier to do (although I didn't use it for this particular transfer).

I've found in the past when posing this sort of problem that some - definitely *uninformed* - people have waded in with all sorts of hair-brained suggestions. But I have been very impressed with the high quality of the responses to this particular thread - yours included!

Many thanks to everyone who has responded so far.

Reply to
Roger Mills

They do fail from time to time, I have two dead ones, one old 1G card that just doesn't appear when you plug it in and a 16G one that I can't write to any more but I think it has been physically damaged as it looks like some of the plastic is missing around the connectors but I don't have another card of the same sort to compare it to.

Reply to
dennis

I was glad to learn that, thanks.

Reply to
Robin

HomeOwnersHub website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.