But I have burned Ubuntu and Android HDMI over and over without problems booting. Though phoenix took about 15 times to burn it correctly. I finally got it to go once but then restored a backup of something that bricked it, and gave up on the cards I had and bought another and was able to get it to come up on the first try after phoenix. When I use a unix machine to DD the cards, while it takes a VERY long time, they do write without issues, but I have never been able to confirm the cards work, as I was burning the touchscreen version and was having nothing but problems with it. It also does it with my faster Samsung Extreame U3 32gb is also too small, though I don't remember by how much, for the 32gb image of course. I have tried to remove there partitions, format them with different formatting tools, nothing seems to work. Anyway the point is there all exactly the same size short. When I use diskimager it tells me that all three are around 900,000 bytes off. I have 3 64 Gb Samsung Evo+ cards, all three are exactly the same size, when I try to use win32diskimager all three have gone through the test for speed and sectors and all three check out perfectly, no loss of data no corruption and speeds better than advertised. More can never hurt, I guess, but its not like you're left with only a couple mb to work with. Some would say more is always better, but if you load, for instance, the 32 gb image for android, and then look at your storage stats, you are left with a fair amount of usable storage. Its definitely geared towards sd cards, and recommended over other utilities, but you also need to consider the source: Honestly, I've never had to dig into format settings past that as I've never had any issues, so others may have better recommendations for the settings if thats the tool you use. I use the default formatting settings on sd formatter, which, based on what I read in the manual, preserves the original settings for the card. This is the app I was thinking of: I would agree, likely not counteerfeit, but this app will definitely run them thru their paces and ensure you have the amount of storage advertised. So what should the file system type be, and what should the sector size be?Īnd the follow up question, does it make sense to use a a 32GB image on a 32GB card, or is it better to use a smaller image and still have some memory available for storage (i.e. I did also pick up a 64GB Samsung EVO+ card (based on discussions of cards), and that is showing 59.6GB, which again makes sense if using the 1024 vs 1000 math.Ĭan anyone comment on what formatting the card should be in? I think the 32GB cards were exFAT32 or something, but that was not an option for the 64GB card. Luke, I thought I had seen this discussion previously as well, but I couldn't find it either, which is why I started the new thread.
I tried to reformat, but didn't make a difference. Maybe it is related to the sector size, I don't know. But I was seeing that error when I tried to burn.
I was seeing the same thing in Windows Explorer, the 32GB rooted showing at 30,981,120 KB (or 29.5GB), and the card showing 29.8GB out of the packaging. What are the correct settings to format the card to? Or, should I use the 16GB image on the 32Gb card in order to have some storage space available? Thanks for the help.ĭon, I don't think they are bootleg cards, especially since all 3 showing exactly the same. I could also select sector size (it was at 512). Is anyone else having this same issue? Am I missing something? Do I need to format the cards first in a different way? I tried to format, I think it was exFAT32. I know companies do the 1000 instead of 1024 thing for how they calculate GB, and if you do that for KB, MB, and GB, you're looking at 29.8GB actual, so that makes sense.īut I would think the image for a 32Gb card should fit on a "32GB" card. All three show the exact same size of 29.8GB. I purchased three of the same card, SanDisk Ultra 32GB class 10, UHS-1. The problem I'm having is when I try to use the DD images for a 32GB card, it says that the image is too big, not enough sectors available (using Win32DiskImager).
I imagine I'm not the only person who has encountered this, but I recently picked up a few microSD cards that I wanted to use with the Pine.