Database Info

CyanogenMod Woes

Hey all,
I stumbled into an issue a few days ago and I'm trying to figure out how to get it resolved with minimum headache.
I downloaded the latest CyanogenMod download from h8rift's get.cm website, but unfortunately I didn't notice that it was CM9 rather than CM10 until I had flashed it and the boot animation popped up.
I didn't have a CM10 zip saved to my SD card partition, and TWRP, for some reason, would not mount to USB on either my Mac or my PC. The phone wouldn't boot into CM9, so I couldn't download the zip from there either.
So, I hit 'factory reset'.. twice, both from the bootloader, and from TWRP. Well, no luck. Now the file browser in TWRP doesn't even show my SD card's contents, just the TWRP folder. Every time I see a command line in TWRP, it tells me the SD card couldn't be mounted.
So, crap. Are all my files gone? I didn't realize factory resetting wipes the phone. I have all my photos on the SD card partition as well as a somewhat recent Titanium backup, so I'd really, really, really not like to lose those.
I understand that running a RUU will probably fix my issue, but the thing is, on the off chance that my SD card contents are still around, I'd like to be able to keep them. Will running a RUU wipe the SD card, if it still is in there somewhere? Are there any other suggestions re: getting the phone to boot, or be recognized as a USB disk? Also, if I do end up RUUing, I assume I have to unlock the bootloader again. Sigh, that was a hassle the first time.
tl;dr I'm complaining about a lot of stuff that I'll probably have to do anyways because I did something stupid and wasn't smart enough to keep backups, but if anyone wants to give pointers that'll make this process easier I will kiss your shoes and worship you forever.
Thanks.

If you end up needing to wipe your SDCard, here are some helpful tips
[Q] E:Can't mount/SD card http://forum.xda-developers.com/show....php?t=1751803
---------- Post added at 11:52 PM ---------- Previous post was at 11:29 PM ----------
denversc said:
If you end up needing to wipe your SDCard, here are some helpful tips
[Q] E:Can't mount/SD card http://forum.xda-developers.com/show....php?t=1751803
Click to expand...
Click to collapse
Oops, here is the full url:
http://forum.xda-developers.com/showthread.php?t=1751803

So I just managed to boot into CyanogenMod 9, without actually doing anything.
So it boots but can't mount the SD card. I have no idea either. Any way to mount the SD card without relocking bootloader?

Have you tried to access your sd card with a file manager app like solid explorer to see if anything is still on the card?
Sent from my Nocturnalized One XL using Forum Runner

Factory reset from the bootloader appears to wipe the sdcard and leave it in an unformatted state. I did this yesterday and fixed it by letting the phone boot back into the sense rom I was running.
Not quite sure what you can do in CM9. Have you tried connecting to your computer and seeing if windows detects a valid drive? If it doesn't maybe let windows format it, yeah I don't like this idea either, so you can at last get some files on it.

I had a similar problem after flashing a nocturnal update...
Here's what I did to resolve:
Wipe all - SD card, factory reset (all can be done inside TWRP)...then plug your phone into your computer via usb and on your phone in TWRP main screen, navigate to Mount and select USB storage. It WILL show up on your computer as unformatted - just reformat (which will wipe it again) and then let you copy files in. Just download the latest CM10 (which is working great) and flash away...
I am using a Mac computer running win xp via parallels and it worked great - I don't remember what file structure to format the SD card as, but it was the default when it brought up the format dialogue...
Hope that helps!
Sent from my One X using xda premium

[Q] S3 Locked in Boot Following CRT Down zip

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.

[Q] MicroSD not detected after JB update

I've bought a new TF300T and updated to JB. The problem is that on ICS the MicroSD was detected properly, but it's not after that update. Now after plugging the card Android hangs for a minute and does a hot reboot. The MicroSD (32GB, class 4) card isn't broken. Is there anything I can do to make the tablet work with this card?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Anyone?
Done factory reset, nothing has changed and nothing is written in adb about this.

wojtal said:
Anyone?
Done factory reset, nothing has changed and nothing is written in adb about this.
Click to expand...
Click to collapse
Power off, remove sdcard place in computer, reformat sdcard fat32, restore to tab, power on.
If there is anything you want to save from sdcard, copy to computer prior to reformat!

