[Q] Keep burning out SDs - need advise .... - Verizon Droid Charge

I am the following setup on my Charge
Voodoo based kernel; regular and over clock
Sd card read fix patch
EE4 fully stock up to date
CWR 4.x.x.04 - the one without voodoo options
This is my second incident with card going bad. The first time I used it for two weeks and card became unreadable. Tried reformat from the phone and on CWR level without any success.
On second ocasion phone worked also two weeks without any issues - till I suddenly got on power up "bad card" pop up. Tried to reformat - failed.
I booted into CWR and to my surprise I was able to browse the card. I deleted cache, Davlik, boot part, reapplied voodoo and ovclock kernels, reapplied card read error pathch - in all possible sequences without much susccess. I do not have voodoo controls under my version of CWR (too bad) and since I do not have memory card - I cannot download and install 3rd party voodo control to try to enable and disable and see if it makes a difference.
I am without access to my pc for a week so Odin or repartitioning lwith pit file and full stock reflash are not an option for me right now. I tried mount SD on a windows machine - without much success as it sees is un formatted. CWR sees it without issues and let's me reflash kernel and patch zips.
I am sure that I will get it working eventually - but would like to ask our opinion AFAYK what is going on? I hate having to lose my cards with pics and data with is not backed up regularly. This is my first device I lost an SD card.
I am assuming that it is related to the voodoo Linux based file system. do you think running a full stock on a voodoo has anything to do with it?
Thanks in advance

i was under the impression that the "Sd card read fix patch" wasn't needed any more.

You might have a bad device that keeps toasting your cards. Have you tried viewing your card in a Linux machine?
Sent from my GT-P1000 using XDA App

I have tried both ways - with and without the patch

You said you were able to mount your sd on a windows machine. Any reason you can't use that machine and odin off of it? Its just a quick download away.

I do not have access to a linux box. Factory reset, Odin and options under CWR are the only options that I usually use. Can I test my phone without a Linux box?

I was just thinking Linux might try to force read it since it ignores file permissions etc. Also, you can't format the SD card within CWM.
Sent from my GT-P1000 using XDA App

It was not my computer - I just wanted to test if i can see sd card on a wintel box. In the long run I do not mind doing the pit file with full stock flash - I just do not want to find myself burning more cards

If you fix it and it does it again i would definitely go to a Verizon store and have it checked out.
Sent from my GT-P1000 using XDA App

Use a small sd card sufficient enough to do everything you want to. If it happens again take it to verizon fully stock and they should replace the phone and SD.

Just to add more to the puzzle
I have second Charge absolutely the same setup.
When I tried to load SD card that is unreadable on the original Charge on the phone level
- I get the same damaged card error.
CWR on both phones can read it.

Just out of curiosity, are these 32gb cards?
Android has a known issue with 32gb cards getting corrupted if they are not formatted with a 32kb allocation size.
The workaround is to re format the card with your windows PC to FAT32, 32kb allocation size. Do a full format, not the quick format.

The two cards that got damaged are leftover cards from my fascinates. 16GB. One of them was reformatted and the other one was not - just reused it the moving all files from root folder to a folder called "Old" ( while mounted on my pc)
I used to be on an non Voodoo kernel/rom on my fascinates, when I installed voodoo kernel on Charge - file system got converted (per female voice)

Apparently I am not the only one with this problem
I stumbled upon this
http://forums.androidcentral.com/verizon-droid-charge/111200-wiping-sd-card.html#post1179362
Looks like that reusing a 16 GB card from fascinate is the issue in both instances.
I am still eager to learn what is the issue?
@Racer
Is it related to a different block size that is used by Samsung to format SD s on Charge? do you have more details on it? Do you know if I can possibly salvage my cards?

garryo said:
@Racer
Is it related to a different block size that is used by Samsung to format SD s on Charge? do you have more details on it? Do you know if I can possibly salvage my cards?
Click to expand...
Click to collapse
It is a problem with the interaction between android and some firmwares in the sdhc cards. It isn't really something that is Samsung specific.
I did some research on it and it solved my problem (similar to yours) that I had with my PNY 32gb class 10 card.
I would definitely try formatting your cards with a windows pc, full format, fat32, 32kb allocation size before I gave up on them.
here are some links:
http://forum.xda-developers.com/showthread.php?t=1010228
http://www.patriotmemory.com/forums...-LX-Series-MicroSD-Problems-on-Android-phones

