05-01-2016, 09:01 PM
(04-30-2016, 09:49 PM)EricL Wrote: Very much appreciated. I've downloaded some of them and taken a look. They seem pretty decent. The only problem is that I end up having to use an image size smaller than the card, because my card is literally a few blocks smaller than the image. (Did the counterfeit check, it's fine. There is just some variation in card size due to things like overprovisioning for wear leveling.) I'd thought about using DD and just blind blasting the image on anyway, but I figure that would probably result in the same problem as a counterfeit card. I still wish there was a way to properly resize these things without using PhoenixCard, as it seems to be really unstable.
I did some looking into why this partition table is so weird, and the answers I found were really unfortunate. Basically, these images were originally designed to be flashed to eMMC and the partition table wasn't meant to be useful outside of the operating system installed. With that in mind, I'm genuinely surprised it has something that looks like a "real" partition table at all, as it could have just as easily been a block at the beginning with a bunch of smashed-together binary data. I could hope that the people over at Jide could sort that out somehow, but I don't know how much control they really have over the kernel.
Back to these DD images, there wouldn't happen to be some reserved space at the end of the image to account for slight card variations, would there? Might it actually be safe to just blast the image blind on to the card with DD?
This is the major issue about DD image, the image cannot be larger than the card size. In general, I try to look for the microSD card that has "smaller" capacity on it class and make the image. I need to know your 64GB mircoSD card actually capacity and explore whether able to make on smaller for it. However, I also don't want to make one that too small and wasting everybody microSD card capacity.
