Hacking [Tutorial] Offline Downgrading

  • Thread starter Thread starter Cermage
  • Start date Start date
  • Views Views 31,223
  • Replies Replies 104

Cermage

Well-Known Member
Member
Joined
Dec 2, 2007
Messages
1,701
Reaction score
0
Trophies
1
Website
Visit site
XP
285
Country
as i have a service where i install backup launcher on peoples wii's, i've been looking for a way to downgrade them from 3.3 and 3.4 for a fair while now and i've found it =). this tutorial assumes you know how to get all the apps and required files, also assumes you know how to operate everything related to homebrew.

*disclaimer*
i will not be held responsible if you do end up bricking your wii following this guide, i have done it plenty of times and each time it has worked without problem.



1. Install Homebrew Channel with twilight hack or use the disc if you have a chip.
2. Load up WAD manager and install IOS16-64-v257-prod.wad, with a little googling you should be able to find this.
3. Load up Custom Wad Manager and install cIOS_fix.wad
4. Load up Wad manager again ( there is a difference between custom WM and WM) and install these in order

Code:
IOS17-64-v512.wad
IOS20-64-v12.wad
IOS21-64-v514.wad
IOS31-64-v1040.wad
IOS33-64-v1040.wad
IOS34-64-v1039.wad
IOS35-64-v1040.wad
IOS36-64-v1042.wad

These IOS files can be a bit tricky to find, so find a game with the 3.2 update (i know bloom blox has it, just make sure its the right one for your region) and extract them using wiiscrubber or something similar.

5. While still in Wad Manager install these files in the following order

Code:
IOS30-64-v1040.wad
SystemMenu-v290.wad ( for PAL) 
SystemMenu-v289.wad (for NTSC)

IMPORTANT: YOU MUST INSTALL IN THIS ORDER, IF YOU DO NOT IT WILL BRICK YOUR WII
once again, i will not be held responsible if you do end up bricking your wii.

these files can also be a little tricky to find. go look for bushings semi-brick fix discs, look for one that corresponds to your region (NTSC for US, PAL for Europe, UK, australia and surrounding regions, NTSC-J for Japan)and extract them using wii scrubber.

Congratulations! you are now on 3.2! and you can install what you like.

Thanks goes to;
Emperor of Canada for his/her tutorial - it helped me plenty of times when i forgot the process of installation, also the modeling of this tutorial goes after his/her tutorial.
Waninkoko - wad manager, the downgraders and cios of course! and more thanks goes to you for showing the files that the IOS downgrader downloads when it downloads them.
Bushing - the semi brick fix discs, the last and vital part of the downgrading part.
 
Awesome, thanks!

Is it possible to use a multi ios installer to install 17 through to system menu?

(That would be awesome: fewer steps meaning virtually automated downgrade)
 
Don Killah said:
mishra said:
Code:
IOS30-64-v1040.wad
SystemMenu-v290.wad
Shouldn't it be SystemMenu-v289.wad for NTSC System as 290 is for PAL ones ?
eh lemme fix that
tongue.gif
i forgot that the NTSC one is different.
 
People who don't know what they are talking about should not write guides!

Little details:
At least IOS9 and IOS28 are missing and cios_fix isn't the cIOS of choice. Why does everybody use cios_fix to downgrade and then install the real cIOS, which could be used for the downgrade too?

Dangerous "detail": SystemMenu-v290.wad is the system menu for ONE region, and NOBODY should recommend to install the wrong one, but this guide does it for 50% of people.
 
WiiPower said:
People who don't know what they are talking about should not write guides!

Little details:
At least IOS9 and IOS28 are missing and cios_fix isn't the cIOS of choice. Why does everybody use cios_fix to downgrade and then install the real cIOS, which could be used for the downgrade too?

Dangerous "detail": SystemMenu-v290.wad is the system menu for ONE region, and NOBODY should recommend to install the wrong one, but this guide does it for 50% of people.

Thanks for that!
 
