The patch nullifies the deviceID parameter. There's a high chance of being banned (they just need to compare the deviceID to the list they have - because they're known to have a CTCert database - and ban something else if missing, such as friend seed or NNID).
Everyone using the luma bypass is being assigned the same console ID you should wait until a better method is created that has a rng to assign a unique one to your device.
I believe that due to the method of installing al9h being updated some users that followed the newer guide won't have a new friendseed in movable.sed does anyone have the old guide so we can see whats being done differently from then to now that would prevent them from having a new movable.sed file
Ok everyone that doesn't understand whats going on should just wait till the guide is made before they start restoring backups and doing unnecessary things, more information is being gathered by the people testing how to get new movable.sed files.
No problem guys I was actually looking at this the first day of bans and gave up but then when I came back to the thread and saw everyone still going at it I tried again, also that jake made me think this is what he was doing so I got the guts to try it and it worked. :)
There should be no need for restoring a nand backup and if you've used tinyformat before then you should be good to follow what was said in previous comments.
Yes that is correct the system format after al9h is probably what generated the new friendseed in movable.sed and the friendseed was just using the old one.
The movable.sed isn't edited I think it holds the next friendseed for your console for if you need to do a system transfer so we are grabbing that seed from the movable.sed and replacing the banned one with it.