I thinked that ckey is common key, and cetk is another thing.
My mistake, corrected.
I thinked that ckey is common key, and cetk is another thing.
CDecrypt v 1.0b by crediarMy mistake, corrected.
Solved, thanks!All files in the same folder, check if filenames for title.tmd etc. is correct.
Depending on how you dl'ed it, it might be simple tmd and so on.
PM'ed you, hope this works.I posted this in the other thread but it actually should go here.
Maybe I am really unlucky or maybe I am doing something wrong. I have spent the last 2 hours trying to get the modified Loadline kernel exploit to work and I have tried all the tips posted by various people.
Wii U is at 5.3.2 E, some things I try are deleting all cookies, powering down again after the hard reboot, opening multiple tabs, closing the browser and then reopening, loading up a page first, closing and then reopening, not opening any tabs at all and typing the url directly in, using wireless, using a LAN adapter.
I'm only loading it from the various sites posted not a local server. The majority of the time I get a black screen that freezes the Wii U and has some garbled pixels. If I don't reboot the console after a hard reboot then the screen just normally freezes but isn't black.
It's an AUS PAL console. Am I just really unlucky or is there more to it? Mainly using the eclipsesin URL but have tried others.
no, at least for mario maker you dont have to (so i guess its for all games)do you need to be on spoofed 5.5.0 to play Rodea or mario maker via loadliine?
I know you said that you listened to a bunch of tips, but I wanna know if you tried the one that immediately solved the problem for me (it's actually the tip that I demonstrate in my video guides). Turn on the system, go to http://eclipsesin.github.io/ and then when it loads fully, turn off the system. Then turn it on and go to the browser and it should be the first page that loads. Click on Loadiine Kernel (or is Multi-Kernel better at this point?) and then wait. It should work a lot more often and if there's an error it will almost always be the race attack failed (as opposed to simply crashing which requires a hard reset) which just requires going into the system settings before trying again.I posted this in the other thread but it actually should go here.
Maybe I am really unlucky or maybe I am doing something wrong. I have spent the last 2 hours trying to get the modified Loadline kernel exploit to work and I have tried all the tips posted by various people.
Wii U is at 5.3.2 E, some things I try are deleting all cookies, powering down again after the hard reboot, opening multiple tabs, closing the browser and then reopening, loading up a page first, closing and then reopening, not opening any tabs at all and typing the url directly in, using wireless, using a LAN adapter.
I'm only loading it from the various sites posted not a local server. The majority of the time I get a black screen that freezes the Wii U and has some garbled pixels. If I don't reboot the console after a hard reboot then the screen just normally freezes but isn't black.
It's an AUS PAL console. Am I just really unlucky or is there more to it? Mainly using the eclipsesin URL but have tried others.
Maybe thats on my side... but thats definitely not the case for me. After a successful kernal exploit i would say i have about a 50:50 change of loadiine freezing/working. (even had a freeze once, when loadiine was already started in the selection screen)Once it works successfully just relaunch the browser and click on Loadiine (vLatest) which should work basically every time given that the first one worked.
It's not just you, since 4.0 I've had just as many crashes running loadiine as with the kexploit. I've also had the one you mentioned where it crashes on the selection screen.Maybe thats on my side... but thats definitely not the case for me. After a successful kernal exploit i would say i have about a 50:50 change of loadiine freezing/working. (even had a freeze once, when loadiine was already started in the selection screen)
After the kernel exploit works. When it reloads the browser or goes back to the home button/pause menu (depends on which kernel exploit you used), I find waiting about 30 seconds before doing anything really helps. Before I started doing this after the v4 update, I couldnt use System Settings for the reset and had to turn my Wii U off instead like before.Maybe thats on my side... but thats definitely not the case for me. After a successful kernal exploit i would say i have about a 50:50 change of loadiine freezing/working. (even had a freeze once, when loadiine was already started in the selection screen)
I added it to the FAQ.ok thanks that should be on the first page
After the kernel exploit works. When it reloads the browser or goes back to the home button/pause menu (depends on which kernel exploit you used), I find waiting about 30 seconds before doing anything really helps. Before I started doing this after the v4 update, I couldnt use System Settings for the reset and had to turn my Wii U off instead like before.
For me it seems like being extremely fast works best. I do have self hosting setup however, with 2 links on the index site 1 to kernal payload and 1 to loadiine payload). So opening the browser as fast as possible after booting and instantly clicking on the links seems to gives the best results for now . (for myself at least)After the kernel exploit works. When it reloads the browser or goes back to the home button/pause menu (depends on which kernel exploit you used), I find waiting about 30 seconds before doing anything really helps. Before I started doing this after the v4 update, I couldnt use System Settings for the reset and had to turn my Wii U off instead like before.
I've also found that the speed of your internet connection and distance of your wifi router from the wii u affect the success rate quite dramatically.. The faster the exploit site loads, the less likely it is to crash... Since I'm hosting my own exploit and things are loading super quick (using no pics and no sub folders), I barely had any crashes... But again everyone seem to have their own little fix as well.. Who know if we can draw any real conclusions out of these... I hope you get it working soonthats interesting eclipse, one time I left the system sitting after the kexploit(successful) for about 30 MINUTES and it didnt work, it did the pixel screen thing.
it makes me wonder if the kexploit is really fully resident for any amount of time...
I've also found that the speed of your internet connection and distance of your wifi router from the wii u affect the success rate quite dramatically.. The faster the exploit site loads, the less likely it is to crash... Since I'm hosting my own exploit and things are loading super quick (using no pics and no sub folders), I barely had any crashes... But again everyone seem to have their own little fix as well.. Who know if we can draw any real conclusions out of these... I hope you get it working soon