Done few times. Nothing changed. I've even tried another MicroSD card and it also didn't work.

wojtal said:
Done few times. Nothing changed. I've even tried another MicroSD card and it also didn't work.
Click to expand...
Click to collapse
If you are using this sdcard in the tablet, not the dock, I'm lost.
I use a 32 gig in mine full time.
Oh, bad update maybe, it would not be the first.
From http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download download proper sku and version #. Unzip once and copy to your internal sdcard. You will get an update triangle on status bar. Accept update.

I've bought this tablet without dock. I've also tried that update from Asus (but via fastboot), which also didn't solve the issue.

wojtal said:
I've bought this tablet without dock. I've also tried that update from Asus (but via fastbootidn't solve the issue.
Click to expand...
Click to collapse
If you are on 10.4.2.17 I'm lost. Maybe someone else will chime in later. I have noticed more people appear to be on in about three hours.
If I can think of anything else I repost.
Good Luck!
I want to say try cleanrom and see if possibly your sdcard slot is now your issue. I know you used in the past, but things happen.
The reason I chose that rom is most are pleased, it is a single flash and everything I tried worked. It is my standby. I am currently on stock 10.4.2.17 while trying to help someone else. Probably tomorrow back to cleanrom until cm10 gets gps.

Hey,
any update regarding this issue? I have the same problem
THanks

bump.
anyone know a fix? i have two 32gb microSD card. One is class 4 and one is class 10. The class 10 one cannot be read from the tablet, but okay from the dock. The class 4 is okay from both tablet and the dock.....tried formatting the sdcard...no use. help :crying:

AW: [Q] MicroSD not detected after JB update
My Transcent 32 GB Class 10 isn't working either - no matter which format (fat32, exfat, ntfs)
Is there any solution to it?
Wouldn't make much sense buying a 32gb class 10 without being able to use it :-/
Gesendet von meinem ASUS Transformer Pad TF300T mit Tapatalk 2
---------- Post added at 05:47 PM ---------- Previous post was at 05:06 PM ----------
A simple software update solved the problem for me.
Besides: is there any way to use the sdcard like one would on a smartphone?
I don't necessarily want to use it as external storage but rather as extended internal storage. Like photos and videos should be saved directly to that sdcard and data of some games should be saved right there as well.
Is that possible?
Gesendet von meinem ASUS Transformer Pad TF300T mit Tapatalk 2

[Nook HD+] CM10.2/SGT7 SD Install (ROM updated 12/2)

CM10.2 ROM with additional SGT7 Framework and Launcher enhancements for Nook HD+. (Nook HD to follow)
Only SD install at the moment.
Follow similar instructions from CM10.1 SD thread.
Downloads:
SD Card cyanoboot/CWM zip - sdcard-ovation-cm10.2-sdv2.img.zip *** updated (increase system partition to 500M) ***
CM10.2 Rom
cm-10.2-20131201-UNOFFICIAL-ovation.zip updated
cm-10.2-20131108-UNOFFICIAL-ovation.zip
cm-10.2-20131028-UNOFFICIAL-ovation.zip
cm-10.2-20131021-UNOFFICIAL-ovation.zip
cm-10.2-20131016-UNOFFICIAL-ovation.zip
cm-10.2-20131006-UNOFFICIAL-ovation.zip
cm-10.2-20130929-UNOFFICIAL-ovation.zip
cm-10.2-20130924-UNOFFICIAL-ovation.zip
cm-10.2-20130918-UNOFFICIAL-ovation.zip
cm-10.2-20130915-UNOFFICIAL-ovation.zip
cm-10.2-20130911-UNOFFICIAL-ovation.zip
cm-10.2-20130903-UNOFFICIAL-ovation.zip
cm-10.2-20130901-UNOFFICIAL-ovation.zip
cm-10.2-20130829-UNOFFICIAL-ovation.zip
cm-10.2-20130828-UNOFFICIAL-ovation.zip
cm-10.2-20130827-UNOFFICIAL-ovation.zip
- fstrim disabled
cm-10.2-20130827-UNOFFICIAL-ovation.zip
cm-10.2-20130818-UNOFFICIAL-ovation.zip​CM10.2 Gapps
gapps-jb-20130813-signed.zip​Changelog
CM10.2 Nightlies Changelog​
Notes:
The SD card format generated on first boot will only contain 3 partitions (boot:fat, system:ext4, data:ext4), so it is no longer compatible with the previous CM10.1 SD card. Please use a new card for testing.
The primary SD card storage is now shared (bind/fuse mounted) with the data partition and no longer a separate partition.
Backup/Restore not yet fully working.

Reserved

Reserved again

Thanks for doing this.
Loaded fine on my 8GB test card. I'll finish setup and let you know if I notice any problem. If you decide to set this up for hybrid might you use a different folder name from 10.1 version so we can test both without having to rename?

Nuor60 said:
Thanks for doing this.
Loaded fine on my 8GB test card. I'll finish setup and let you know if I notice any problem. If you decide to set this up for hybrid might you use a different folder name from 10.1 version so we can test both without having to rename?
Click to expand...
Click to collapse
thanks for testing. yes that is what i intend to do.

Slightly confused by the directions, can you update over an existing 10.1 ? Not sure if you mean a clean install needs a new card only?

I can't say what is best but as it uses a different gapps I chose not to attempt an overwrite 1. I backed up my apps to internal using titanium - 2. Re- imaged the sd card using Win32DiskImager and the img file linked above. 3. Reinstalled the ovation zip and gapps -4. Did initial card setup - 5. reloaded data to apps from titanium.

vimesxda said:
Slightly confused by the directions, can you update over an existing 10.1 ? Not sure if you mean a clean install needs a new card only?
Click to expand...
Click to collapse
Since bokbokan's 10.2 and 10.1 use different partition structures (3 vs. 4 partitions), flashing 10.2 on top of existing 10.1 will not work. So you need to start from scratch: use sdcard-ovation-cm10.2-sdv2.img to create the new 3-partition structure then flash ROM and gapps. To do this you don't need to get a new card, unless you want to keep your current 10.1 card intact to fall back to without messing around with backup/restore of 10.1. If you choose to use the existing card, you can backup your current apps and their settings as @Nuor60 suggested above, or you can simply backup the card's whole image using win32diskimager read/save option.

Sounds good, thanks for the helpful response, I think i'll try using nuor's method if I have the space.Actually titanium requires root so maybe not. Can I transfer my apps over to 10.2 from 10.1 without titanium, surely a straight Copy and paste would cause some kind of error?

vimesxda said:
Sounds good, thanks for the helpful response, I think i'll try using nuor's method if I have the space.Actually titanium requires root so maybe not.
...
Click to expand...
Click to collapse
Custom ROMs like CM come with root enabled.

I have a Nook HD+ with a hybrid install of CM10 (2013-05-12).
Can I do a clean install of this CM 10.2 version on my SD card and run it from there, or will there be a problem due to the CM10 hybrid install data remaining on the EEMC?

So I installed this today by just overwriting the existing image with win32diskimager and so far its running very nicely, smoother than previous version and faster. Thanks a lot for all the hard work on these updates, much appereciated.
Im wondering though was the old version, apps and all the data erased or is it still there somewhere? Mainly ask because I backed up using titanium before install but now when I go to restore there's nothibng to restore. Now the previous version sometimes read my SD card as internal and vice versa so I'm guessing it backed up to my SD card and now its gone? Not a massive deal as play store remembers the apps I had but would be nice to get the data back.

vimesxda said:
So I installed this today by just overwriting the existing image with win32diskimager and so far its running very nicely, smoother than previous version and faster. Thanks a lot for all the hard work on these updates, much appereciated.
Im wondering though was the old version, apps and all the data erased or is it still there somewhere? Mainly ask because I backed up using titanium before install but now when I go to restore there's nothibng to restore. Now the previous version sometimes read my SD card as internal and vice versa so I'm guessing it backed up to my SD card and now its gone? Not a massive deal as play store remembers the apps I had but would be nice to get the data back.
Click to expand...
Click to collapse
When you overwrite the image on your sd card you're going to lose everything that was on it. If you made a backup with titanium but didn't specify that you wanted to save it to a folder on your internal memory, then you lost that as well. Next time go to preferences in titanium backup and specify a folder on your internal sd card so that when you redo your sd card next time you'll have your apps.
Sent from my Barnes & Noble Nook HD+ using Tapatalk 4
---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------
kkt12 said:
I have a Nook HD+ with a hybrid install of CM10 (2013-05-12).
Can I do a clean install of this CM 10.2 version on my SD card and run it from there, or will there be a problem due to the CM10 hybrid install data remaining on the EEMC?
Click to expand...
Click to collapse
I highly doubt this world work. In fact I tried it several times with another 10.2 Rom and couldn't even get it to flash the zip. I'd wait for a true hybrid version. That's what I'm doing.
Sent from my Barnes & Noble Nook HD+ using Tapatalk 4

works fine until power off?
Nook HD+, installed fine using San Disk 32gig class 4. Works fine until power off the tablet. After power off, it boots to stock Nook rom, won't boot the sd card until I re-image it. Re-seated the sd card many times. Am I missing something?

@bokbokan:
Does your 10.2 builds have fstrim enabled?

kdavis11_1 said:
Nook HD+, installed fine using San Disk 32gig class 4. Works fine until power off the tablet. After power off, it boots to stock Nook rom, won't boot the sd card until I re-image it. Re-seated the sd card many times. Am I missing something?
Click to expand...
Click to collapse
This is my first attempt on HD+, I switched over to 10.1 and can now boot both 10.1 and stock, no problems. This version of 10.2 only boots first time, then fails. Boots straight into stock as if the SD card is no longer bootable.

I tried out the new 10.2 and its performance is so much better than that of the 10.1 builds -- the boot time is shorter and apps' response-times are much snappier.
FWIW the process I used to create the 10.2 card with customized allocation of space amongst partitions is to delete partitions 2-4 on my 10.1 card (which was created using the process described at http://forum.xda-developers.com/showpost.php?p=42785708&postcount=118), create two new ext4 partitions /system and /data, then boot to CWM recovery and flash the 10.2 ROM and gapps-jb-20130813 zip files.

digixmax said:
@bokbokan:
Does your 10.2 builds have fstrim enabled?
Click to expand...
Click to collapse
Not yet.

kdavis11_1 said:
Nook HD+, installed fine using San Disk 32gig class 4. Works fine until power off the tablet. After power off, it boots to stock Nook rom, won't boot the sd card until I re-image it. Re-seated the sd card many times. Am I missing something?
Click to expand...
Click to collapse
I've notice on my HD+ the SD card gets written to after booting and somehow it destroys the boot image. I imagine the HD+ mounts the SD card, sets a FAT and that overwrites the boot. But what do I know? I'm guessing here.
---------- Post added at 03:35 AM ---------- Previous post was at 03:30 AM ----------
digixmax said:
I tried out the new 10.2 and its performance is so much better than that of the 10.1 builds -- the boot time is shorter and apps' response-times are much snappier.
FWIW the process I used to create the 10.2 card with customized allocation of space amongst partitions is to delete partitions 2-4 on my 10.1 card (which was created using the process described at http://forum.xda-developers.com/showpost.php?p=42785708&postcount=118), create two new ext4 partitions /system and /data, then boot to CWM recovery and flash the 10.2 ROM and gapps-jb-20130813 zip files.
Click to expand...
Click to collapse
Compared to 10.1 my tablet has its tongue wagging in the breeze. It is not near as smooth as simplegreens last build for 10.1. Who'd ever think a X.2 could be so complicated? Obviously there are some major changes in the core. 4.3 Kind of reminds me of Windows, how running 98 was smooth but XP sux because it was based on the need for higher processor performance.

bokbokan said:
digixmax said:
@bokbokan:
Does your 10.2 builds have fstrim enabled?
Click to expand...
Click to collapse
Not yet.
Click to expand...
Click to collapse
Thanks, I am glad I can safely continue to use your builds on my HD+ (which has the buggy Samsung emmc part listed at http://wiki.cyanogenmod.org/w/EMMC_Bugs).

SD cards: exFAT Fat32 file sizes

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