Sorry for the rant, but even with disclaimer you should know what you are doing when you write a guide about something that can brick Wiis. You should add some information about what IOS16 is and why you install it, and what's the difference between the custom WAD Manager and the normal one. And add the missing IOS, at least IOS9 and IOS28 are missing. And if you skip cios_fix.wad and use Waninkoko's cIOS36rev7 directly this guide will save A LOT OF TIME for a lot of people, for the people following this guide and for the people cleaning up after the noobs followed this guide. And if you add how to test if the installation of the IOS was done right, this guide could become the standard downgrade guide.
 
WiiPower said:
Sorry for the rant, but even with disclaimer you should know what you are doing when you write a guide about something that can brick Wiis. You should add some information about what IOS16 is and why you install it, and what's the difference between the custom WAD Manager and the normal one. And add the missing IOS, at least IOS9 and IOS28 are missing. And if you skip cios_fix.wad and use Waninkoko's cIOS36rev7 directly this guide will save A LOT OF TIME for a lot of people, for the people following this guide and for the people cleaning up after the noobs followed this guide. And if you add how to test if the installation of the IOS was done right, this guide could become the standard downgrade guide.
I do agree with WiiPower , this guide needs some cleaning and more detailing to avoid bricks and dealing with angry noobs crying
wink.gif
but it is a good attempt
wink.gif
 
And it it would use Waninkoko's cIOS36rev7 directly, the plague that people are using cios_fix and complain about not working backup launchers will hopefully stop.
 
WiiPower said:
And it it would use Waninkoko's cIOS36rev7 directly, the plague that people are using cios_fix and complain about not working backup launchers will hopefully stop.

Can you please explain what you mean? Should we install cIOS36rev7 instead of cios_fix.wad and then continue on to run IOS downgrader and then cIOS downgrader?
 
So on 3.4 after HBC etc:

Run wad man 1.3 and install:

1a - IOS16-64-v257-prod.wad

Run custom wad man and install:

1b - cIOS249-v7.wad

Run wan man 1.3 again and install (in this order):

1c - IOS9-64-v516.wad
1d - IOS17-64-v512.wad
1e - IOS20-64-v12.wad
1f - IOS21-64-v514.wad
1g - IOS28-64-v1288.wad
1h - IOS31-64-v1040.wad
1i - IOS33-64-v1040.wad
1j - IOS34-64-v1039.wad
1k - IOS35-64-v1040.wad
1l - IOS36-64-v1042.wad

2a - IOS30-64-v1040.wad
2b - SystemMenu-v290.wad (FOR PAL ONLY)

--=or=--

2b - SystemMenu-v289.wad (FOR NTSC ONLY)

Correct?
 
Basically yes, but with explanations.

bowser said:
WiiPower said:
And it it would use Waninkoko's cIOS36rev7 directly, the plague that people are using cios_fix and complain about not working backup launchers will hopefully stop.

Can you please explain what you mean? Should we install cIOS36rev7 instead of cios_fix.wad and then continue on to run IOS downgrader and then cIOS downgrader?

Why do you think cios_fix is used in the guides?
 
KiiWii said:
So on 3.4 after HBC etc:

Run wad man 1.3 and install:

1a - IOS16-64-v257-prod.wad

Run custom wad man and install:

1b - cIOS249-v7.wad

Run wan man 1.3 again and install (in this order):

1c - IOS9-64-v516.wad
1d - IOS17-64-v512.wad
1e - IOS20-64-v12.wad
1f - IOS21-64-v514.wad
1g - IOS28-64-v1288.wad
1h - IOS31-64-v1040.wad
1i - IOS33-64-v1040.wad
1j - IOS34-64-v1039.wad
1k - IOS35-64-v1040.wad
1l - IOS36-64-v1042.wad

2a - IOS30-64-v1040.wad
2b - SystemMenu-v290.wad (FOR PAL ONLY)

--=or=--

2b - SystemMenu-v289.wad (FOR NTSC ONLY)

Correct?
--=or=--

2b - SystemMenu-v288.wad (FOR JAP ONLY)

So that people with Jap Wiis (like me) don't feel left out
smile.gif
 

Site & Scene News

Popular threads in this forum