DOL VS WAD explanation:
any IOS can properly install the IOS16 wad, because is is correctly signed.
Take NOTE: WadManager Works THROUGH IOS, so it is limited by
whatever IOS it is pointing at can do.
after installing IOS16 with regular Wad Manager (pointing at IOS35 [no fakesign ability], I believe?)
you can then use the modified wad manager (pointing at IOS16 [with fakesign ability])
to install cIOS_fix [with fakesign ability and more], and then go back to a fully enabled regular wad manager (becuase it defaults to cIOS249, if its there,
and if not ONLY THEN uses IOS35)
the DOL is a CIOS INSTALLER, which....guess what....ALSO uses IOS35 (or similar no fakesign ability IOS) to send its commands (most homebrew does)
the CIOS the DOL is trying to INSTALL is FAKESIGNED.....and it is trying to do this on an IOS (35) that no longer allows it to do so.
the newest cIOS installer is rev6
cIOS_fix is the definitive version of rev5, nothing more, nothing less.
It was chosen for this trick, because simply,
it is the easiest to find cIOS wadfile, because it has been passed around here like crazy. if you missed why it has to be a wad,
re-read everything I've just said. and I'll say it again:
it has to be a wad, because you can only install a wad using either IOS 16 or a cIOS itself using this trick.
if it were a dol, aka: an installer, it would be pointing at
IOS35 or whatever, and would not work.
cIOS was just here and does the job, so we use it. it is really just cIOS249_rev5_definitive edition
someone could easily pack cIOS249_rev6 into a wad, heck I could do it right now, but you don't need me to, so stop asking why.
now, after you've read this post about three times....and you're just joining us,
read this too:
http://gbatemp.net/index.php?showtopic=112...t&p=1504942