SifJar said:NutNut said:It still a point I can't understand well !(not a noob)
Now, there is the AHBPROT so even if the "downgrade bug" is fixed we don't need it anymore 'cause we don't need to downgrade IOS15 anymore.
When we patch IOS36, there is the "version check patch" which allow the patched IOS to downgrade a high revision IOS. (for exemple, this patch allow us to install cIOS in a stubbed slot without deleting the stub before)
So if TBR use IOS36 v3608 instead of v3351 it will be exactly the same, isn't it ?
I tested something, I changed the sources from TBR to install IOS36 in slot 236 with revision 65535 (based on IOS36 v3608) then I decide to use the real TBR to replace this IOS236 v65535 by IOS236 v1 and during the install it tell me error -1035 !
The question is, Why can't I downgrade ?
Normally, the AHBPROT + IOS58 can downgrade anything so why this error ?
or Maybe it use the IOS I want install (IOS36 v3608) to try to downgrade the IOS236 v65535, I don't know but :
The IOS is patched with "version check" before installation but the patch is not yet active if the IOS is not installed ?
Can you explain me more please SifJar !
The application has to be programmed specifically to make use of IOS58 and AHBPROT. All AHBPROT does is allow full access to hardware. Its up to the app to use that access to patch the currently running IOS e.g. to allow it to downgrade. Simply booting an app with the HW_AHBPORT flags set won't make the app behave any differently to usual unless it is programmed specifically to use the HW_AHBPROT flags. I hope you understand, if not, I'll try to explain more clearly
here's a smart thought : update at least to 4.0 and don't be a retardOrel said:Here's a crazy thought.. Don't udpate? I'm still on 3.4 and everything works fine
But yea the topic is nescesary to just know about it XP
Last time I looked, you'll need to use NUSD.Cuber said:Is there a new shop updater yet? >.>; Will there be... or am I going to have to use NUS..
No, I have moded IOS236 Installer adding a bit of code from Dop-Mii. and IOS236 Installer is based on TBR.SifJar said:I though you were talking about using TBR? I'm confused what you mean =/
Why? Of course I could, but why? Everything works perfectlylulwut said:here's a smart thought : update at least to 4.0 and don't be a retardOrel said:Here's a crazy thought.. Don't udpate? I'm still on 3.4 and everything works fine
But yea the topic is nescesary to just know about it XP
and everything will still work perfectly in 4.0 AND you'll have SD accessOrel said:Why? Of course I could, but why? Everything works perfectlylulwut said:here's a smart thought : update at least to 4.0 and don't be a retardOrel said:Here's a crazy thought.. Don't udpate? I'm still on 3.4 and everything works fine
But yea the topic is nescesary to just know about it XP
Kryptical said:I'm on 4.2U and updating seems pointless to me... So right now the only thing you need to update your shop channel is Shop Channel V20 with IOS56 V5662? Will it work with V5661?
Kryptical said:I'm on 4.2U and updating seems pointless to me... So right now the only thing you need to update your shop channel is Shop Channel V20 with IOS56 V5662? Will it work with V5661?
Riley said:ok I installed shopping channel v20 and it does infact need the latest ios56...Kryptical said:I'm on 4.2U and updating seems pointless to me... So right now the only thing you need to update your shop channel is Shop Channel V20 with IOS56 V5662? Will it work with V5661?
It works with v5661.
Well, I guess he can try it out with v5661 first. But from what I read... well, here's the quotes:
Yuan said:Download and install IOS56 v5662 (lastest version @ NUSD) too. Or Wii Shop Channel will boot to a #002 error.
QUOTE(Richardarkless @ Sep 8 2010, 07:43 AM)
synce said:Hmm so there are softmodders who update their Wii? That seems a little weird. I'm still on 3.2 and don't see the point in updating beyond that