Hacking CIOSCORP install GUIDE

  • Thread starter Thread starter bp2000
  • Start date Start date
  • Views Views 18,572
  • Replies Replies 115
Status
Not open for further replies.
well i think that was the plan if it happened , but its not to say that something might go wrong with an update in the way if u updated an NTSC game on a PAL region you get a brick.

same could happen with this in the future.
 
Jizmo said:
I can't believe that Marcan hasn't dropped by yet to come in and tell us all what stupid asshole we are for doing this and how it's using copyright code or whatever. Was kinda looking forward to it.

Oh yea, I forgot.... how we're gonna burn in hell!
Well this isnt all bad some people use it for legal backups
 
bp2000, there if the update wipes out Corp and takes us to say 3.5 theres also the other problems too

for example...3.5 could -- block the install/remove if found Homebrew Channel, they could even include a new IOS16 fix we dont know..

and hell yer where are the BootMii boys lol
 
bp2000 said:
djtaz said:
I dont think its automatic updating even in 3.4 - its just a rephrase of the EULA
ok so if ninty does release a update that does something to CIOSCORP than we could just downgrade to like 3.1 than update to 3.2 again and have oringinal ioses

Posts merged

[

no dowgrading will not remove the patched IOS's you need to update to the 3.3v2 or 3.4 them are the only updates that completely overwrite all IOS's

SO just Any offical updates wont and can't brick your wii, only remove the patch IOS's
 
way I ask if there are any game discs that come with IOSes that have the fakesigning bug already patched out? (v3.3b or 3.4) update ?

So i wonder what IOS versions to install to correctly "deinstall" cioscorps.
I mean there are a lot versions of for ex. IOS30's out...
 
the original idea is from WiiCrazy, not WiiPower, so add that at the top, and change WiiPower to just MCI creator....!!!
wink.gif
 
And not even sure when the newer Wii Games come out that contain the 3.4 IOS's if patching would even work, wont know until they get released. I think we would need a new method in patching the IOS's for the new 3.4 IOS's, But anyways I'm done experimenting
 
WiiBlaster said:
bp2000 said:
djtaz said:
I dont think its automatic updating even in 3.4 - its just a rephrase of the EULA
ok so if ninty does release a update that does something to CIOSCORP than we could just downgrade to like 3.1 than update to 3.2 again and have oringinal ioses

Posts merged

[

no dowgrading will not remove the patched IOS's you need to update to the 3.3v2 or 3.4 them are the only updates that completely overwrite all IOS's

SO just Any offical updates wont and can't brick your wii, only remove the patch IOS's

3.3v2 is impossible, I downgrade the other day to 2.0 then back to 3.3, I only saw one 3.3 on the list from Nintendo's servers. Unless they replaced the old 3.3 entirely with the version 2.
 
WiiBlaster said:
bp2000 said:
djtaz said:
I dont think its automatic updating even in 3.4 - its just a rephrase of the EULA
ok so if ninty does release a update that does something to CIOSCORP than we could just downgrade to like 3.1 than update to 3.2 again and have oringinal ioses

Posts merged

[

no dowgrading will not remove the patched IOS's you need to update to the 3.3v2 or 3.4 them are the only updates that completely overwrite all IOS's

SO just Any offical updates wont and can't brick your wii, only remove the patch IOS's
ok so we could update to 3.3 than than to the future update (3.5)
 
I just love how people talk about newer updates they know nothing about, If the 3.4 completely overwrites your IOS's dont you think 3.5 would do the same thing it would have to.

Anyways i never update my wii i only install the IOS's i need
 
ether2802 said:
the original idea is from WiiCrazy, not WiiPower, so add that at the top, and change WiiPower to just MCI creator....!!!
wink.gif
thanks i fixed it
 
jeesh i dont look at the board for a few hours and some noob puts up a shitty how to on something that most people shouldn't even be messing with. Sad. Especially considering those that made it had agrees that it wasn't ready for a guide to be put up.. at least with the official thread people had to read and completely understand all the risks and what they were doing and everything was together in one place. Its people like this that give the hacking scene a bad name, attempting to gain fame off of others work.
 
WiiBlaster said:
I just love how people talk about newer updates they know nothing about, If the 3.4 completely overwrites your IOS's dont you think 3.5 would do the same thing it would have to.

Anyways i never update my wii i only install the IOS's i need


my ios30 for example, has v1040 atm.
Should I better install a ios30 v1040 or is it better to install an ios v2576?
 
mine is 2576, i'm not sure of the difference but i know the system menu will run off of either one on any region Wii
 
digitydogs said:
jeesh i dont look at the board for a few hours and some noob puts up a shitty how to on something that most people shouldn't even be messing with. Sad. Especially considering those that made it had agrees that it wasn't ready for a guide to be put up.. at least with the official thread people had to read and completely understand all the risks and what they were doing and everything was together in one place. Its people like this that give the hacking scene a bad name, attempting to gain fame off of others work.
im not a noob im just new to this site and have you rechecked my guide its goten a lot better and it said not to make a guide when it envolved patching ios249 but now thats not nesserary it is now much safer and i strongly stress the risks in my guide
 
Never the less digity is right bp2000

if you had followed the hole thread and read the comments from the creators you would know that they didnt want a guide been made for this.

it was a total no go, especially by some one who was not involved in the project.
 
I'm sorry but even in your own thread you are being corrected about what this can and can't do and are asking noob questions. That alone to me says you had no business doing this. And FYI 002 errors dont happen using this method. So you might wanna remove that from the initial post as well. You should also point to the original thread, since you neglected to include any of the answers to the questions everyones spent the last week figuring out. You know a nice warning not to uninstall these wads as they will leave you without any IOS and bricked would be nice too. This in one of the things that when a guide was finally put up it shouldn't have needed improving or changing until another breakthrough was made. But you'll learn. I just hope your presumption in doing this doesn't stop any of us that were working/helping with this from attempting another project, seeing as how you'd probably try to steal credit for that too with another half ass guide.
 
20clarky08 said:
Never the less digity is right bp2000

if you had followed the hole thread and read the comments from the creators you would know that they didnt want a guide been made for this.

it was a total no go, especially by some one who was not involved in the project.
ya i know but wiiblaster also made a guide on a different website and i thought that they didnt want a guide when it evolved patching ios249
 
Fors must be laughing so loud at us right now, because of the lame approach to a cSM...!!!
laugh.gif
 
bp2000 said:
20clarky08 said:
Never the less digity is right bp2000

if you had followed the hole thread and read the comments from the creators you would know that they didnt want a guide been made for this.

it was a total no go, especially by some one who was not involved in the project.
ya i know but wiiblaster also made a guide on a different website and i thought that they didnt want a guide when it evolved patching ios249
Yes on another site that doesn't have every noob to the scene trying every guide they see. He was directly involved with this and has alot of experience There were good reasons a guide wasnt posted here and we were making everyone read through the whole 40 some odd pages.
Sorry if i sound like a dick, we have enough people on here jumping into things before they are sure they know what they are doing, and without fully reading detailed guides. Making a guide that doesnt even explain in detail what this does and why is just wrong. You hit one of my pet peeves. But im done with my rant, unless you want me to keep going.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum