Hacking Wii U Hacking & Homebrew Discussion

[Marionumber1]

Add/replace this code to make it work on 5.3.2:

asm(
"lis %r1, 0x1220 ;"
"ori %r1, %r1, 0xc250 ;"
);

Which file are you suggesting to add this to, and why? I can incorporate this back into libwiiu if it helps people.

 

[Adeka]

So far, I haven't really received a definitive answer. Did you accidentally update?

I updated because I wanted the dlc for smash

 

[crediar]

Which file are you suggesting to add this to, and why? I can incorporate this back into libwiiu if it helps people.

You mentioned that function calls crash, this means there is a problem with the stack.
Some examples have this code:

/* Load a good stack */
asm(
"lis %r1, 0x1ab5 ;"
"ori %r1, %r1, 0xd138 ;"
);

Replace that or add it after _start.

 

[Adr990]

Which file are you suggesting to add this to, and why? I can incorporate this back into libwiiu if it helps people.

I believed the "findcode532.c" file under the framework/src.

Am I correct in assuming that this PPC ASM does either add 0x1220 or(i) add 0xc250 to r1 (stack)?

 

[JaceCearK1]

Updated http://wiiulib.arndroid.nl/ with Crediar's fix.

I cannot test it myself yet, so... yeah.

Code execution still works, but also still crashes! :/

 

[the_randomizer]

I updated because I wanted the dlc for smash

Oh right...well, so far I haven't gotten a definitive answer at all.

@Marionumber1 are those on 5.4.0 shit outta luck?

 

[NWPlayer123]

So in "findcode532.c", I should replace this:

asm("stwu %r1,-0x2000(%r1)");

With yours? I'm gonna try that now, and upload it back to wiiulib.arndroid.nl.

Not findcode, in the loader.c file you're trying to compile. Basically it's loading a clean stack to use.

 

[Marionumber1]

You mentioned that function calls crash, this means there is a problem with the stack.
Some examples have this code:

/* Load a good stack */
asm(
"lis %r1, 0x1ab5 ;"
"ori %r1, %r1, 0xd138 ;"
);

Replace that or add it after _start.

Unfortunately, that still doesn't fix the problems I've mentioned. Where exactly did you get 0x1220c250 anyway?

I believed the "findcode532.c" file under the framework/src.

Am I correct in assuming that this PPC ASM does either add 0x1220 or(i) add 0xc250 to r1 (stack)?

It loads 0x1220, shifted 16-bits left, into r1 (lis stands for load-immediate shifted), so it loads 0x12200000. Then it does a bitwise-OR with 0xc250, meaning r1 becomes 0x1220c250 (ori stands for OR-with-immediate).

 

[JaceCearK1]

Not findcode, in the loader.c file you're trying to compile. Basically it's loading a clean stack to use.

I put it before the OSFatal function-call.
Since it's stack-access, maybe it should be after the function!?

 

[the_randomizer]

So no one, and I mean no one has any information on all regarding the safety of 5.4.0.?

 

[Marionumber1]

I put it before the OSFatal function-call.
Since it's stack-access, maybe it should be after the function!?

Well, OSFatal() needs the stack to run, so it would be before. Anyway, when you say code execution works, are you saying OSFatal() does or doesn't print something?

 

[the_randomizer]

Well, OSFatal() needs the stack to run, so it would be before. Anyway, when you say code execution works, are you saying OSFatal() does or doesn't print something?

Never mind, it's been answered.

 

[Marionumber1]

So no one, and I mean no one has any information on all regarding the safety of 5.4.0.? Freaking really? I would've thought those who programmed the exploit would know more about that. Wow, that really is reassuring. No really.

Calm down, we're getting a lot of questions and there's no reason yours takes priority. We have some bugs that seem viable, but 5.4.0 isn't our focus while we finish 5.3.2.

 

[JaceCearK1]

Well, OSFatal() needs the stack to run, so it would be before. Anyway, when you say code execution works, are you saying OSFatal() does or doesn't print something?

It prints the text, but the console doesn't recognise any buttons presses what-so-ever! :/

 

[A Plus Ric]

You don't pay much attention ever to things, just gimme gimme gimme. They are probably all right now polishing and fixing any bugs they can in the 5.3.2 right now. I am sure at some point they will look into and get back on 5.4.0. No answer probably means they aren't sure yet.

 

[Marionumber1]

It prints the text, but the console doesn't recognise any buttons presses what-so-ever! :/

That's exactly what OSFatal() is supposed to do, meaning it worked perfectly.

 

[the_randomizer]

Calm down, we're getting a lot of questions and there's no reason yours takes priority. We have some bugs that seem viable, but 5.4.0 isn't our focus while we finish 5.3.2.

I'm not the one asking, @Adeka was the one that asked, and I was merely trying to get someone to answer his question, that's all.

 

[NWPlayer123]

See? If I quote someone to ask about 5.4.0 and if it's safe, it will be brushed aside. That's very consoling.

http://gbatemp.net/threads/wii-u-hacking-homebrew-discussion.367489/page-337#post-5536677
I've already answered this question multiple times.

 

[the_randomizer]

http://gbatemp.net/threads/wii-u-hacking-homebrew-discussion.367489/page-337#post-5536677
I've already answered this question multiple times.

On the previous page, Adeka asked the question.

 

[Demifiend]

Calm down, we're getting a lot of questions and there's no reason yours takes priority. We have some bugs that seem viable, but 5.4.0 isn't our focus while we finish 5.3.2.

Please tell me, it's your program made to create homebrews on the Wii U?, because i don't understand how this works.