Well we know you are a douche who likes to make up stuff just to tear down the accomplishments of others, so I'm going to say tueidj.hanibel said:I would've toBladexdsl said:so whats your REAL account in here?hanibel said:
you and gbatemp if I tell.
Nobody should ever update to 4.3, but you might consider updating to 4.1 for the bug fix.BortzANATOR said:
JoostinOnline said:
Yeah, I made a fake account to attack the people who created this exploit... which includes myself.JoostinOnline said:Well we know you are a douche who likes to make up stuff just to tear down the accomplishments of others, so I'm going to say tueidj.
He's not the guy with the most tact, but he's more respectable than that.JoostinOnline said:Well we know you are a douche who likes to make up stuff just to tear down the accomplishments of others, so I'm going to say tueidj.
4.1 was the last update to receive anything beneficial. 4.2+ were released to brick region changed Korean Wii's and block multiple types of homebrew.kevan said:
I was talking about the System Menu itself, which offers no benefits. You can get everything you need on 4.1.tueidj said:
Updating to 4.1 and upgrading the IOSes individually (or worse, downgrading the system menu) is not simpler/safer than just updating straight to 4.3. There is also no longer any advantage to using sysmenu 4.1 over sysmenu 4.3, unless you actually enjoy installing extra shit like priiloader (which has many reported cases of bricking wiis while installing/contains stolen code) to stop games nagging you to update.JoostinOnline said:
(Note his cute hidden message in 00000000.app which he used to overwrite the original contents (removing marcan's name in the process) after I called attention to what he was doing. Note also that if he had any clue about how things work, he'd realize 00000000.app isn't functionally required and only existed in DVDX to show who the original creator was.)QUOTE said:
tueidj said:
Not really. The title with the magic TMD bits has to be launched for them to do their magic (with ES_LaunchTitle or whatever) so the DVDX "channel" (00000001.app) has to do some tricks to give execution control back to the program that launched it. In the old days when ES_Identify was usable, it would have been enough to call it using a fakesigned TMD with the AHBPROT bit set.cwstjdenobs said:I wasn't suggesting otherwise. It was a genuine question, I wasn't trying to set you up or anything, I just thought maybe you couldn't be arsed explaining it to someone who can't be arsed looking for themselves.I know, I just threw that in there for Joostin.
QUOTECouldn't he have also patched the ticket, or rather simply made his own, to keep ahbprot rights too? I mean that's all DVDX was right, an empty channel with the right flags set in the ticket?
@
Xdqwerty:
@
K3Nv2:
@
K3Nv2:
