Hacking New "unmoddable" Wii

  • Thread starter Thread starter Scarfish
  • Start date Start date
  • Views Views 7,767
  • Replies Replies 41
oh good lord, now your arguing in German. That's it, I'm out of here, lol.
laugh.gif


anyway, I did some searching, found nothing on that serial number.

Looks like more headaches for new wii owners for a bit, lol.
 
if there is a new wii serial theres going to be alil bit of buzzing going around lol
 
It's pretty easy. Just assume that every Wii you see now in the stores is "unsoftmoddable" and that every Wii that was bought with 3.4 (or higher) on it is one of them.
 
TroyTheZombie said:
oh good lord, now your arguing in German. That's it, I'm out of here, lol.
laugh.gif


anyway, I did some searching, found nothing on that serial number.

Looks like more headaches for new wii owners for a bit, lol.

Pretty sure it's just the PAL equivilent of a LU64. Should be solvable with cboot2.
 
Heres an Idea...... since the latest CIOS's can be installed on the lu64 wiis with system menu 4.0 why not on these. Simply install bootmii as IOS. once this is done use wiigator's cboot2 v16 with bootmii IOS. (yes it shopuld work.) then this should enable you to install the CIOS 38 rev 13..... I do believe you will need to obtain a wad of this file. None the less I myself have not done this but it is my understanding that that is the purpose of cboot2......... With that you should manage to get the CIOS installed and that should then enable you to manage to modify the system the rest of the way. Since we can get a trucha compatible IOS on these wiis we should really patch the truch bug into the updated IOS's and then install them on the wiis......
 
FYI, I think these are the two main guides I've seen for lu64 / "less hackable consoles". Both appear to have very high success rates.

If you have 3.4

http://gbatemp.net/index.php?showtopic=152406

If you have 4.0

http://www.wiihacks.com/wii-custom-softwar...s-menu-4-a.html

I suspect you'll need the 4.0 one now. If you use it, be use to "uninstall" when directed.

Question: someone mentioned using cboot2 ala the 4.0 guide... would the 4.0 guide also work on 3.4 lu64/65?

Also, if anyone by chance has found brick protection for these consoles, please advise.

Thanks.
 
Sure it would work. But on 3.4 it's much easier to simply install IOS16 instead of going through the trouble of using cboot2 if you don't have to.
 
Wow, I'm off one night and hell breaks loose
tongue.gif
.

Anyway thanks all for replying. Gonna see this Wii as a LU64+ Wii now (and all the Wii's I see from now on with 3.4 as default).

@WiiPower: You say dont downgrade IOS35 but isn't it a good way to see if a Wii is going to bug you? I mean downgrade IOS35 look if IOS_ReladIOS(35) works. If it hangs you have an anoying (new) Wii. If it won't hang you don't have a bugging Wii. After this test reinstall the latest IOS35. (Please don't kick me in the nuts, since this was only an idea, a stupid one maybe but hey we all gotta learn
tongue.gif
)
 
Scarfish said:
Wow, I'm off one night and hell breaks loose
tongue.gif
.

Anyway thanks all for replying. Gonna see this Wii as a LU64+ Wii now (and all the Wii's I see from now on with 3.4 as default).

@WiiPower: You say dont downgrade IOS35 but isn't it a good way to see if a Wii is going to bug you? I mean downgrade IOS35 look if IOS_ReladIOS(35) works. If it hangs you have an anoying (new) Wii. If it won't hang you don't have a bugging Wii. After this test reinstall the latest IOS35. (Please don't kick me in the nuts, since this was only an idea, a stupid one maybe but hey we all gotta learn
tongue.gif
)

That's not stupid, it's the same i would do to check if a Wii is one of "them". But until now i did not see this explanation nor the instructions to restore IOS35 afterwards in any guide.
 
Thanks WiiPower for clearing that up.

One more question tho: Why do we need to use cboot2 for running wadmanager and removing and installing IOS16? Isn't it possible to do it with the normal wad manager using IOS36 or something?
 
FenrirWolf said:
Sure it would work. But on 3.4 it's much easier to simply install IOS16 instead of going through the trouble of using cboot2 if you don't have to.

How much easier? You can just install BootMii while you're putting HBC on anyway, and then it's a matter of running the cboot2 wad manager instead of an IOS16 one. I guess some people have problems getting cboot2 going...it went right through for me, and I've never had to go through all the steps of making the files for it once I had a working set.

QUOTE said:
That's not stupid, it's the same i would do to check if a Wii is one of "them". But until now i did not see this explanation nor the instructions to restore IOS35 afterwards in any guide.
Bah, I've said a dozen times that you can use this as a check, then just run the IOS35Downgrader again and do a system update to get it back (at that point you're still virgin anyway)

