Hacking FINALLY!!! A Fix for The October 23d update!!!

marcan said:
If (say, in 9 months) get to the point where Nintendo fixed all the known holes and we couldn't find new ones over some time, then maybe we'd consider IOS16 as an option.

So you guys were going to re-distribute copyright code ? I thought you preached against all that all the time ?
 
djtaz said:
marcan said:
If (say, in 9 months) get to the point where Nintendo fixed all the known holes and we couldn't find new ones over some time, then maybe we'd consider IOS16 as an option.

So you guys were going to re-distribute copyright code ? I thought you preached against all that all the time ?
I think this is about how it would go: Here's all the software you need. You can dump the wad from the pink fish disk yourself.

As marcan said, this is the last resort because it involves copywriten code. They will do everything else before they do this.
 
midna25 said:
I think this is about how it would go: Here's all the software you need. You can dump the wad from the pink fish disk yourself.

As marcan said, this is the last resort because it involves copywriten code. They will do everything else before they do this.

Ohh so he is only pissed that someone else discovered the same exploit and let people know about it in the same way as he would have done ... but they did it now instead of in the future ?

You'd swear it was his right to release the exploit and anyone else doing so was in the wrong becase he owned it.
 
Everybody here is uninstalling the ios16?

Wouldn't it better?Because if nobody has this bug on wii, Nintendo will never know about this bug...
 
HEY EVERYONE I GOT IT FIGURED OUT! ok for those of you who were having problems with the ios downgrader1.0, goto waninkokos website and download the CIOS downgrade 1.2 it will allow you to select what version of firmware you want to run on your wii, so 3.3 to 3.2, make sure if your 3.3u to downgrade to 3.2u now p or j your wii will be screwed. good luck
 
midna25 said:
marcan said:
noobwarrior7 said:
you think IOS16 was the big bug/last resort they mentioned? I kinda doubt it, because it relies on distributing copyright nintendo code, which they never do...and also, it won't be a viable option for a lot of people.
You do not seem to understand the phrase "last resort".

If (say, in 9 months) get to the point where Nintendo fixed all the known holes and we couldn't find new ones over some time, then maybe we'd consider IOS16 as an option.

Now, if that happens, I guess we'll just take a nice long vacation from looking for holes.

Sure, we have more exploits, but they won't last forever. We have big bugs. The last resort (IOS16) wasn't one of them. It was a (shitty) last resort. Which you've just killed.

This crap makes me want to release BootMii in such a way that somehow, someway, it's useless for the WAD crap (don't think for a second that I wouldn't if it were obvious, it's just that it isn't). Then you guys can have fun finding the real exploits once this one's closed.
Calm down, Marcan. Sure, he's killed a small exploit and opened the gate again for wads again, but it's not all that bad. By the way, Can't wait for bootmii
bow.gif

who's he? Syndicate released the fish disc. Davi92 only made a wad-manager to work with IOS16:
http://gbatemp.net/index.php?showtopic=112...t&p=1500344

it was said waninkoko was going to release some huge last resort, but he was against this release.
 
noobwarrior7 said:
midna25 said:
marcan said:
noobwarrior7 said:
you think IOS16 was the big bug/last resort they mentioned? I kinda doubt it, because it relies on distributing copyright nintendo code, which they never do...and also, it won't be a viable option for a lot of people.
You do not seem to understand the phrase "last resort".

If (say, in 9 months) get to the point where Nintendo fixed all the known holes and we couldn't find new ones over some time, then maybe we'd consider IOS16 as an option.

Now, if that happens, I guess we'll just take a nice long vacation from looking for holes.

Sure, we have more exploits, but they won't last forever. We have big bugs. The last resort (IOS16) wasn't one of them. It was a (shitty) last resort. Which you've just killed.

This crap makes me want to release BootMii in such a way that somehow, someway, it's useless for the WAD crap (don't think for a second that I wouldn't if it were obvious, it's just that it isn't). Then you guys can have fun finding the real exploits once this one's closed.
Calm down, Marcan. Sure, he's killed a small exploit and opened the gate again for wads again, but it's not all that bad. By the way, Can't wait for bootmii
bow.gif

who's he? Syndicate released the fish disc. Davi92 only made a wad-manager to work with IOS16:
http://gbatemp.net/index.php?showtopic=112...t&p=1500344

it was said waninkoko was going to release some huge last resort, but he was against this release.
Oh, you know. They generic He and they that everyone talks about. They released something new etc...
 
if it's a shite "last resort", which it definitely is, because even I had thought about it half-asleep, 36 hours ago, just randomly daydreaming, then why does it matter if people use it now to downgrade? If people have a right to do what they want with their consoles as far as code goes, they have a right to downgrade if they want. And, if we're talking about patience and selfishness...well yes, I could have waited until after launch date to get my two wiis, but I'm impatient, and instead of buying two wiis and forty games over the past yearish, I could have given money to homeless urchins, so I guess I'm selfish. who's in that boat with me?

I'm not gonna come crying to marcan or bushing or anyone to fix my wii, and I like the work they do a lot. Anyone who expects someone else to be their wii saviors, they are the selfish ones. I'm just helping people who don't want to banner brick....end story.


How's that you say?

Because a bad banner, installed on any 3.3 without the twilight hack, equals a full brick. If you are on 3.3 NOW, and can't downgrade NOW, then that becomes your problem NOW. with this you can take steps to fully downgrade to 3.2 (although not the nice easy old steps) and have a no-cost banner-brick-proofing, as I've discussed elsewhere.
 
