Wednesday, 25 May 2016

Wii U emulator: Cemu 1.5.0 public release, Cemu 1.5.1 available on patreon



We recently mentioned Cemu 1.5.0, which was available to patreon supporters of the popular Wii U emulator. Version 1.5.0 has now been released publicly, and you can enjoy the performance improvement that comes with it.
Cemu 1.5.0 brings the following changes, according to the changelog:
  • New enhanced controller configuration menu and emulation
    • Configure up to 8 players (assuming the game supports it)
    • Added Pro Controller and Classic Controller emulation
    • Compatible with the original Pro Controller (using mayflash adapter)
  • Improved shader emulation and graphic bugfixes
  • Improved sound emulation
  • Reduced VRAM usage
  • Small bugfixes and changes
The Cemu 1.5.0 Wii U emulator has been said to bring huge performance improvements and run some games at full speed on reasonable PC configurations, such as in this video running Mario Kart 8 below. Note that Cemu does not play all Wii U games yet, and is actively being developed.

Meanwhile, Cemu 1.5.1 is already available to the project’s patreon supporters. Cemu 1.5.1 is a minor bug fix release and brings the following changes:
Input: Fixed input for controllers with off-center axes
Input: Added axis range scaler (50% to 200%)

H264: Fixed a bug in H264DECMemoryRequirement() that could lead to a crash.

CPU: Added new instructions to recompiler: ps_mr, ps_sel, ps_l/ps_st type 6, stfdx
CPU: Recompiler will now utilize BMI and AVX instruction set to generate faster code (if supported by host CPU)
CPU: Fixed a bug in code generated by recompiler for FSUB & FSUBS where the result would incorrectly become -0.0 instead of 0.0

AX: Added API AXSetVoiceSrcRatio()
AX: Fixed a bug in voice volume update
AX: Increased audio volume
AX: Added logging for audio API

GX2: Fixed wrong colors for certain texture dump formats
GX2: Fixed vertex ordering for special cases when PRIMITIVE_RECTS is used
GX2: New implementation for tiling aperature. Still heavily work-in-progress.
Mario-Kart-8
Reddit have an interesting FAQ explaining, among other things, why Cemu is not open source. I felt it was an interesting read:
Q: Why is it closed source?
A: “I have a very strong vision on how the future of Cemu should look like. This includes potential contributors with whom I am already in talks with. I believe that for speedy progress, a small team of long-term, dedicated and skilled team members is better than a big team of temporary contributors. Why? Because every contributor first has to acquire the necessary knowledge about the emulated system. More knowledge means more effective emulator development since a lot of time can be saved by 1) fixing bugs faster 2) implementing features correctly on first attempt. For this approach open-source is simply not necessary. In fact, it is easier to get talented developers to join long-term when their name will have more meaning in the credits. I have also considered donation-driven development. It works very well for artists and comic authors, and I see it as a great incentive for emulator development too. But it would be problematic for a open-source project.

But of course there are other concerns as well, like development suddenly focusing on a direction which is not favorable to the original intentions of the emulator. Example: Focus on hacky solutions to get games into playable state earlier. I can see this happen in a open-source environment more likely, because piracy can become the main source for development motivation. Another example: Splatoon is moving towards playability fast, but online features are of low priority to avoid people using the emulator to cheat in online-play and ruin the experience for everyone. With open-source code there is no easy way to steer the development focus away.
Needless to say there are personal reasons as well. Like not wanting to lose control over the project and being slightly reluctant to share the code with people who have no respect for the effort and time it took to get this far. Not to mention the 1000 messages I received along the lines of “This emulator is doomed when it doesn’t go open-source”. It makes me want to prove them otherwise. Oh and as I already stated, if development on Cemu gets stuck for a long period of time or if it is abandoned, the source code will be released anyway. I agree with the sentiment that the knowledge should not go to waste.”
Considering that the project is generating more than $2000 a month on patreon alone, I feel the authors are on good track to make it a full-time thing… How does the community feel about this?

Download Cemu 1.5.0 – Wii U emulator


