help getting files off of sd card

owengerig

New member
Mar 21, 2016
3
0
0
Visit site
I have a nvidia shield tablet running Android 6.
My main question here is how to read the sd card without a device?

The reason behind my question is that every time i put the sd card in the device it will work (can view & edit files on it) for a short time then it will freeze, crash and reboot the whole device.
I really just need to get my titanium backup files from it so i can restore my device.

I have of course tried to plug it into my windows laptop
but windows wants to format the drive (doesnt understand the file system)
but i could easily spin up a linux box if that would help, or i have access to osx as well

I also tried using and otg cable and plugging it into another android device (running cyanogenmod) but it did not show any files, not sure usb host really works on that device
 

Golfdriver97

Trusted Member Team Leader
Moderator
Dec 4, 2012
35,367
113
63
Visit site
Welcome to the forums. If you can take the card out of the device when it's off, you can insert it into your PC, and try to pull the files off and then connect the tablet to the same PC.

If the card is damaged, there may not be much you can do.
 

LeoRex

Retired Moderator
Nov 21, 2012
6,223
0
0
Visit site
Judging by what you are saying, I suspect that the card may be corrupted. Windows might be trying to read in the FAT and get the file index built and fails, so it just tosses it out and asks you to format the card. On the tablet, that index failure seems to be causing a kernel panic, which reboots the device.

SD cards are all formatted using FAT32, which is a native filesystem to Windows... NOT Android. So if Windows looks at it and says "Nah..." that is most often a sign that the data on the card is toast. It doesn't take much on SD cards... they are far less 'hearty' than on board media, or HDs, etc. All it takes is a small portion of the media to go South and the whole card can go into the toilet.
 

owengerig

New member
Mar 21, 2016
3
0
0
Visit site
thanks for the greetings
I have tried putting it into my windows laptop but it wants to format the drive.

are you sure about the fat32 thing when the sd card was setup to be "Internal mode" LeoRex?
 

LeoRex

Retired Moderator
Nov 21, 2012
6,223
0
0
Visit site
are you sure about the fat32 thing when the sd card was setup to be "Internal mode" LeoRex?

Oh.... hold the phone... 'internal mode'? That changes things a bit. If it's 'portable', then the filesystem is FAT32. I just looked into this a little bit and if you selected 'internal' mode, it may have formatted the card as a native filesystem and then encrypted the data. In terms of recovery standpoint, that's bad news since that card will not be able to be read by anything once you pull it out of the phone. It's Nvidia's terminology for the new Adoptive Storage feature in Android 6.0.

Either way, the card is most likely having issues... but since it's set to internal mode, that device is most likely the only one that will be able to read it.

Not sure what to tell you as far as recovery options here. The core issue is that bad card. Had it been external/portable, then the Windows box would have been able to take a look at the files and you might have been able to get the data off. Internal? Can you get in there to copy files off before it reboots? Or does it reset as soon as you try to read it?
 

owengerig

New member
Mar 21, 2016
3
0
0
Visit site
not really sure the exact size of the directory but i only have a minute maybe 2 (if that) to copy before reboots.
i didnt even think of encryption. that really sucks. ill need to research how to turn that off
you say "native filesystem" but what would that be for android?
lets say it wasnt encrypted could osx or linux read it?

sucks too because like ive said it seems like some process that is checking the disk upon insertion, it was crashes the device
if i could get in and kill the process in time maybe that would do it

I also just tried booting into twrp recovery mode, but i cannot mount or view the sdcard from there. though that was always the case (even before this problem started)