This is one heck of a way to introduce myself. I am embarrassed and frantic about what has happened. I've been using the guidance in these forums for years, never had any problems, but I usually made a backup. Because of the size of the S3 backups, I didn't have one this time.
I have a Verizon S3 on stock ROM, rooted, CWM Touch Recovery installed, bootloader locked. I flashed the CRT Down - ODEX.zip (attached) from the thread below. Everything seemed to go well, but on reboot the phone gets stuck in the boot animation. I have also contacted Scott over Scott's ROMS since this was where the file came from, but have not heard back. My first preference is to undo the changes to the modded files. Second choice is to flash the latest stock ROM (Stock Root - VRALHE - ODEX.zip) that I have downloaded, BUT I cannot get it on the phone since the phone won't boot, and for some reason CWM does not see any files on the external SD card. My last choice is to do a wipe/restore from stock, and I think I know how to do this, but it will be very painful.
Anyone in a helping mood? I don't know where to go from here. This is just terrible.
http://forum.xda-developers.com/showthread.php?t=1841802&highlight=crt
CWM won't read your SD card because it's not formatted to the correct file system. You could take your card and backup the data, format it to Fat32 then transfer the ROM over to your phone that way. I've long since lost the link to the simple format tool that I used to format my card but if you search for it you should find it in I think the General Forum...
SD card already FAT32, formatted by PC and then reformatted in phone. Thanks anyway.
undrgnd1 said:
SD card already FAT32, formatted by PC and then reformatted in phone. Thanks anyway.
Click to expand...
Click to collapse
If you reformated in phone you formatted it back to extFAT.
You are absolutely correct sir. Your assessment was dead on. Thank you very much. I can now make a backup to the external card. Unfortunately, I had to restore the phone (-#*@"*). I found that two other 64GB cards I was having problems with had the same issue. Wow! Twenty five years around computers and I just figured out how to format volumes larger than 32GB in FAT32. Thanks again. This thread is done.
Related
I tried to do a search on this but found nothing, and I'm also apologizing ahead of time if I'm posting in the wrong section.
I am trying to get my LG G2x to a stock ROM using this guide: (can't post link since it's my first post, but it's "how to unroot the tmobile g2x" at the unlocker.
I was able to follow the steps and installed clockworkmod on the phone (v4.0.1.5). I am however having problem on step 6. When I do the the backup on clockworkmod (CWM), it automatically is doing the backup on the phone's internal memory, and not the sd card.
I tried to mount the phone with the PC and cut and paste the folder to the SD card, thinking CWM would pick it up after a reboot of the phone. However, this is not the case. I tried to find the SD card by trying to do "install zip from SDcard" in CWM, but there is only a DCIM folder in the _ExternalSD folder, and nothing else. No matter what I do, the backup is always saving to the internal memory, and not the SD card. If I leave the backup on the phone's memory, it is showing up under recovery in CWM, but I'm guessing it's not possible to flash the phone while it's running from the internal memory.
I formatted the card at least 3 times, and even tried another card just to be sure, but no luck still.
Am I doing something wrong? Do I have to do something to mount the card or unmount the phone memory? If anyone could please help. I have to send in my phone for warranty in a few days, and I desperately need to get it back to stock. Thanks.
Nvflash latest recovery (5.0.2.7 i believe)
fcisco13 said:
Nvflash latest recovery (5.0.2.7 i believe)
Click to expand...
Click to collapse
Worked like a charm. I guess I had flashed the internal and SD option for nvflash, and that's what was messing up. 5.0.2.7 allows you to save only to SD card, so it worked perfectly. Thank you so much!
sideburnsam said:
Worked like a charm. I guess I had flashed the internal and SD option for nvflash, and that's what was messing up. 5.0.2.7 allows you to save only to SD card, so it worked perfectly. Thank you so much!
Click to expand...
Click to collapse
Latest also allows you to flash from internal/external.
Okay, So I normally never post in these forums. I am always reading and learning new ways to improve my Cell Phone.
Anyways, Today, I experienced a freaky Force Close. It was for my TWLauncher and no matter how many times I clicked FC, it still kept FCing not allowing me to enter into Debug mode to allow me to get to Recovery or even Odin.
Finally after clicking the Search button quick enough I was able to type in settings and then change to debug mode. I rebooted into Recovery mode and flashed to Default, no root, nothing. I then downloaded [ROM][ODIN] Stock DEODEXED KC1 [Root][Einherjar Dev Team][4.21.2011]-Whitehawkx booted that up and now Im trying to install CWM and {rom}Cwm-GB-2.3.5-Octane-V2.x.
Well first off I noticed something strange when I couldnt push from my adb so I manually went in and moved the file myself with a root file manager and placed the update.zip file and the zip file for the rom i wanted into my root.
I recovered mode, booted into CWM, and now when I try and Back up or update from zip file on sd card and I can't. Its telling me that...
"Unable to Mount Sd card"
or
E:/Can't Mount SD Card
I've tried formating SD Card from Phone and Computer. I've removed everything from SD Card, and still not working! Im soo confused. @[email protected]
I hope someone here can help me with this problem!
Thanks!
Josh
Could have something to do witb voodoo being ENABLED before flashing. Not sure though, never happened to me before.
Sent from my rockin' Galaxy S 4G using XDA Premium App
I have the same problem here!
Any suggestions? I even tried SD Formatter 3.1 to format my sd card but no luck...
TheKucho might be onto the issue. Did either of you have the sdcard formatted with the ext4 filesystem? If so, Windows won't be able to format it because it can't read ext4. I don't know about any of the apps in the market but I would think most of them are written for whatever filesystem is native to the platform (which ext4 is not, usually).
If you guys were on ext4, either mount the card via a Linux box & reformat it to FAT or you'll have to load a voodoo enabled kernel on your phone & reformat it that way.
Thanks for Reply Guys
The SD Card wasn't reformatted from the phone ever til last night.
I reformated to FAT32 on my laptop, readded my pictures to the sd card, and then moved it back to my phone...
I've tried multple sd cards, nothing seems to work. Almost as if the cell phone is finding the sd cards when in recovery mode or from the adb... I can take pictures and save them to sd, and I can mount sd to pc from usb coord, but thats it.
Yay
For anyone experiencing this problem, I have solved it thanks to the help of everyone here...
I followed the GB EXT4 Starter and installed octane 2.x-Updated
The steps worked completely, at one point it was bit fuzzy, right after finalizing EXT4 process, my phone began to boot up, load, auto reboot, but not completely, only went to splash screen, made noise, and then opned up again. OVER AND OVER.
I fixed this by battery drop, recovery mode, loading zip from sd, first the Octane, and then Busy Box.
I HAVE MY BABY BACK!
So I finally got the courage to flash a rom after dealing with an extremely sluggish Vibrant for over a year. I flashed the rom and everything was good, then I tried to get all my music on the phone. I couldn't get it on the external 16gb sd card so I figured I needed to format the card. I went into settings and It only gave me the option to format one of them, under SD card "format" wasn't even selectable. So I format the one I could and now notice a lot of missing folders. All that is left is albumthumbs, android, dcim, lost.dir, external_sd.
I'm not sure what I deleted but the phone still works fine.
What do you recommend I do? Should I odin back to stock and then load it again?
U should flash rom again
Sent from my Galaxy Mini using xda premium
Thanks for the response. That is what I figured.
Flash ROM again OR attempt recovery using a recovery tool
doctordunk said:
So I finally got the courage to flash a rom after dealing with an extremely sluggish Vibrant for over a year. I flashed the rom and everything was good, then I tried to get all my music on the phone. I couldn't get it on the external 16gb sd card so I figured I needed to format the card. I went into settings and It only gave me the option to format one of them, under SD card "format" wasn't even selectable. So I format the one I could and now notice a lot of missing folders. All that is left is albumthumbs, android, dcim, lost.dir, external_sd.
I'm not sure what I deleted but the phone still works fine.
What do you recommend I do? Should I odin back to stock and then load it again?
Click to expand...
Click to collapse
You could also connect your phone into mass storage mode to the computer and attempt a recovery using one of the many available tools if you had important information on the internal SD.
Cheers,
Stefan.
I've recently flashed vjs ROM below to my old desire.
http://forum.xda-developers.com/showthread.php?p=40191064
I've just got a new 8gb class 6 SD card to upgrade from old smaller class 2.
I think the apps for this ROM are installed to my SD card in some way.
Any tips how I can easily upgrade from old to new SD? I was thinking some kind of sector based copying technique could save me reinstalling ROM and apps? Or am I better to simply plug in new SD card, re flash ROM and reinstall apps?
Thanks in advance
Buzzlightyear2 said:
I've recently flashed vjs ROM below to my old desire.
http://forum.xda-developers.com/showthread.php?p=40191064
I've just got a new 8gb class 6 SD card to upgrade from old smaller class 2.
I think the apps for this ROM are installed to my SD card in some way.
Any tips how I can easily upgrade from old to new SD? I was thinking some kind of sector based copying technique could save me reinstalling ROM and apps? Or am I better to simply plug in new SD card, re flash ROM and reinstall apps?
Thanks in advance
Click to expand...
Click to collapse
when you flashed the rom do you remeber typing these commands into terminal emulator:
su
a2sd install
Y
N
Y
Yes exactly right
Buzzlightyear2 said:
Yes exactly right
Click to expand...
Click to collapse
ok that means that your apps are on the sd.
Which recovery do you have right now? and are you s-off?
Yes S off with clockwork recovery v5.0.2.0
Dont think it is significant but thought I'd mention that I did partition the old SD card when I had cyanogen 7 flashed to get more space for apps. I do not know if this partition still exists and if it is in use...I don't think so since I followed instructions for vjs 4.2.2 ROM.
I find partitions with android bit confusing which is frustrating as I've done it with Windows PCs for years
Buzzlightyear2 said:
Dont think it is significant but thought I'd mention that I did partition the old SD card when I had cyanogen 7 flashed to get more space for apps. I do not know if this partition still exists and if it is in use...I don't think so since I followed instructions for vjs 4.2.2 ROM.
I find partitions with android bit confusing which is frustrating as I've done it with Windows PCs for years
Click to expand...
Click to collapse
your partition is still there and its in use (all your app are on it). This is what you should do:
1. Install 4ext recovery (much better for the desire than clockwordmod). Go here: http://www.4ext.net/ Download the apk and install it to your phone. Then open the app and donwload/install the new recovery
2. boot into recovery, go to backup | restore, and choose backup
3. after its done reboot your phone
4. Take your old sd out of the phone, and put your new one in. Then follow this guide to partition the new sd: http://forum.xda-developers.com/showthread.php?t=2125513 (use the 4ext method and start at step [4])
5. Once its done reboot the phone.
6. Now put your old sd card into your pc, and copy all of the files onto the pc into a folder.
7. Take out your old sd card, and put the new one in. Then copy all the files over onto the new sd.
8. Put your new sd card into the phone, and boot into recovery.
9. Go to backup|restore and choose restore. Then select the backup.
10. reboot and your done.
Really appreciate your help. Will give that a shot and report back.
Thanks again
chromium96 said:
1. Install 4ext recovery (much better for the desire than clockwordmod).
Click to expand...
Click to collapse
Great tool...just bought the paid version
A littlebit off topic here, but I am also using that rom. Have been for 2 days now. How long have you been using it and have you had any issues with stability.
To the other guy what is the difference between cwm recovery and ext4 and why is it better for the desire if you don't mind me asking
Kind regards
Sent from my DLR_MID using xda app-developers app
Buzzlightyear2 said:
Great tool...just bought the paid version
Click to expand...
Click to collapse
Yeah its a great recovery. Lots of useful options.
Did everything else work out OK?
---------- Post added at 06:48 PM ---------- Previous post was at 06:37 PM ----------
bozie said:
A littlebit off topic here, but I am also using that rom. Have been for 2 days now. How long have you been using it and have you had any issues with stability.
To the other guy what is the difference between cwm recovery and ext4 and why is it better for the desire if you don't mind me asking
Kind regards
Sent from my DLR_MID using xda app-developers app
Click to expand...
Click to collapse
i also used that rom for about a month. It was very fast but i kept having random reboots. I ended up switching to the one in my signature. Its not as fast, but in my opinion its more stable, and i'd rather have stability than speed.
4ext is a good recovery because it has a lot of useful features like partitioning the sd (cwm has this too, but its not good), usb unbrick, touchscreen, themeable, one click full wipe, etc... I used to use cwm, and i never had any problems with it, i just recently moved to 4ext and is great.
I have not noticed any reboots as yet, although I will look out for them now lol. Will have a look into that recovery.
Thanks for the advice
Much apreciated
Sent from my DLR_MID using xda app-developers app
bozie said:
A littlebit off topic here, but I am also using that rom. Have been for 2 days now. How long have you been using it and have you had any issues with stability.
Click to expand...
Click to collapse
Couple of random reboots...no worse than cm7.2...I suspect some of reboots and lags I see are due to me not knowing what I was doing partitioning SD plus old slow class 2 SD
chromium96 said:
Did everything else work out OK?.
Click to expand...
Click to collapse
I will complete SD folder backup later when I have access to a pc...will let you know
glad I posted this question...just read excellent partition guide you linked to and also happy with 2 tools (4ext and titanium backup pro) I've learned about and bought. I owe you a beer
Buzzlightyear2 said:
I will complete SD folder backup later when I have access to a pc...will let you know
glad I posted this question...just read excellent partition guide you linked to and also happy with 2 tools (4ext and titanium backup pro) I've learned about and bought. I owe you a beer
Click to expand...
Click to collapse
Lol no need. Just press thanks
OK I partitioned new 8gb SD with 1024mb ext1 no ext2 and no swap. The remaining was fat32. Now I can plug SD card in adapter in windows PC and copy all files from old card to new sd, plug new sd into phone, boot to recovery...but no backup to restore! all the files I copied to the root of SD in windows (inc my nandroid backup) are not visible so I cannot restore my nandroid backup! In recovery all I can see is a folder called 4ext (using apply zip functionality simply to see if I can view files)
Plugging new SD back into windows I can see all the files again!
Buzzlightyear2 said:
OK I partitioned new 8gb SD with 1024mb ext1 no ext2 and no swap. The remaining was fat32. Now I can plug SD card in adapter in windows PC and copy all files from old card to new sd, plug new sd into phone, boot to recovery...but no backup to restore! all the files I copied to the root of SD in windows (inc my nandroid backup) are not visible so I cannot restore my nandroid backup! In recovery all I can see is a folder called 4ext (using apply zip functionality simply to see if I can view files)
Plugging new SD back into windows I can see all the files again!
Click to expand...
Click to collapse
If you boot into android and use a file manager can it see the files?
chromium96 said:
If you boot into android and use a file manager can it see the files?
Click to expand...
Click to collapse
No.
When I copied files from old SD to windows the PC windows would not recognise the SD directly so I put old sd in phone, booted android then turned on usb storage and copied via usb phone cable.
Windows recognised new SD so I plugged SD card into PC directly (not using phone) to copy files to new card.
I suspect this process may be the problem but do not understand why.
Copied files via USB to phone with new SD card and then restored nandroid...seems to have worked but lags I hoped would be fixed with faster class 6 card still there bit a bit better.
Thanks for all your help
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
gsmyth said:
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
Click to expand...
Click to collapse
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
jujuburi said:
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
This is the first problem I've had with it to be honest, had it or over a year and was using it in my HTC Sensation previously. I'm trying to remember if it was exFAT or FAT32, I remember a ROM (Google Edition S4 ROM) not being compatible with exFAT and checking mine out of curiosity, but just can't recall what it was and never flashed the ROM. I didn't reformat it coming from my Sensation so it hadn't changed in anyway.
Luckily all my photos were backed up to dropbox so nothing lost of too much importance. Need to get a microSD card reader to see if its completely borked or if files can be retrieved.
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Theoriginalgiga said:
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Click to expand...
Click to collapse
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
gsmyth said:
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
Click to expand...
Click to collapse
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Theoriginalgiga said:
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Click to expand...
Click to collapse
Cheers, I had re-downloaded the previous version of the ROM which I was on before hand and made sure to check the md5s but it still wouldn't boot which was annoying, but a full install from scratch may be the way to go. Never had bootloops before and was just worried after I had wiped and started a fresh and it still happened. I think the real lesson is to make sure to backup ANYTHING that is of value to you!
Luckily I had just happened to use the auto backup for photos to dropbox so got off lightly this time!
I have had the EXACT same issue 2 weeks ago.
I bought 2 x 32gig microSD cards (Sandisk)
1 for my phone and 1 for my digital camera.
Recently the 32gig one in my phone just DIED for no reason at all. Lost all my files, music, everything.
I contacted Sandisk, had it repalced. In the meanwhile i purchased a 64gig Samsung one.
I am yet to have an issue with the Samsung 64gig, but only time will tell.
On a plus note, Sandisk sent me a replacement 32gig card very quickly (infact too quick, i purchased the 64gig Samsung one on the idea that the Sandisk replacement was going to take months... in fact it only took 6 days...)
Cheers
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
jujuburi said:
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
I always use Fat32 on SD-cards. Why? It works on every Rom, with every kernel, every recovery, on every device, every camera, every computer, all the time.
When not in need of files greater than 4GB Fat32 simply is the way to go, compatibilty-wise.
gsmyth said:
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tried the card in a reader connected to my laptop but nothing. I've emailed Sandisk support so will see what they say.
Sent from my GT-I9505 using xda app-developers app