Hacking StartPatch4.1

  • Thread starter Thread starter aquilino
  • Start date Start date
  • Views Views 23,988
  • Replies Replies 96
aquilino said:
all version's No health check is Health Check to Back Menu
Thanks for the re-up
wink.gif
 
Updated (using Waninkoko) to v4.1U. I was previously on 4.0U and had everything, including the previous startpatch 4.0.6 working just fine. After the 4.1U update, I went to give startpatch 4.1 a go. I get the es_indentify -1017 error and it exits.

I copied it to another card and same deal. I ended up restoring my system using a nand backup and bootmii and am now back in 4.0U.

Just for the heck of it, I tried to launch startpatch 4.1 from here (just to see if it can get past the error) and it still displays the 1017 error and kicks out of the program. I tried 4.0.6, and of course it goes right in and displays patches to install.

Any idea here?

EDIT: Nevermind. Found out and fixed it on my own. Works great. Thanks!
 
zektor said:
Updated (using Waninkoko) to v4.1U. I was previously on 4.0U and had everything, including the previous startpatch 4.0.6 working just fine. After the 4.1U update, I went to give startpatch 4.1 a go. I get the es_indentify -1017 error and it exits.

I copied it to another card and same deal. I ended up restoring my system using a nand backup and bootmii and am now back in 4.0U.

Just for the heck of it, I tried to launch startpatch 4.1 from here (just to see if it can get past the error) and it still displays the 1017 error and kicks out of the program. I tried 4.0.6, and of course it goes right in and displays patches to install.

Any idea here?

EDIT: Nevermind. Found out and fixed it on my own. Works great. Thanks!


This post does not help anyone. you should have told us what you did to fix it just in case someone will have that error later on.
 
I am using 4.1J + preloader 0.29 with no hacks.ini for brick protection. Can startpatch 4.1J co-exist with preloader on it's own settings?
 
donowprod said:
zektor said:
Updated (using Waninkoko) to v4.1U. I was previously on 4.0U and had everything, including the previous startpatch 4.0.6 working just fine. After the 4.1U update, I went to give startpatch 4.1 a go. I get the es_indentify -1017 error and it exits.

I copied it to another card and same deal. I ended up restoring my system using a nand backup and bootmii and am now back in 4.0U.

Just for the heck of it, I tried to launch startpatch 4.1 from here (just to see if it can get past the error) and it still displays the 1017 error and kicks out of the program. I tried 4.0.6, and of course it goes right in and displays patches to install.

Any idea here?

EDIT: Nevermind. Found out and fixed it on my own. Works great. Thanks!


This post does not help anyone. you should have told us what you did to fix it just in case someone will have that error later on.

RE-EDITED:

You need to have a cIOS rev12 or higher to use Startpatch v4.1. My problem was that I was using cIOS11 and cIOS10 on my second wii. Both are based on IOS36 and are not compatible with the latest Startpatch. So, if you want to go to system menu 4.1 and use startpatch 4.1, you *must* use cIOSrev12 or higher (13a, 13b)
 
Bloodlust said:
I am using 4.1J + preloader 0.29 with no hacks.ini for brick protection. Can startpatch 4.1J co-exist with preloader on it's own settings?

I don't think so, since Preloader rearranges the contents of the System Menu.
 
About the es_indentify -1017 error:

My fix was running StartPatch from a regular SD card, It just wouldn't start from my SDHC.
let us know if that was your problem...
 
condorstrike said:
About the es_indentify -1017 error:

My fix was running StartPatch from a regular SD card, It just wouldn't start from my SDHC.
let us know if that was your problem...


Definitely NOT the problem. I have two cards. One is an SDHC (A-Data 16GB) and the other is a plain old 2GB Sandisk standard SD card. The Sandisk is the card I use with bootmii since it is compatible as well. And regardless of that, after performing the above installs to get rid of my error, Startpatch loaded just fine off the a-data and the sandisk.
 
Thanks, aquilino.
I will use this when I update to 4.1

FenrirWolf said:
Bloodlust said:
I am using 4.1J + preloader 0.29 with no hacks.ini for brick protection. Can startpatch 4.1J co-exist with preloader on it's own settings?

I don't think so, since Preloader rearranges the contents of the System Menu.


The 4.0 version couldn't, but it sounds like this one can apply patches with preloader installed.

QUOTE(aquilino @ Jul 20 2009, 09:31 AM)
-apply patches with preloader installed or softmii?

- yes
 
piratesmack said:
Thanks, aquilino.
I will use this when I update to 4.1

FenrirWolf said:
Bloodlust said:
I am using 4.1J + preloader 0.29 with no hacks.ini for brick protection. Can startpatch 4.1J co-exist with preloader on it's own settings?

I don't think so, since Preloader rearranges the contents of the System Menu.


