Well, without wanting to add fire to the discussion, mihd's root has an additional advantage apart from freeing up a USB port - and that is (believe it or not): security!
My use case is the following - I use root with libPinCode (I forgot the actual name but it locks the TV with PIN on demand) in order to impose a TV watching limit for the kids. This will be especially helpful when they will be older and home alone. Chances are that they'll figure out they can bypass it if they unplug the root USB and power-cycle the TV, but it might be more difficult for them to track down this thread and figure out what is the magic file that stops root at boot. So, better security for my use case
Regarding excessive usage of internal flash - although this root increases the read/writes to internal flash, I think that flash is EMMC (like the ones found in smartphones) and has better quality than most USB drives. It should support wear leveling automatically. It should be good for years of usage - most likely something else will fail thanks to Samsung's Planned Obsolescence program (TM).
@mihd: Can you also add an "unroot" guide to your first post - in case it's needed for whatever reason? Also, can one delete samyext4.img by resetting/formatting the Samsung HUB? Also, in case of samyext4.img corruption, what is the replacement/recovery procedure (can we get a minimal shell to run a fsck on it)?
Also, a suggestion - maybe you could implement a switch (a special file on USB) that triggers reading samyext4.img from USB instead of from internal storage. That way if anything bad happens with the internal image you can boot a rooted system and repair things manually?
