What are the implications here, for dummies? If something goes very wrong, there's no fixing it? Or can you use the Odin "go back to stock" method still? So it's just more involved than usual getting back to where you were?
It can be fixed, but it will be a pain in the but. Part of the Vooodoo magic (hah!) is that it overwrites the mbr on /dev/block/mmcblk0 to point to a custom protection image. This is a bit of a fake out to the system, and the only process that reverts the mbr to stock is the actual Voodoo uninstall process.
If you were to flash a stock kernel over the voodoo lagfix you'd end up with a busted /data partition, booting into what looks like a stock TouchWiz environment, but upon further inspection would actually be a FC hell of epic proportions.
To summarize, you can always go back to stock. If, for whatever reason, you do not un-install Voodoo correctly, getting back to stock is going to be a severe PITA.
if i understand correctly, most (if not all) AOSP builds of 2.2 shouldn't need to have voodoo uninstalled, as they use ext4 partitions, for the OTA however, i would almost guarantee that voodoo would have to be uninstalled first.
I haven't looked at the source yet. Enabling etx4 support in the kernel is trivial, it's a few lines in the config. The Eclair kernel (.29) is fully capable of supporting ext4 (i.e., Voodoo kernel), Samsung was the party who decided for some reason to go with an RFS file system on our devices. Regardless, I would always recommend uninstalling Voodoo before updating/upgrading.
The uninstall process for Voodoo is extremely easy (just create a single, empty file), it just takes a bit of time to process on the device. Once it's been uninstalled, you can continue to use the Voodoo kernel should you wish. Removing the lag-fix has no impact on the kernel.. It's like running a FAT16 partition on Windows 7. It'll still work, even though it's slow.
Facebook
Twitter
Instagram