Related

[Q] Damaged Micro SD card?

Hi, I have been messing with rooting and installing custom roms on my Droid Charge. I'm totally new to it and have been getting the hang of it, lots of wipes, reinstallations, etc. Unfortunately, it looks like my 32gb microSD card has been a casualty of all this. Since I had managed to install a custom rom on my Charge, my card cannot be read by any device, I've tried it in two computers and two Android phones. All are unable to format the card either, showing it in RAW format.
I believe when I was looking at some threads here, there was an issue with some of the roms maybe damaging the sd card, maybe forcing it to read-only mode? Is there a way I can definitively find out if my card is toast or I can still save it?
Thanks!
I don't have a solution but a question. Was the last rom you flashed a GB rom?
Charged up post!
No, all my roms and kernels have been 2.2 Froyo based.
Flash the SD card fix, not sure how since the SD card isn't working but I would attempt to flash a stock ee4 through Odin & actually use the SD card fix this time....
Also, you might want to consider using Titanium Backup to get all your apps saved to your SD card so you don't lose them from the wipe.
blarrick said:
Flash the SD card fix, not sure how since the SD card isn't working but I would attempt to flash a stock ee4 through Odin & actually use the SD card fix this time....
Also, you might want to consider using Titanium Backup to get all your apps saved to your SD card so you don't lose them from the wipe.
Click to expand...
Click to collapse
He said that he can't even format it in a separate reader, so changing out the software on his phone isn't going to fix anything.
To the OP: Honestly, it sounds like your card might be bad; it happens. I doubt that any software/ROM could have caused this since software can't physically damage hardware. One suggestion I can make is to try cleaning the contacts on the card; I recommend q-tips and isopropyl alcohol for that. If it still doesn't work and can't be formatted in your computers reader, you simply have a bad card. At that point, try calling VZW and hope they will replace it. They may insist on replacing your whole phone as well; I don't know. Or, you can use this as an excuse to get a faster (Class 4+) card.

SD Card Issue

