Hacking team twiizers needs you

  • Thread starter Thread starter linkinworm
  • Start date Start date
  • Views Views 27,870
  • Replies Replies 169
The wii Was purchased within the past two maybe three weeks and It has no physical mods made. I couldn't exactly say if it's chipable as I haven't looked the System works great for homebrew after the firmware was downgraded from 3.4u to 3.2u Nothing seems to be affected by the systems different boot version.
smile.gif
It's a USA Wii. There was nothing special about it. I don't believe it was ever sent for repairs or anything like that so I'm not sure Why it has this new boot 2 other than it being a very new build.
 
Hells Guardian said:
The wii Was purchased within the past two maybe three weeks and It has no physical mods made. I couldn't exactly say if it's chipable as I haven't looked the System works great for homebrew after the firmware was downgraded from 3.4u to 3.2u Nothing seems to be affected by the systems different boot version.
smile.gif
It's a USA Wii. There was nothing special about it. I don't believe it was ever sent for repairs or anything like that so I'm not sure Why it has this new boot 2 other than it being a very new build.

Thanks for the info. The new ones might all have that now
frown.gif
 
Thats what I'm thinking but according to marcan it shouldn't be anything to worry about. I'm dumping the NAND Flash at this moment to upload for them to analyze.
smile.gif
 
computerboy said:
Hells Guardian said:
The wii Was purchased within the past two maybe three weeks and It has no physical mods made. I couldn't exactly say if it's chipable as I haven't looked the System works great for homebrew after the firmware was downgraded from 3.4u to 3.2u Nothing seems to be affected by the systems different boot version.
smile.gif
It's a USA Wii. There was nothing special about it. I don't believe it was ever sent for repairs or anything like that so I'm not sure Why it has this new boot 2 other than it being a very new build.

Thanks for the info. The new ones might all have that now
frown.gif
Well,
Than it is just more work for team twiizers... (though we can help a little
wink.gif
)

But I'm pretty sure that they get around this too
smile.gif
 
linkinworm said:
about that "bootmii"

from marcan

Not bootmii, just an old test menu that runs under bootmii.

marc holyland wrote:
> hi, someone posted http://static.hackmii.com/bootmii.elf on gba temp,
> everyones downloading it, i think you need to make a post on hackmii
> about it or something
>
> Linkinworm
> marc holyland

--
Marcan ([email protected])
Good. The last thing we needed was another "leak" case
smile.gif
I'm glad it only was a test menu, and even useless without bootmii
biggrin.gif
 
Hells Guardian said:
The wii Was purchased within the past two maybe three weeks and It has no physical mods made. I couldn't exactly say if it's chipable as I haven't looked the System works great for homebrew after the firmware was downgraded from 3.4u to 3.2u Nothing seems to be affected by the systems different boot version.
smile.gif
It's a USA Wii. There was nothing special about it. I don't believe it was ever sent for repairs or anything like that so I'm not sure Why it has this new boot 2 other than it being a very new build.
So I assume you're the one the big mean red text was talking to?
 
I just ran it, on my US Wii, got it for christmas, it said my boot1 hash started with f01e so I have the "Korean Boot1" but my Wii has never been region changed, all I've done was downgrade from 3.4U to 3.2U back up to 3.4U and am now on 3.2U and am going to go to 3.4U in a little while (I got it, hacked it yesterday, decided against the hacking, realized there was something I forgot to do (like run the checker) and I am about to un-hack again).

Just thought that tidbit of info about my boot1 was interesting/potentially helpful
 
cactusjack901 said:
I just ran it, on my US Wii, got it for christmas, it said my boot1 hash started with f01e so I have the "Korean Boot1" but my Wii has never been region changed, all I've done was downgrade from 3.4U to 3.2U back up to 3.4U and am now on 3.2U and am going to go to 3.4U in a little while (I got it, hacked it yesterday, decided against the hacking, realized there was something I forgot to do (like run the checker) and I am about to un-hack again).

Just thought that tidbit of info about my boot1 was interesting/potentially helpful

Dont worry man, almost all the news wiis contains that new boot1, plus nintendo has already released a version of boot1 higher than that, version 4 i think.
Probly Old News but i talked to marcan about my bricked launch Wii and according to Marcan he is going to be releasing a Special version of bootmii to work with Infectus nand Flasher, on bricked Wiis, with no need of a nand Dump or Nand keys,
Thank God, I'll finally be able to unbrick my old wii.
 
WiiBlaster said:
cactusjack901 said:
I just ran it, on my US Wii, got it for christmas, it said my boot1 hash started with f01e so I have the "Korean Boot1" but my Wii has never been region changed, all I've done was downgrade from 3.4U to 3.2U back up to 3.4U and am now on 3.2U and am going to go to 3.4U in a little while (I got it, hacked it yesterday, decided against the hacking, realized there was something I forgot to do (like run the checker) and I am about to un-hack again).

Just thought that tidbit of info about my boot1 was interesting/potentially helpful

Dont worry man, almost all the news wiis contains that new boot1, plus nintendo has already released a version of boot1 higher than that, version 4 i think.
Probly Old News but i talked to marcan about my bricked launch Wii and according to Marcan he is going to be releasing a Special version of bootmii to work with Infectus nand Flasher, on bricked Wiis, with no need of a nand Dump or Nand keys,
Thank God, I'll finally be able to unbrick my old wii.


Very cool. I used to be big in the PSP hacking scene, but kinda fell out of it. I sit here watching this, and it just seems to be a bit more...chill, and everybody seems to be willing to help each other and all. It really makes me wish I enjoyed hacking the wii more than I do (in fact, right now I am virgin-izing my wii and updating to 3.4U...forgive me Twiizers for I have sinned)
 
afif95 said:
Mine is f01e.....

I can't install Bootmii,
sleep.gif

My guess is you will.
As far as I can figure TT will make Bootmii compatible with all wii's out there.

BootMii isn't the challenge anymore, the core is ready. Running it on all wii's is the new hurdle to take.
They are hackers after all, they will find a way eventually. Always challenged by the system they work on.

Let's just hope this doesn't take too much time...
Not stressing here, just anxiously waiting for BootMii and what advantages it may bring us.
 
FRanatic said:
afif95 said:
Mine is f01e.....

I can't install Bootmii,
sleep.gif

My guess is you will.
As far as I can figure TT will make Bootmii compatible with all wii's out there.

BootMii isn't the challenge anymore, the core is ready. Running it on all wii's is the new hurdle to take.
They are hackers after all, they will find a way eventually. Always challenged by the system they work on.

Let's just hope this doesn't take too much time...
Not stressing here, just anxiously waiting for BootMii and what advantages it may bring us.

The problem is bigger than you think, the new boot1, is Bug Fixed, meaning, sense boot0 hash checks boot1 you can't touch boot1, therefore you can't change it or fix it, and now on the new boot1's they are Bug fixed, meaning they wont run a fake signed boot2, meaning you can't install the new bootmii sense it is a fake signed boot2. I myself dont see away around it, but hopefully you never now they may come up with something, and fix it
I myself am going back and fixin my Old Lauch Wii with a infectus , so i can use the new bootmii when it comes out, cause my new Wii has the new boot1, but you know this New boot1, is going to be in All New Wiis, Which really sucks
 
WiiBlaster said:
FRanatic said:
afif95 said:
Mine is f01e.....

I can't install Bootmii,
sleep.gif

My guess is you will.
As far as I can figure TT will make Bootmii compatible with all wii's out there.

BootMii isn't the challenge anymore, the core is ready. Running it on all wii's is the new hurdle to take.
They are hackers after all, they will find a way eventually. Always challenged by the system they work on.

Let's just hope this doesn't take too much time...
Not stressing here, just anxiously waiting for BootMii and what advantages it may bring us.

The problem is bigger than you think, the new boot1, is Bug Fixed, meaning, sense boot0 hash checks boot1 you can't touch boot1, therefore you can't change it or fix it, and now on the new boot1's they are Bug fixed, meaning they wont run a fake signed boot2, meaning you can't install the new bootmii sense it is a fake signed boot2. I myself dont see away around it, but hopefully you never now they may come up with something, and fix it
I myself am going back and fixin my Old Lauch Wii with a infectus , so i can use the new bootmii when it comes out, cause my new Wii has the new boot1, but you know this New boot1, is going to be in All New Wiis, Which really sucks

Once the old wii is fixed, you should do what I would, use one as your up to date, 100% legit wii, and use one as your hacked wii (it's what I would do with any console....except for PSP, but that's just because Mathieulh is brilliant, and any issues I have with flash0 he has a solution for)
 
WiiBlaster said:
FRanatic said:
afif95 said:
Mine is f01e.....

I can't install Bootmii,
sleep.gif

My guess is you will.
As far as I can figure TT will make Bootmii compatible with all wii's out there.

BootMii isn't the challenge anymore, the core is ready. Running it on all wii's is the new hurdle to take.
They are hackers after all, they will find a way eventually. Always challenged by the system they work on.

Let's just hope this doesn't take too much time...
Not stressing here, just anxiously waiting for BootMii and what advantages it may bring us.

The problem is bigger than you think, the new boot1, is Bug Fixed, meaning, sense boot0 hash checks boot1 you can't touch boot1, therefore you can't change it or fix it, and now on the new boot1's they are Bug fixed, meaning they wont run a fake signed boot2, meaning you can't install the new bootmii sense it is a fake signed boot2. I myself dont see away around it, but hopefully you never now they may come up with something, and fix it
I myself am going back and fixin my Old Lauch Wii with a infectus , so i can use the new bootmii when it comes out, cause my new Wii has the new boot1, but you know this New boot1, is going to be in All New Wiis, Which really sucks

This particular hole is patched. There might, of course, be more bugs available in boot1. At least, one can only hope ...
 
joda said:
WiiBlaster said:
FRanatic said:
afif95 said:
Mine is f01e.....

I can't install Bootmii,
sleep.gif

My guess is you will.
As far as I can figure TT will make Bootmii compatible with all wii's out there.

BootMii isn't the challenge anymore, the core is ready. Running it on all wii's is the new hurdle to take.
They are hackers after all, they will find a way eventually. Always challenged by the system they work on.

Let's just hope this doesn't take too much time...
Not stressing here, just anxiously waiting for BootMii and what advantages it may bring us.

The problem is bigger than you think, the new boot1, is Bug Fixed, meaning, sense boot0 hash checks boot1 you can't touch boot1, therefore you can't change it or fix it, and now on the new boot1's they are Bug fixed, meaning they wont run a fake signed boot2, meaning you can't install the new bootmii sense it is a fake signed boot2. I myself dont see away around it, but hopefully you never now they may come up with something, and fix it
I myself am going back and fixin my Old Lauch Wii with a infectus , so i can use the new bootmii when it comes out, cause my new Wii has the new boot1, but you know this New boot1, is going to be in All New Wiis, Which really sucks

This particular hole is patched. There might, of course, be more bugs available in boot1. At least, one can only hope ...

One can always hope, but the chances seem very minimal. There aren't a whole lot of mistakes to make in boot1 that make it as vulnerable as the signing bug. The signing bug was a pretty big one. So now, if boot2 has to have the correct checksum, that kind of narrows the possibilities down to a hash collision. Again, while there's always a chance of another bug being found, the outlook is grim.
 

Site & Scene News

Popular threads in this forum