Source: Cemu.info, via hackinformer

Tuesday, 17 May 2016

Wii U emulator: Cemu 1.5.0 runs Mario Kart 8 at full speed (Video)

Cemu 1.5.0 was released a couple days ago to people who are supporting the project on patreon, and it will most likely be released publicly to other people in the weeks to come.
The official changelog is as follows:
  • New enhanced controller configuration menu and emulation
    • Configure up to 8 players (assuming the game supports it)
    • Added Pro Controller and Classic Controller emulation
    • Compatible with the original Pro Controller (using mayflash adapter)
  • Improved shader emulation and graphic bugfixes
  • Improved sound emulation
  • Reduced VRAM usage
  • Small bugfixes and changes
Mario-Kart-8
Of course, a changelog alone is not what the end user wants, and the community delivered, with countless people showcasing the emulator in videos on Youtube. Check for example this video of Mario Kart 8 running on Cemu 1.5.0 at full speed, by GBATemp member reznoire:

Download Cemu

Cemu 1.5.0 is currently only available for patreon supporters of the project, but you can download Cemu version 1.4.2 on their official site here. 1.5.0 will become publicly available in the weeks to come.

Tuesday, 10 May 2016

WUDecrypt Released – decrypt Wii U Disc images on MacOS, Linux, and Windows

Developer Makikatze dropped by the GBATemp forums this week to release Wii U tool WUDecrypt.

What is WUDecrypt

WUDecrypt is an open source tool to decrypt Wii U disc images in the WUD format.
Tools already exist to decrypt those Wii U images  provided you have the right set of keys, but they are Windows only. Makikatze’s tool is compatible with Linux and MacOS (and Windows as well). It’s also open source if you feel like contributing. WUDecrypt is programmed in C.
This is a “work in progress” release and the developer mentions the tool will be slow and might crash.

WUDecrypt – Download & use

The source code can be found on the same github repo.
wiiu
The Readme has the following instructions to run the decryption process:

For wudecrypt to work, you will need a WUD image, the corresponding disc key and the Wii U common key. If you have all of these files, you can run wudecrypt via the following command:
wudecrypt path/to/image.wud /path/to/output /path/to/commonkey.bin /path/to/disckey.bin
wudecrypt has a fifth optional argument which can be SI, UP, GIor GM depending on which partition types you want to extract. To play the decrypted image, extracting only the GM type partitions should be enough. I mostly introduced this function as the extraction takes a very long time and it tries to avoid a whole lot of data you won’t need.

Thursday, 21 April 2016

Proof of concept webkit exploit running on PS4 firmwares 2.xx

Developer Fire30 released a webkit exploit proof of concept for the PS4, ported from a webkit heap buffer overflow revealed in 2014. I haven’t tested this myself, and this is still unconfirmed information at this point.
Fire30 says the exploit should run on any PS4 firmware below 2.50, although he mentions parts of the exploit implementation will only work on firmware 2.03, presumably because this is the firmware he’s using to write the code.
There’s not much to be said about this at this point, although in theory the kernel exploits BadIRET and dlclose could be ported to this exploit, if confirmed legit: it has been mentioned these kernel exploits are compatible up to firmware 2.xx, and the only thing preventing those from being used on any other firmware than 1.76 so far was because the only publicly available userland exploit has been the 1,76 webkit exploit.
CVE-2014-1303
A port of the dlclose exploit to this new webkit vulnerability could bring some Linux joy to more PS4 users, and help decrease the current asking price for hackable PS4s.

Download and install the CVE 2014-1303 Proof Of Concept for PS4

You can Download Fire30’s proof of concept on his github here. You’ll need a PS4 running below firmware 2.50, ideally firmware 2.03. According to the readme:
a poc for the CVE 2014-1303 originally disclosed by Liang Chen. It has been tested to work on system firmware 2.03, but should work for systems on a firmware < 2.50, the ROP test will however only work on 2.03.
Usage
You need to edit the dns.conf to point to the ip address of your machine, and modify your consoles dns settings to point to it as well. Then run
python fakedns.py -c dns.conf
then
python server.py
Debug output will come from this process.
Navigate to the User’s Guide page on the PS4 and various information should be printed to the console. The ROP test will print what is stored in the rsp register. Continuing execution after rsp is pivoted still needs to be done.