The 4.0 version couldn't, but it sounds like this one can apply patches with preloader installed.

QUOTE(aquilino @ Jul 20 2009, 09:31 AM)
-apply patches with preloader installed or softmii?

- yes

Hope to see confirmation of preloader working alongside with startpatch 4.1 soon...
 
If you are working with preloader installed in 4.1JAP in theory with all versions.

only startPatch4.1 works with sysmenu 4.1 rather 4.0

the ES_identify problem error - xxxx is due to IOS 36 patch does not work in the new ios

why runs with cios249

management is very easy loads the dol and choose the patch that you like if you don't like what unistall

bay
 
aquilino,

I see on your instructions that it says not to use 4.1 StartPatch if your IOS36 is trucha-patched, is this only for Startpatch 4.1? Is it ok if I use StartPatch 4.0.4 USA-MOD on system menu 4.0, since I have a trucha-bugged IOS36 and cIOS36rev10?
 
ayojoe said:
aquilino,

I see on your instructions that it says not to use 4.1 StartPatch if your IOS36 is trucha-patched, is this only for Startpatch 4.1? Is it ok if I use StartPatch 4.0.4 USA-MOD on system menu 4.0, since I have a trucha-bugged IOS36 and cIOS36rev10?


If that works by runs under ios 249
 
aquilino said:
the ES_identify problem error - xxxx is due to IOS 36 patch does not work in the new ios

why runs with cios249


Well, then it does not make any sense. If startpatch 4.1 is only using cIOS249, then I should never have received that error (since I have cIOS 13a installed as 249). I still got the error however, and performing the above steps fixed it.


EDIT:

AHA! I found the problem! Forget the above steps I posted. Only one thing is needed is to install a cIOS rev12 or HIGHER. This should be added to the readme.

The reason I got the -1017 error previously was because I was running cIOS11 (which is based off of IOS36). I tried on another wii I have here with cIOS rev10 (also based off of IOS36) and got the same error. After installing cIOS13a, the error disappeared. This is becuase cIOS13a (and 12, 13b) are based off of IOS38.
 
zektor said:
aquilino said:
the ES_identify problem error - xxxx is due to IOS 36 patch does not work in the new ios

why runs with cios249


Well, then it does not make any sense. If startpatch 4.1 is only using cIOS249, then I should never have received that error (since I have cIOS 13a installed as 249). I still got the error however, and performing the above steps fixed it.


EDIT:

AHA! I found the problem! Forget the above steps I posted. Only one thing is needed is to install a cIOS rev12 or HIGHER. This should be added to the readme.

The reason I got the -1017 error previously was because I was running cIOS11 (which is based off of IOS36). I tried on another wii I have here with cIOS rev10 (also based off of IOS36) and got the same error. After installing cIOS13a, the error disappeared. This is becuase cIOS13a (and 12, 13b) are based off of IOS38.

Cios 249 have a patch that is fs permisions to nand flash to read and write

TBR 1.0 wiipower ,install this patch and fixes the error in IOS36-64-v3094 and all ios

patch_fsperms

u8 old_table[] = {0x42, 0x8B, 0xD0, 0x01, 0x25, 0x66};
u8 new_table[] = {0x42, 0x8B, 0xE0, 0x01, 0x25, 0x66};

startpatch4.1 working with new IOS36-64-v3094
 
All is working fine except my Gamecube PAL games. It worked in 4.0. Would it be possible to update it to region free Gamecube Games?
 
aquilino said:
ayojoe said:
aquilino,

I see on your instructions that it says not to use 4.1 StartPatch if your IOS36 is trucha-patched, is this only for Startpatch 4.1? Is it ok if I use StartPatch 4.0.4 USA-MOD on system menu 4.0, since I have a trucha-bugged IOS36 and cIOS36rev10?


If that works by runs under ios 249
Wait I am confused. I'm going to restate what I said.

I'm trying to use StartPatch 4.0.4 USA-MOD for SM 4.0. (NOT 4.1) I'm sorry I have to talk about it here but the thread for it is dead.

The 4.1 StartPatch says it's dangerous to have a trucha-patched IOS36. I have a trucha-patched IOS36 w/ patched ES_identify.

Does this matter for the 4.0.4. USA-MOD StartPatch? Can I still use it?
 
aquilino said:
If you are working with preloader installed in 4.1JAP in theory with all versions.

only startPatch4.1 works with sysmenu 4.1 rather 4.0

the ES_identify problem error - xxxx is due to IOS 36 patch does not work in the new ios

why runs with cios249

management is very easy loads the dol and choose the patch that you like if you don't like what unistall

bay

So you are saying that startpatch 4.1J works with preloader 0.29? And it only works properly when cios249rev13 is installed? ES_Identify errors will occur with rev10?
 

Site & Scene News

Popular threads in this forum