[Android General] syserr:
(a lot to answer, I chopped it up a little)

How to restore NVRAM... proof that forums suck... I've written it at least twice and it's still a pain to find.

http://xdaforums.com/showpost.php?p=46460264&postcount=35

http://xdaforums.com/showpost.php?p=46885043&postcount=87

Good info on NVRAM:

http://xdaforums.com/showpost.php?p=46992632&postcount=2009

USB weirdness:

I'm not sure what is going on. I use ADB a lot to push files over my USB to my SDCARD. I used to pull my SDCARD and put it in my computer to write... but that is a lot of physical clunky stuff, so for less wear on connections and a little faster, I just transfer over USB with ADB. If you have CWM running, you can run ADB there too, but you need to manually mount the sdcard. But back to your problem, I'd be surprised if the USB transfer is actually the problem. More likely is bad flash... bad filesystem... bad MS Windows? I assume you are mounting the SDCARD as USB Flash through Windows. I use Linux almost exclusively, and it has assorted problems with these tablets. Their passthrough emulation of USB Flash isn't great.

How to change your layout:

So the MBR/EBR1/EBR2 that I supplied have to go with the Scatter.txt file that is with them. You *should* be able to copy all files over a stock clearsky and it will repartition and install clearsky. At that point you could replace the Recovery with CWM and install various CWM-style ROMS. I haven't played with a lot of other variations on this, so I can't say if you can throw them on "any old" SPFT-style ROM directory and then push it with SPFT.

System a mess and stalls:

You can always get everything back if you have backups. That's why I try to get folks to backup their NVRAM partition (img) as soon as possible. The A2107A is bullet-proof... you can't hard brick it. You might see if turning down the Port Speed in SPFT will solve your 40% stall problem. I use XP inside of VMware on Linux/Mint14. I believe I've had that stalling problem once out of maybe 300 times. What I would do if I were you is get your full ROM backup (the one that is 1GB or whatever) and Write Memory several times... maybe 10 times. This would give you some confidence that hardware is working well. On my XP (on VMWare on Linux) the raw Read Memory and Write Memory are maybe 1/5 the speed of the "Download" option. Someone on here said I was wrong, so apparently so people don't see this slow down with raw reads/writes. The "Download" option has some speed settings... and I'm not exactly sure what mechanisms are being used. It's almost like it starts as a USB serial port... then steps up to some other USB transport that is not serial. This could be why you get errors... the hardware may not be perfect.

SD card, stuff disappearing:

There are 2 "sdcards". You are probably writing to sdcard1 (the internal one) and then looking at sdcard2 (the external one). And to make matters worse, CWM mounts them on names a little different than the normal ROMs. SDCARDS can be: /sdcard0, /sdcard1, /sdcard2, /sdcard, /sdcard-ext or any of those down in /mnt or /media....... it all depends on how a ROM configures the mount points. You can ever do it... I'm confident that I could do away with the interal sdcard and remove all the FAT (/sdcard1) and mount the real sdcard as /sdcard1. MediaTek probably hard coded some bits, so you'd have to be careful to give them something that is valid as they expect though.

Well... thats enough typing.