fire30 credits the following people, in addition to Liang Chen who revealed the vulnerability in 2014:
thexyz
dreadlyei
If you happen to have a PS4 running a firmware below 2.50, and have the skills to 1) confirm that this is true and 2) try and get the dlclose exploit to run on this, then by all means, help the PS4 scene :)
Otherwise… stay tuned!
source: github, thanks to @isset_asset

Monday, 4 April 2016

Cemu (Wii U emulator for Windows) updated to 1.4.0c, improves speed & graphics

Exzap, the dev behind the wildly popular Wii U emulator Cemu, has recently released an update that brings it up to version 1.4.0c.

Cemu Wii U emulator changes in 1.4.0.c

According to Exzap, this latest version improves the graphics and CPU emulation by a significant amount. The full changelog from the announce:

  • Added PowerPC JIT recompiler (up to 5-6 times faster CPU emulation)
  • Decreased shader compilation stutter
  • Improved audio emulation
  • Large improvements to graphics emulation
  • Tons and tons of smaller changes and bugfixes
Exzap mentions a few known limitations about Cemu 1.4.0:
  • CEMU does not work with AMD’s graphic driver 16.3 and upwards. This issue will likely be fixed in the next CEMU release.
  • Some games don’t boot or randomly crash when recompiler is enabled.
Cemu_1_4_0
Hey, these are pretty ok limitations, knowing that Cemu wasn’t working at all on AMD not so long ago. Great to see steady progress here :)
As with every new Cemu release, users so far are welcoming the new improvements. User SimonBestia on GBATemp says:
Super Mario Maker is running at 56-60fps on my PC!
It ran around 24fps on 1.3.3, now THAT’S a massive speed up!
Several users are reporting twice as much FPS on several games, others are reporting that games are now playable on Cemu with lower end configurations that did not work with former version 1.3.3. Overall, the feeling is that this version dramatically improves performance.

Download Cemu 1.4.0c

Sunday, 3 April 2016

Release: Fully operational dlclose exploit + Linux for PS4, by kR105

The name kR105 might ring a Bell to you because this developer has been credited a lot recently by CTurt on his PS4 hack work. Today, kR105 popped up on our forums to release something that lots of us had been chasing for a while: a fully operational dlclose exploit. He also emailed me to mention he has now integrated support for booting Linux straight from the PS4-Playground tools, and, icing on the cake, also provided the actual PS4 Linux files to use with the tools.
In other words, kR105 is closing the gap here, releasing everything you need to run Linux on your PS4. This is not a drill or a proof of concept video, people. The files are up for anyone to grab. I haven’t tested them myself though, because I’ve still beenhesitating on getting a 1.76 PS4, but I’m regretting not having one every day that goes by. If you’re the lucky owner of a PS4 1.76 though (we have an article here on where you might be able to get one), now’s the right time to test this! Furthermore, there’s absolutely no reason to doubt this release is real, given that it initiates strait from kR105, in CTurt’s github. Also CTurt confirmed this release to me earlier today.

So, what was just released by kR105?

A fully functional dlclose exploit. The exploit had been released about a week ago, and several people had been able to take it further, but there were still issues on how the publicly available code was working, crashing as soon as the exploit was attempting to return to userland. kR105’s release fixes all of that, it includes root, sandbox escape and jailbreak. This exploit is what you’ll want to run your native code on a 1.76 PS4
dlclose PS4 Kernel exploit
The dlclose kernel exploit was released a few days ago
An update to PS4-Playground to run Linux. Another missing link here, that will let people launch linux without having to write their own loader. The launcher integrates the dlclose exploit if I understand correctly. From the Readme:

You need a FAT32 formatted USB drive plugged in on any PS4’s USB port with the following files on the root directory:
bzImage : Kernel image that will be loaded. Recommended to use this sources to compile it.
initramfs.cpio.gz : The initial file system that gets loaded into memory during the Linux startup process. This one is recommended.
The file names must match with the above and you can have more files on the same USB drive. From there you can setup the environment to run from an NFS share or from an external drive via USB (recommended) and boot a complete distro!


linux_loader
A Compiled distro of Linux for the PS4. kR105 has the files bzImage and initramfs.cpio.gz ready for anyone to grab, so you don’t have to compile your own version. In his words: “those files should get you into linux with a nice bash console on your tv”.

Downloads

Update: As pointed out by CTurt, you can simply download the compiled Linux files, put them on a FAT32 USB stick that you’ll connect to your 1.76 PS4, and test directly by going to the PS4 Playground live Demo here.
Wow, now that’s a good start for the weekend!

Monday, 28 March 2016

Is now the right time to buy a 1.76 PS4?

The PS4 scene is boiling right now, with people making daily progress on the dlclose and BadIRET kernel exploits on PS4 1.76. It’s probably going to be a matter of weeks now until people start poking into the Ps4 firmware, or get a full toolkit to install Linux on the device. Is now the right time to get a 1.76 PS4?
If you’ve been on the console scene for a while, you’re probably familiar with the concept of “golden firmware”. The golden firmware is the firmware that gives you the best of what your console can achieve, both from a perspective of official games, and from a hacking point of view. On the PSP, firmware 1.5 was the “golden firmware” for a very long time, as it was the only one with all the cool exploits, piracy, and homebrews. If I recall correctly, the first custom firmwares on the PSP from Dark Alex were basically taking all the cool stuff from firmware 1.5, and merging those on top of the latest firmware, to get the best of both worlds.
Nowadays, with online access being a prerequisite to do anything official on your console, it’s difficult to bypass firmware updates. Most games or applications on your PS4 will probably refuse to run if you’re not running on the latest firmware, and very soon you’d have to say goodbye to the latest games if you decided to stay forever on, say, firmware 1.76.
In that kind of context, I’m convinced people who are interested in the PS4 scene will need basically two consoles: one for hacks that you’d keep on a lower firmware, the other for “regular” gaming, constantly up to date.
dlclose PS4 Kernel exploit
The dlclose kernel exploit was released a few days ago
Now that the scene is just getting ramped up on PS4 exploits with firmware 1.76, it is still possible to find a 1.76 PS4 for a “reasonable” price. We’re all facing a choice at this point: some of us will be buying one now for a reasonable price, in the hope that 1.76 exploits take off soon. Others will just be waiting, hoping that new kernel exploits surface for the latest firmware (3.50?) by the time user-friendly hacks and tools are available.
Our first guy is buying a 1.76 console at a quite expensive price, but still reasonable (you can easily find 1.76 PS4s around $550 today). If hacks on 1.76 become mainstream, prices of 1.76 consoles will skyrocket, and I can easily picture such devices selling for more than $1000 very soon. On the other hand, if an exploit is revealed on the latest firmware, which gives people the same level of tools as 1.76 provides now, our  friend has overpaid about $150 for his second PS4.
My second guy doesn’t want to buy a 1.76 PS4 just yet. If an exploit is revealed for the latest firmware 3.50, he can buy any second-hand PS4 for $300, keep it at 3.50, and be done with it. On the other hand, if 1.76 PS4 hacks become mainstream and no “latest firmware” exploit is revealed for a long time, he’ll be the *** having to buy a 1.76 PS4 for more than $1000.
ps4_jailbreak_1_76_Glacier_white_destiny_bundle

I’m personally on the fence right now. It’s a bet. Statistics tell me there’s always going to be an exploit for the latest firmware at some point, however I can’t help but realize that times have changed: hackers don’t release kernel exploits as often as they used to for, say, the PSP. Maybe what we have on 1.76 right now is a “one time thing”, and we might not see more PS4 kernel exploits for a long time.
Thoughts?