Open GoogleCodeExporter opened 8 years ago
Again, an enhancement.
Original comment by Flamesha...@gmail.com
on 12 Mar 2010 at 1:22
Few things to comment on.
1. This will not protect you from the DOP installer. The way the DOP installer
works
is that if the revision # is > selected revision, it will patch the TMD to 0 so
that
it can install the selected revision. It should however protect you from other
apps
trying to install an IOS if they are not doing the v0 patch.
2. It will not protect from deletion. A title can be deleted then reinstalled.
3. If you do patch to 65535, you may forget what actual version you have
installed
down the road.
4. If the revision is patched for a System Menu IOS and you run the System Menu
installer. The installer will try and get you to reinstall the correct IOS
version to
ensure that the System Menu will boot. If you try canceling this part of the
installation then the System Menu installer will cancel itself.
Original comment by Lunatik.CN@gmail.com
on 12 Mar 2010 at 2:43
Response:
1~2. That's absolutely fine. The idea is to protect from Nintendo updates.
3. Same with installing IOSes to a different slot. You might forget which IOS
you have.
4. That's OK, also. The same will happen if you decide to downgrade that IOS.
Original comment by Flamesha...@gmail.com
on 12 Mar 2010 at 9:56
It was mainly just informational in case any else looks at the ticket ;)
Original comment by Lunatik.CN@gmail.com
on 12 Mar 2010 at 10:17
I don't agree with this enhancement ! Not useful and it coulb be delusive
Original comment by cs-nut...@live.fr
on 17 Mar 2010 at 9:17
It does have a use. If an IOS is revision 65535, Nintendo updates will not
replace
them. This allows you to not have to worry about Nintendo stubbing IOSes or
replacing
them with IOSes that are useless.
Original comment by Flamesha...@gmail.com
on 18 Mar 2010 at 12:21
cIOSes will always have small revision ;) So Nintendo Update will erase it !
Moreover, if you don't want Nintendo updates erase your patched IOSes, Install
them
to another slot which is not Stubbed (ex: IOS36 to slot 236, IOS38 to slot 238
etc...)
I think it's much more cleaner !
Original comment by cs-nut...@live.fr
on 18 Mar 2010 at 8:06
Let's say you want to use apps that are hardcoded to work with one IOS slot,
and that
IOS slot has been stubbed, or is stubbed in the future, or is an actual updated
IOS.
You will lose that IOS when you update unless you version patch it.
Or, if Nintendo decides to stub an open slot, like IOS5 (which I use). I won't
have
to do anything when I update.
Original comment by Flamesha...@gmail.com
on 18 Mar 2010 at 11:30
There is 1 thing that i thought about that may or may not affect the outcome of
patching the revision number. Let's say somehow one of the IOSes got installed
corrupted and you are forced to restore the Wii back to Factory default. If the
revision is patched then the Nintendo updater may or may not reset the IOS back
to
default. If it does not then you will basically have a bricked Wii. Just
something to
take into consideration.
Original comment by Lunatik.CN@gmail.com
on 18 Mar 2010 at 1:48
This could be useful for Korean Wiis that are region changed.
If you install IOS60 v6174 as IOS70 and change the revision to 6687, it will
prevent
official updates from bricking Korean Wiis with error 003.
Without this, you end up with IOS70 v6174, which will be overwritten by a real
IOS70
v6687 during an update.
Original comment by wolst...@gmail.com
on 23 Apr 2010 at 10:57
Original issue reported on code.google.com by
Flamesha...@gmail.com
on 12 Mar 2010 at 1:21