QUOTE(Scarfish @ Jun 19 2009, 03:10 AM)
One more question tho: Why do we need to use cboot2 for running wadmanager and removing and installing IOS16? Isn't it possible to do it with the normal wad manager using IOS36 or something?

Because that's the point of the whole thing. You need an IOS with the fakesign bug to get the ball rolling, and the cboot2 method gives you a modified WadManager/IOS36 from which you can install whatever you want. (Most guides opt for IOS16 and/or LU64FIX.wad but there's no reason you couldn't go straight to cIOS rev13 or a patched IOS36 or anything else you had a wad for)
 
So what you're saying is that with the cboot2 Wad Manager you don't need an IOS with the trucha bug for installing fake signed wads. So the steps in some guides that opt for using the cboot2 wad manager for removing IOS16 first and then install the old trucha bug version so you could use that IOS for installing a custom IOS are not needed.
Just install a cios using this wad manager and your fine? Installing hacked WiiWare games would also work right (no blocking from the new Wii's or something I mean)?
 
Scarfish said:
So what you're saying is that with the cboot2 Wad Manager you don't need an IOS with the trucha bug for installing fake signed wads. So the steps in some guides that opt for using the cboot2 wad manager for removing IOS16 first and then install the old trucha bug version so you could use that IOS for installing a custom IOS are not needed.
Just install a cios using this wad manager and your fine? Installing hacked WiiWare games would also work right (no blocking from the new Wii's or something I mean)?

exactly
most guides are giving you unprecise and unnecessary steps anyway, that's why it's alway better not being the lazy one and do some research first, will eventually pay some day
 
QUOTE said:
My brother in law just bought a Wii with serail LEF1213....
On the Wii was System Menu 3.4 and he updatet it to 4.0.

just curious to know if this was bought brand new or second hand ???

mine is about 2 weeks old "LEH24" i guess serials don't have any set way of increasing i.e. LEA B C D etc etc

friend has LEH15 and looks like thing work fine

i've not tried anything apart from installing HBC

bootmii couldn't be installed as boot2

so i'm a bit cautious about attempting anything else until i'm sure of what i'm doing.

i'm trying to cuage how PAL serials compare to US ones
 
It seems (notice the "seems") that PAL wii aren't at this time unsoftmodable. We have some Wii that have fixed boot1 & boot2 but we don't have something like the LU64 and +.
 
I've seen Wii's with lots op LEH type serials. None of them were a problem.
Now I see this Wii (which is brand new, he has it a couple days now) with the LEF serial and my best guess is that this is new type of Wii ala LU64.

@carbonyle: I was also pretty sure that we didn't have such a PAL version Wii but apparently we do now. Let's wait for more users with a new PAL wii and a LEF serial.
 
i have a new wii 3.4 (bought today) and a softmodded launch wii. i made a nand backup using bootmii with my old wii, so i have a 3.2 nand backup.
here's my (stupid?) question: can i install bootmii (as ios) on the new (3.4E) wii and replace the nand with my 3.2 nand backup?
is it possible to restore a nand on a wii with the nand backup from another wii in general?
 
ApolloCheese said:
i have a new wii 3.4 (bought today) and a softmodded launch wii. i made a nand backup using bootmii with my old wii, so i have a 3.2 nand backup.
here's my (stupid?) question: can i install bootmii (as ios) on the new (3.4E) wii and replace the nand with my 3.2 nand backup?
is it possible to restore a nand on a wii with the nand backup from another wii in general?
NO just don't do it!
Every wii has different key (I'm not taking about common-key)
BUT I know Bushing offer some kind of things (he just charge 10$) cannot find anymore the link and it's a particular case.
 
carbonyle said:
ApolloCheese said:
i have a new wii 3.4 (bought today) and a softmodded launch wii. i made a nand backup using bootmii with my old wii, so i have a 3.2 nand backup.
here's my (stupid?) question: can i install bootmii (as ios) on the new (3.4E) wii and replace the nand with my 3.2 nand backup?
is it possible to restore a nand on a wii with the nand backup from another wii in general?
NO just don't do it!
Every wii has different key (I'm not taking about common-key)
BUT I know Bushing offer some kind of things (he just charge 10$) cannot find anymore the link and it's a particular case.

There IS a way to reencrypt with the correct keys, complicated, but doable. The problem is the instant brick in this case because of:
- Not accepted boot2 version
- If boot2 was not overwritten, then the system menu IOS wouldn't be accepted
 

Site & Scene News

Popular threads in this forum