Big problem. I have a Lexar 32gb sd card and today it seems to have went corrupt.
I noticed it when my ring tone change from a song to default. if i put the sd card in my PC and try to read from it it says card needs to be formated. Please tell me there is a way to recover the info on the card??? when i put the sd in the phone it says preparing then says safe to remove sd card.
TIA
JC
Hopefully just a format is all you need. I lost a 32g USB drive recently, and fortunately Corsair has great warranty service.
Sent from my Bricked Energy Sensation.
My wife's sensation did the same thing, I had to take out the SD and put it into my SD card reader on my laptop, format it and then put it back in the phone. The phone then wanted to format it again which it did and now it seems fine.
By the way, the data was intact when I put it in my SDcard reader. I was able to back up the data before I formatted it.
He said he wanted to recover the files on the SD card, not how to get the **** thing working.
You might want to check if all of the connections are clean. If they're not, a format the ****-error is likely to happen. Pure alcohol might do the trick.
If it doesn't, you could search Google or the forums for terms like 'recover corrupted micro SD'.
Good luck!
Edit: Maybe this guide does the trick?
I've an other question. I made the mistake to format my SD card with CWM and now it's only a 4 GB card (it should be 8 GB). Does someone know how I can force format it to 8 GB (with Windows or Mac OS disk utility, I can't expand the size anymore, just reformat it) ?
you can use sdformatter, a great and simple tool for those types of things, or you can download easus partition manager, its free and pretty good software for drive management.
If you want to make a linux disc, such as Ubuntu, gparted is one of the best tools available for examining, repartitioning, flagging, and fixing disks. I believe you can just download gparted and boot it from a CD or flashdrive, but I think just downloading a linux distribution is easier.

64GB micro sdxc "damaged", unable to format

So I've been looking around for help on this across various sites and I've had no luck fixing my problem.
I'm running the most recent CM10 nightlies, which I read might influence which formats the phone can read, and even after I formatted the card to FAT32 via the gui app and easeUS partition editor my phone still says my card is damaged. When I try to format it it just says "unmounting card" with the spinning circle and sits there, never unmounting and formatting like it wants to. I tried to mount/unmount and format in CWM, no dice. This card is brand new out of the package today so there's been no previous use or problems.
Am I just going to be unable to use this card while running CM10, would I have to go back to a TW ROM or stock to make it read correctly? It will show up on my computer when I plug it in and files transfer to it fine so I figure it's a problem on the phone's side. My old 16gb card from my DX works fine and that's what I'll use in the meantime but the space is dangerously low, hence why I jumped on this 64gb card when it was an Amazon deal.
If anyone has some insight or experience with this I'd really appreciate it, I'm guessing it's a problem with CM10 or I missed some tiny step somewhere but I've tried a lot and had no success.
weavethesource said:
So I've been looking around for help on this across various sites and I've had no luck fixing my problem.
I'm running the most recent CM10 nightlies, which I read might influence which formats the phone can read, and even after I formatted the card to FAT32 via the gui app and easeUS partition editor my phone still says my card is damaged. When I try to format it it just says "unmounting card" with the spinning circle and sits there, never unmounting and formatting like it wants to. I tried to mount/unmount and format in CWM, no dice. This card is brand new out of the package today so there's been no previous use or problems.
Am I just going to be unable to use this card while running CM10, would I have to go back to a TW ROM or stock to make it read correctly? It will show up on my computer when I plug it in and files transfer to it fine so I figure it's a problem on the phone's side. My old 16gb card from my DX works fine and that's what I'll use in the meantime but the space is dangerously low, hence why I jumped on this 64gb card when it was an Amazon deal.
If anyone has some insight or experience with this I'd really appreciate it, I'm guessing it's a problem with CM10 or I missed some tiny step somewhere but I've tried a lot and had no success.
Click to expand...
Click to collapse
What exactly is the partition editor you used, and why? The GUI program to format it to fat32 is sufficient...
I would guess either it's the card(what brand btw?) or the partition editor.
Brian Gove said:
What exactly is the partition editor you used, and why? The GUI program to format it to fat32 is sufficient...
I would guess either it's the card(what brand btw?) or the partition editor.
Click to expand...
Click to collapse
It's the "SanDisk Ultra 64 GB microSDXC Class 10 UHS-1 Memory Card 30MB/s with Adapter SDSDQUA-064G-U46A", I've noticed a lot of GS3 owners have been buying something similar or the same.
I used EaseUS Partition Master as well as the fat32 gui program that's been circulating, sounds like you know the one, and while the format was successful the phone still sees the card as damaged and won't completely unmount the card when I try to format it like it says.
You try formatting it on a windows computer
Sent from my SCH-I535 using xda app-developers app
Jarredw said:
You try formatting it on a windows computer
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yeah I'm using Windows 7
weavethesource said:
Yeah I'm using Windows 7
Click to expand...
Click to collapse
use this program linked below for formatting to
fat32.
http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm
weavethesource said:
It's the "SanDisk Ultra 64 GB microSDXC Class 10 UHS-1 Memory Card 30MB/s with Adapter SDSDQUA-064G-U46A", I've noticed a lot of GS3 owners have been buying something similar or the same.
I used EaseUS Partition Master as well as the fat32 gui program that's been circulating, sounds like you know the one, and while the format was successful the phone still sees the card as damaged and won't completely unmount the card when I try to format it like it says.
Click to expand...
Click to collapse
That's there exact same card I got. Format it again with the gui but DON'T use the partition program. I guarantee that's what is messing you up.
Brian Gove said:
That's there exact same card I got. Format it again with the gui but DON'T use the partition program. I guarantee that's what is messing you up.
Click to expand...
Click to collapse
Did you use the sd adapter to plug into the computer or you did it while it was inserted in the phone already? I did the latter, idk if buying an sd slot to usb would change anything.
I am having the same problem. I thought I had a bad card, so I sent it back. Now I am searching for a solution as well. I will give this a try later tonight.
weavethesource said:
Did you use the sd adapter to plug into the computer or you did it while it was inserted in the phone already? I did the latter, idk if buying an sd slot to usb would change anything.
Click to expand...
Click to collapse
I used the adapter and put it directly in my computer to format it.
Brian Gove said:
I used the adapter and put it directly in my computer to format it.
Click to expand...
Click to collapse
Ah ok, looks like I'll have to buy an sd-usb plugin then.
Had the same issue on two different cards and eventually they said that they were an unsupported raw format. Called sandisk and they said there are a lot of issues with the 64gb class 10 cards and the SGSIII. I am on my third one. This one has been working almost perfectly. I often get a unmounting remounting issue with the card, but I am not blaming the card yet as ever since I flashed the cracked aboot I have been having odd issues. I am going to put my phone back to stock and start over here today or tomorrow.
Sent from my SCH-I535 using xda app-developers app
I fixed it
I bought a multi-SD plug-in with USB, slid my card in there, ran the gui on the card, put the card back in my phone and it worked fine, the phone recognizes it. For whatever reason the card didn't want to format while it was in the phone despite my manipulations, so plugging the SD into the computer is crucial I think.
Thanks for the support guys.
I have done everything described here, and still have what the OP says. Card is not recognized, like its not even plugged in to the phone, is formatted as FAT32 and works in windows.
sparkerjc said:
I have done everything described here, and still have what the OP says. Card is not recognized, like its not even plugged in to the phone, is formatted as FAT32 and works in windows.
Click to expand...
Click to collapse
Well, I literally fought this for 3 hours, and finally I just deleted the entire partition and formatted the card in the stock ROM. Then I pulled the card and formatted with EaseUS partitioner as FAT32 and put it back in and it worked. Then I flashed back to CM10 and it still works.
How frustrating this is....

Large MicroSD troubles

I was previously using a UHC-1 speed 64GB MicroSD card in the MicroSD card slot on my TF101. This worked great in ASUS stock ICS, and also ASUS stock ICS w/ Guevor kernels. I decided to try out a few JB builds. So far, every JB build, and combination of kernels that I have tried does not allow me to read this card. I can read a smaller 4GB card just fine. Even if I put it in an adapter and stick it in the dock SD card slot, it still won't read. After verifying that I could still read it on my PC, I even reformatted the card as exFat from a PC, and that still yielded no success in reading it on the TF101.
To date, I've tried the official CM10 nightlies and EOS3 (with KAT 1.0.1 and Harmony JB kernel). None of these combinations, on any of the revisions (I tried back-dated versions also) seem to work with the card. It shows it present, but it can't mount it.
Anybody care to throw a stab at what may be going wrong?
I searched around a bit, and nobody has stated any such problems. (That or my google-fu is lacking)
I would hate to have to go back to ICS after going through all this trouble.
(Yes, I wiped, and wiped, and wiped, and wiped again. I even cleaned the entire user data section as well as everything else, I even reflashed things from scratch from the PC).
Sent from my Transformer TF101 using Tapatalk 2
ryocoon said:
I was previously using a UHC-1 speed 64GB MicroSD card in the MicroSD card slot on my TF101. This worked great in ASUS stock ICS, and also ASUS stock ICS w/ Guevor kernels. I decided to try out a few JB builds. So far, every JB build, and combination of kernels that I have tried does not allow me to read this card. I can read a smaller 4GB card just fine. Even if I put it in an adapter and stick it in the dock SD card slot, it still won't read. After verifying that I could still read it on my PC, I even reformatted the card as exFat from a PC, and that still yielded no success in reading it on the TF101.
To date, I've tried the official CM10 nightlies and EOS3 (with KAT 1.0.1 and Harmony JB kernel). None of these combinations, on any of the revisions (I tried back-dated versions also) seem to work with the card. It shows it present, but it can't mount it.
Anybody care to throw a stab at what may be going wrong?
I searched around a bit, and nobody has stated any such problems. (That or my google-fu is lacking)
I would hate to have to go back to ICS after going through all this trouble.
(Yes, I wiped, and wiped, and wiped, and wiped again. I even cleaned the entire user data section as well as everything else, I even reflashed things from scratch from the PC).
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I think it has to be fat32 formatted to be seen, at least in recovery. I believe the JB ROMs are currently unable to read NTFS, not sure about exFat.
sidneyk said:
I think it has to be fat32 formatted to be seen, at least in recovery. I believe the JB ROMs are currently unable to read NTFS, not sure about exFat.
Click to expand...
Click to collapse
Yeah you're usually safe just sticking with FAT32.
But if you get too frustrated at that SD card, I'd be glad to take it off your hands for you, haha.
ryocoon said:
I was previously using a UHC-1 speed 64GB MicroSD card in the MicroSD card slot on my TF101. This worked great in ASUS stock ICS, and also ASUS stock ICS w/ Guevor kernels. I decided to try out a few JB builds. So far, every JB build, and combination of kernels that I have tried does not allow me to read this card. I can read a smaller 4GB card just fine. Even if I put it in an adapter and stick it in the dock SD card slot, it still won't read. After verifying that I could still read it on my PC, I even reformatted the card as exFat from a PC, and that still yielded no success in reading it on the TF101.
To date, I've tried the official CM10 nightlies and EOS3 (with KAT 1.0.1 and Harmony JB kernel). None of these combinations, on any of the revisions (I tried back-dated versions also) seem to work with the card. It shows it present, but it can't mount it.
Anybody care to throw a stab at what may be going wrong?
I searched around a bit, and nobody has stated any such problems. (That or my google-fu is lacking)
I would hate to have to go back to ICS after going through all this trouble.
(Yes, I wiped, and wiped, and wiped, and wiped again. I even cleaned the entire user data section as well as everything else, I even reflashed things from scratch from the PC).
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Did you ever get a solution? I just got a 64gb UHS-1 card and am having all types of problems with accessing it. I am using KatKiss 4.3_029. I started getting no access to write access errors in TB, and copying files to it would just stop and say the disk might be full. I reformatted it exFAT using the SDFormatter tool on a PC, and wrote many fles to it on PC with no problems, but on ANdroid am seeing 0 byte files and all kinds of weirdness. I fixed permissions, I Edited the platform.xml file's WRITE_EXTERNAL_STORAGE permission. Before doing the exFAT format, I had tried formatting in TWRP. None of these things fixed my problem. I even have the problems when installed in the dock in an SDCArd adapter.
Does anybody have any other ideas?
I formatted my 64GB card as vfat within Linux and I think I did it while it was in my card reader front panel. Now I have 63GB of storage that works in twrp and 4.4.2.
Sent from my SM-N900T using XDA Premium HD app
bradysd4 said:
Did you ever get a solution? I just got a 64gb UHS-1 card and am having all types of problems with accessing it. I am using KatKiss 4.3_029. I started getting no access to write access errors in TB, and copying files to it would just stop and say the disk might be full. I reformatted it exFAT using the SDFormatter tool on a PC, and wrote many fles to it on PC with no problems, but on ANdroid am seeing 0 byte files and all kinds of weirdness. I fixed permissions, I Edited the platform.xml file's WRITE_EXTERNAL_STORAGE permission. Before doing the exFAT format, I had tried formatting in TWRP. None of these things fixed my problem. I even have the problems when installed in the dock in an SDCArd adapter.
Does anybody have any other ideas?
Click to expand...
Click to collapse
I eventually switched over to KatKiss on my TF101, but I also now use a TF701. exFAT, in general, does not work for auto-mount. Mostly due to licensing restrictions and stupidity like that for the core of the OS. You can format a 64GB card as FAT32, but you need a special tool to do it, as Windows won't let you format anything over 2GB as FAT32, and instead switches to vFAT/exFAT or NTFS, which are... less compatible and will not auto-mount. Now, I would have to go back and look at my TF101 device, but I lost the MicroSD from it (which was sad, as it had tons of pictures from a DSLR I took during a trip that not all had been cloud backed-up when I lost it). So more recent KatKiss kernels/ROMs may be able to auto-mount exFAT or vFAT along with older FAT32. NTFS will never auto-mount it seems (at least not as read/write), but can be mounted read/write if you have the right kernel or tool combination.
Also, I've never had the formatter in either CWM or TWRP work properly since the days of the OG Droid (Motorola Milestone A855).
ryocoon said:
I eventually switched over to KatKiss on my TF101, but I also now use a TF701. exFAT, in general, does not work for auto-mount. Mostly due to licensing restrictions and stupidity like that for the core of the OS. You can format a 64GB card as FAT32, but you need a special tool to do it, as Windows won't let you format anything over 2GB as FAT32, and instead switches to vFAT/exFAT or NTFS, which are... less compatible and will not auto-mount. Now, I would have to go back and look at my TF101 device, but I lost the MicroSD from it (which was sad, as it had tons of pictures from a DSLR I took during a trip that not all had been cloud backed-up when I lost it). So more recent KatKiss kernels/ROMs may be able to auto-mount exFAT or vFAT along with older FAT32. NTFS will never auto-mount it seems (at least not as read/write), but can be mounted read/write if you have the right kernel or tool combination.
Also, I've never had the formatter in either CWM or TWRP work properly since the days of the OG Droid (Motorola Milestone A855).
Click to expand...
Click to collapse
OK, I reformatted to FAT32 last night using Easus disk partition software on Windows, re-copied a bunch of files to it, but haven't had a chance to test it yet. I couldn't get mini-tool partition software (which others had mentioned using) to work on Win8.1. If that doesn't fix it, I may try to get it replaced by mfg.
UPDATE: It seems like that (reformat with easus to FAT32) fixed it. No problems today. Yay! Back to 64gb MicroSD.
bradysd4 said:
OK, I reformatted to FAT32 last night using Easus disk partition software on Windows, re-copied a bunch of files to it, but haven't had a chance to test it yet. I couldn't get mini-tool partition software (which others had mentioned using) to work on Win8.1. If that doesn't fix it, I may try to get it replaced by mfg.
Click to expand...
Click to collapse
I didn't use any partition manager software (if I was on linux, possibly, but I'm rockin' the Win 8.1 on my box at the moment, other systems in storage). I used a command line tool for formatting FAT32, it is GPL and such. Located at http://www.ridgecrop.demon.co.uk/fat32format.htm .
It seemed to work pretty well, but you have to decipher the command line options a bit.

[Q] Strange automated system restore from gingerbread vimicro 7''

Hello All,
I have a tablet here that I haven't been able to fix (yet!)
It's a mid vimicro vortex vc0882, armv7, grh55 with android 2.3 November 2011 firmware (resistive 7'') 512mb ram, 4 gb sandisk class 4 internal memory.
Although since getting this one, I now have several other much faster ones to choose from, I really like this tablet with it's chunky yet smooth navigation and so far no pc, laptop, netbook or tablet has beaten me!
Some time around early December 2012 this device experienced a system crash (freeze) that left several apps and games crashing on next boot.
This had happened once before. At which time I performed a simple factory reset from settings\privacy menu and all was well. Not the case after this more recent crash!
The device is stuck with all data as of the crash date. It will install and uninstall apps cleanly within the session, it will write to the internal sd card, yet next time the machine is started, everything is back as it was. The external sd card seems fine and unaffected (moving apps to this doesn't improve the situation, as in still not writing current configuration correctly).
ADB will push basic requests incl installation of apps, but that's as far as it goes. Any clockwork mod based tools don't help. Recovery menu has been tried with every combination. Any recovery / update from zip has been rejected due to e signature error. Tried flash tools and nothing has got through. Once the machine restarts, all is back to crash date groundhog day!
The machine is rooted (has been for most of it's life) and this didn't seem to create any problems.
I have contacted the suppliers for any firmware / recovery that they have, no joy there yet.
Sorry about the long post!
As I have root access does anyone have ideas about a system file workaround / mod or a forced clockwork mod to enable update from zip that bypasses the e-signature verification?
Permissions have been checked and system cleaned on a regular basis.
This tablet is very close to the wopad one just different buttons/button locations, with power/menu/home and back buttons.
Thanks for any positive input!
Bob
Update... Anyone out there?
After removing the internal sd card and exploring the fat 32 partition via windows, I deleted a few non essential local files (one or two of them I had to change the permissions to do so). Refreshed the disk (sd card) and the files were back. So it appears that there is an error in the sd card. Based on this idea, I tried to copy the fat 32 + full linux partitions with contents from the original 4gb sandisk to a 4gb kingston card. All appeared correct via linux type explorer software on windows, but it doesn't work for the device. Attached are the details from the partitioning software and another program that questioned the partitioning setup.
Any tips on the best software for the job + which key (possibly hidden elements) need to be included?
Thanks
Bob
3rd time lucky....
In summary, is it realistic to copy an android's internal micro sd card (system) to another blank card including correct formatting of partitions and get it to operate when inserting the copied / cloned internal memory card into the device?
A while back I asked a question regarding a different tablet, which fell on deaf ears, after a bit I sorted it myself.
Considering the nature of this forum, if this one goes "unsuggested" I will be somewhat disappointed.
With a touch of faith?
Bob
bob_mac said:
Update... Anyone out there?
After removing the internal sd card and exploring the fat 32 partition via windows, I deleted a few non essential local files (one or two of them I had to change the permissions to do so). Refreshed the disk (sd card) and the files were back. So it appears that there is an error in the sd card. Based on this idea, I tried to copy the fat 32 + full linux partitions with contents from the original 4gb sandisk to a 4gb kingston card. All appeared correct via linux type explorer software on windows, but it doesn't work for the device. Attached are the details from the partitioning software and another program that questioned the partitioning setup.
Any tips on the best software for the job + which key (possibly hidden elements) need to be included?
Thanks
Bob
Click to expand...
Click to collapse

Categories

Resources