I install the ios16 whith the wadmanager 1.3 and then replace the boot.dol for the boot .doll from the wadmanagerios16 but i cannot install the ciosinstaller from backuplauncher 0.3 and a i try to install the cIOS36_rev6 but the same error ocurred, what can i do? (i am in the update 3.2)

i think i am missing the last step

*Finally, use Wad Manager that was recoded to work off of IOS16 to install the cIOS fix, and you are on your way again!

but i don't know what iosfix are you talking =(
 
noobwarrior7 said:
if it's a shite "last resort", which it definitely is, because even I had thought about it half-asleep, 36 hours ago, just randomly daydreaming, then why does it matter if people use it now to downgrade? If people have a right to do what they want with their consoles as far as code goes, they have a right to downgrade if they want. And, if we're talking about patience and selfishness...well yes, I could have waited until after launch date to get my two wiis, but I'm impatient, and instead of buying two wiis and forty games over the past yearish, I could have given money to homeless urchins, so I guess I'm selfish. who's in that boat with me?

I'm not gonna come crying to marcan or bushing or anyone to fix my wii, and I like the work they do a lot. Anyone who expects someone else to be their wii saviors, they are the selfish ones. I'm just helping people who don't want to banner brick....end story.


How's that you say?

Because a bad banner, installed on any 3.3 without the twilight hack, equals a full brick. If you are on 3.3 NOW, and can't downgrade NOW, then that becomes your problem NOW. with this you can take steps to fully downgrade to 3.2 (although not the nice easy old steps) and have a no-cost banner-brick-proofing, as I've discussed elsewhere.
Another good point. This allows someone to recover from future bricks.
 
vic1337 said:
I install the ios16 whith the wadmanager 1.3 and then replace the boot.dol for the boot .doll from the wadmanagerios16 but i cannot install the ciosinstaller from backuplauncher 0.3 and a i try to install the cIOS36_rev6 but the same error ocurred, what can i do? (i am in the update 3.2)

i think i am missing the last step

*Finally, use Wad Manager that was recoded to work off of IOS16 to install the cIOS fix, and you are on your way again!

but i don't know what iosfix are you talking =(


Cios_fix.wad .. its in the wad folder in the zip file in my signature
 
djtaz said:
So you guys were going to re-distribute copyright code ? I thought you preached against all that all the time ?
No, we'd try to find a solution. Like, for example, developing a tool to install IOS16 as based from another IOS, reconstructing the original without distributing most of it - maybe even a few kB at most.

Of course, I don't expect anyone in this thread to care about legality to even think about something like that, much less actually do it. After all, this is WAD-land we're talking about. FFS, the entire site is based around a warez database.

djtaz said:
Ohh so he is only pissed that someone else discovered the same exploit
What exploit? This is no exploit. It's a stupid omission by nintendo. Anyone can come up with it. It's a shame that PFD got leaked right now, but the damage wouldn't have been done if people who came up with the idea didn't immediately start using it for WAD piracy. What a great way of getting Nintendo's attention.

QUOTE(noobwarrior7 @ Oct 29 2008, 02:52 AM)
Because a bad banner, installed on any 3.3 without the twilight hack, equals a full brick. If you are on 3.3 NOW, and can't downgrade NOW, then that becomes your problem NOW. with this you can take steps to fully downgrade to 3.2 (although not the nice easy old steps) and have a no-cost banner-brick-proofing, as I've discussed elsewhere.
If you have a bad banner NOW, and you installed it NOW, without having a recovery solution NOW, after being told dozens of times about the danger, then as far as I'm concerned you're an idiot and should just sit and cry and either buy a new wii or wait for a hardware BootMii solution and flash it using an infectus.
 
Ugh, I feel like a complete moron by not being able to figure out the link for the cough cough file.

I need sleep.
 
djtaz said:
vic1337 said:
I install the ios16 whith the wadmanager 1.3 and then replace the boot.dol for the boot .doll from the wadmanagerios16 but i cannot install the ciosinstaller from backuplauncher 0.3 and a i try to install the cIOS36_rev6 but the same error ocurred, what can i do? (i am in the update 3.2)

i think i am missing the last step

*Finally, use Wad Manager that was recoded to work off of IOS16 to install the cIOS fix, and you are on your way again!

but i don't know what iosfix are you talking =(


Cios_fix.wad .. its in the wad folder in the zip file in my signature

now i find it in your folder [cios_fix.wad] so after installing the ios16.wad whith the wadmanager 1.3 and then replace the boot.dol for the boot .doll from the wadmanagerios16 i need to install that iosfixed.wad too?
 
Are these the correct steps

1) put wadmanager 1.3 in apps

2) put IOS16-64-v257-prod.wad in the folder .WAD

3) run wadmanager 1.3 and install the ios16.wad

4) take the boot.dol from wadmanagerios16 and replace it in the boot.doll from wadmanager 1.3

5) install de iosfix.wad (only step i think i am missing)


is this rigth?
 
Man, I made a mistake with an underscore. Every time.

I feel like a grade A idiot.

Anyways, I have everything up, but when I try to install the WAD I hit a error (ret = -1022). I'm using 1.3. What's causing this?

EDIT: Turns out it was because my stupid SD card was formatted to FAT, not FAT32.
 

Site & Scene News

Popular threads in this forum