Why is using the SDK frowned upon? Is it a moral thing? Like you want to reverse engineer things on your own? Or is it a legal thing? Just curious.There are a few examples in the SDK if you want to cheat.
Kinda both, we're too good to use the SDK, we'll do it on our own just like everything else we've doneWhy is using the SDK frowned upon? Is it a moral thing? Like you want to reverse engineer things on your own? Or is it a legal thing? Just curious.
Yeah I hear the SDK is for nerds anywaysKinda both, we're too good to use the SDK, we'll do it on our own just like everything else we've done
Why is using the SDK frowned upon? Is it a moral thing? Like you want to reverse engineer things on your own? Or is it a legal thing? Just curious.
Kinda both, we're too good to use the SDK, we'll do it on our own just like everything else we've done
Yeah but i doubt there'd be any legal issues if you just looked at it to ascertain how to reverse something. It would be extremely hard to prove that someone used the SDK as reference material.It largely has to do with it being copyrighted material and against the terms of use for it to have been leaked in the first place.
Hi all. I am back for an update and found some interesting things . I just want to say thanks for everyones work. I still don't understand what the hell has been done or not done but I see people excited so maybe that means something.
Anyways, I just wanted to ask. I noticed someone talking about downgrading and backing up or something. Did someone try that? If not, maybe explain 1 more time what needs to be done and I will try it. I don't care about the Wii if it bricks. I just want to contribute as much as I can since I don't know anything about code... but I can follow a tutorial and maybe help out that way?
Let me know if I can be of use since again I don't care what happens to the Wii U. I just want to see if we can get this released ASAP
PS. I offer this only if its like a needed thing from developers. I don't want to brick my Wii U, but I what I mean is that I want to help develop this ASAP and if this is a step I would like to help.
This is pointless to try since devkits have their own set of keys, though there is no risk since it will only installed correctly signed and encrypted content.
Anyone care to give a lesson on how to analyze a file to determine what encryption method has been used on it?
And don't conflate the dump.img (Win32imager) you can make with the recovery.img from the DevKit, definitely 2 different animals.
You could probably write a true disk image (via hardware) a lot easier than using the POWER + EJECT + IMG on SD. And poking around there are already some tools for easily flashing the unit, I might try to see if they will work
with a simple FTDI board instead of the card reader.
***I found this, but I know squat about Python. It is supposed to be able to identify how something is encrypted -- if I understand correctly. What is the best Python Environment to run on Win 7 64bit so I can run this script?
http://www.mediafire.com/view/i3iob9aoa37j5t6/Hash_ID_v1.1.py
from here:
https://code.google.com/p/hash-identifier/
Unless you are talking about hashes (one-way encryption), no. That program will only recognize hashed stuff, which is (I guess) pointless as it is not decryptable anyway.
That seems to analyze unencrypted firmware images, something you won't find on a console.https://github.com/devttys0/binwalk <------------- am I getting warmer..?
I am working on a PDF that will have instructions, if you really want to try it. But first:
Do you have a tri-wing screwdriver to open the Wii U?
How is your solder work? (Rat shack iron or fancy MetCal?)
Do you have a SD card reader to sacrifice?
20AWG(+) wire?
Even if people don't want to try to downgrade, at least you can dump your unit, and preserve the 5.3.2. FW, one that came from your specific unit. I don't know that it matters, but I would only think it would remove any compatibility issues in returning (re-flashing) it to the console.
ehhh. The SDK is a great tool, especially if you are going to want to write homebrew. But again it should just be another tool in your arsenal. Information is your only true weapon.
I am working on a PDF that will have instructions, if you really want to try it. But first:
Do you have a tri-wing screwdriver to open the Wii U?
How is your solder work? (Rat shack iron or fancy MetCal?)
Do you have a SD card reader to sacrifice?
20AWG(+) wire?
Even if people don't want to try to downgrade, at least you can dump your unit, and preserve the 5.3.2. FW, one that came from your specific unit. I don't know that it matters, but I would only think it would remove any compatibility issues in returning (re-flashing) it to the console.
ehhh. The SDK is a great tool, especially if you are going to want to write homebrew. But again it should just be another tool in your arsenal. Information is your only true weapon.