Crix0r said:
After using CMDVDX 3.4 to downgrade IOS35, I tried the WMIOS35. I don't get a blank screen, the banner for WM comes up but the systems halts from there.
My guess would be that WMIOS35 is writing to the display before calling IOS_ReloadIOS whereas other WadManagers may not be(?). This would be the same as a blank screen then.
Crix0r said:
I did a hard reboot and tried installing CIOSV9.wad using the WMIOS16. It worked!
I think this just means that WM16 can overwrite an older version IOS with a newer version. I don't think it's related to downgrading IOS35 with the 3.4 DVDX installer.
QUOTE(Crix0r @ Apr 11 2009, 09:33 PM)
Anyone else think this is related to IOS36?
Not really, but I think if we could downgrade all of the "normal" IOS'es then cIOS would function again. But then again that pretty much
is the problem in the first place
I would be interested to know what Comex's 3.4 DVDX installer does to IOS35. In theory, if it were only a true downgrader it would download the older IOS35 files from the NUS servers, pack them into a WAD (properly signed) and install them using the newer exploit (not the fakesigning bug). If that was the case then the ticket for IOS35 would have a valid signature. And in that case, if WMIOS35 is freezing when calling IOS_ReloadIOS(35) then it is not a fake signature that is causing it.
If, however, Comex's downgrader just patches the existing IOS35 (lowering version, adding fakesign bug), packs it into a WAD and fakesigns it before installing it then the ticket for IOS35
would have a faked signature and it
could be the fake signature that is causing it to hang.
I may be way off base on this (above). Does anyone know exactly what Comex's IOS35 downgrader does?