I've gotten it to work about 3 times now, after a total of 10 hours or so of trying to beat that race attack using the webkit exploit. Obviously it's as reliable as a pancake in a thunderstorm, but some users seem to be able to get it to work within a few tries consistently. These individuals are obviously are in league with satan. If you would be so kind, how long does it take you for a successful attempt, and what do you do to make it happen? Multiple browsers open? none? reset of browser data every time? clear cookies, restart, clear cookies? sacrifice several small goats? etc, etc. Update: it seems that self-hosting is the best way to go. No goat sacrifice required! I'm guessing all ya'll that it works within the first few times either have really good internet, or are self hosting? Or using the usb-internet adapter? Please share your method, as it's nice to have such data. My method that didn't work: -Using a 4g-wifi thingi with At&T, my wii u and laptop were connected over wifi. -have that tubehax dns in place -Used http://wj44.bplaced.com/ to launch the exploit -Started Wii U, opened browser, closed all tabs, cleared all cache. Shut down Wii U -Start up Wii U again, open browser, clear cache, visit wj44.bplaced.com -Sometimes cleared cache, closed browser, opened it, then visited wj44.bplaced.com -Attempt exploit, hangs (sometimes video disconnect/black screen, or just hangs) -Go back and forth between having loads of opened tabs and no tabs -Nothing after a lot of hours Method that does work: -Host files on PC -Start Wii U, open browser, clear cache, close browser, open browser, clear cache -Run exploit -Success on first or second attempt every time It also works just going straight to the exploit off of boot and clearing nothing. I can't seem to get tcpGecko to recognize the Wii U exist this time around, but I suspect that's my PCs fault..somewhere. My previous setup had cable internet at the edge of the wifi range, and that worked only after an hour or two of doing things. Hosting files seems to help a lot. Latency issues perhaps, as it is a race attack?