Talk:DOP-Mii/Archive 1

From WiiBrew
Jump to navigation Jump to search

Suggestions

- Copy the code from some other project that allows to select which IOS to use. The projects i'm thinking of can't be linked here, but parts of their code can be quite useful for various projects. --WiiPower 14:27, 18 August 2009 (UTC)

I know what you mean. Eventually I'd like to incorporate sanity checks on the level of IOS selection, however, I'd prefer to write it on my own.--Arikado 16:29, 18 August 2009 (UTC)
I don't mean sanity checks, i mean just getting the list of the actually installed IOS and select from them. --WiiPower 16:45, 18 August 2009 (UTC)
Right. What I was talking about was performing sanity checks on the IOS list so that IOSs that could not accept fakesigning would be filtered out of the list. Also, thanks to your suggestion, I have that working now (except for the filtering at time of writing - but it should be working soon)--Arikado 18:57, 25 August 2009 (UTC)
How do you want to filter the IOS with the bug? I could only look at the revisions of the IOS and know by that which IOS have the bug. You can gather more info, like if the IOS fakesigned by grabbing the tmd and/or ticket(-->most likely patched for trucha bug), but that does not work on all IOS, i mean not all IOS used as firmware will provide that info. You can load all IOS to gather info about them, but that would be dirty, and the program won't work when there's 1 broken IOS. I'm looking forward to your next release, maybe you find something that i would not think about. Oh, and you can do an IOS Reload directly after getting -1017 or -2011, so you could just run with IOS36, and then just try all existing IOS until one has the bug. --WiiPower 19:16, 25 August 2009 (UTC)

- Do not use ES functions to decrpyt with the common key. ES_Decrypt(ES_KEY_COMMON[...] will fail on the not module based IOS like IOS15. The decryption is "just" AES with the common key. (you will get -1017 even with IOS15v257) Oh and there's already some project with the code for that too. --WiiPower 14:27, 18 August 2009 (UTC)

That's stuff in the original Dop-IOS you're talking about. I'd eventually like to go through and totally revamp the entire project to include features like what you're talking about.--Arikado 16:29, 18 August 2009 (UTC)
It's stuff from PatchMii. I don't like the way stuff is done in PatchMii anyways. Don't get me wrong there are plenty of useful functions in PatchMii and i use many of them, but it does stuff in a (to me) strange way: There's a loop where the contents of the IOS are processed, and each one is downloaded, decrpyted, patched, encrypted and temporarily stored on nand. And on the installation after this, the contents are loaded from nand again. I prefer it to get the IOS, decrypt it as a whole, patch it, encrypt it again, and then just install it. Adding alternative ways to get the IOS contents is a little complicated on original PatchMii code. --WiiPower 16:45, 18 August 2009 (UTC)

- Take a look at WiiSCU; I would love if the core functionalities of both Dop-IOS and WiiSCU were conjoined. Nago 00:27, 16 September 2009 (UTC)

So would I--Arikado 20:13, 26 September 2009 (UTC)
And a bit more beside - installing new System Menus perhaps? It'd just have to check you have the System Mneu IOS, then install the actual System Menu, so you could update without losing trucha. Then you wouldn't need the official System Menu update. And you'd be able to install different regions so it could help in a semi-brick. Any chance of this happening Arikado? --SifJar 14:06, 27 September 2009 (UTC)
The IOS sanity check would be hard to implement. Since some people may have trucha in it, that may return a "failed check" when in reality it would work. It would be better to leave that check up to the user and/or give the user the option to install a clean version of the required IOS before installing the system menu. And yes, this will happen if I can get people willing to test it. Honestly, it's the next logical step in the application's development. Also, just so you know, I plan to redo the GUI if/when I choose to implement this.--Arikado 15:00, 27 September 2009 (UTC)


-I would also be interested in an "update all" function which would do something akin to: 1) Gather information: Ask the user if they'd like to apply the signing patch. Also ask the user if they want to update "critical" IOSes (IOS60, etc), giving them the ability to forego a more 'dangerous' upgrade. 2) For non-stub IOSes, if the newest version is newer than the installed version, download and install. Nago 00:27, 16 September 2009 (UTC)

Ditto, again, I would be interested in seeing this happen too.--Arikado 20:13, 26 September 2009 (UTC)