bootmii et le nouveau boot 1V3
Posté: Dim 22 Fév 2009 09:21après avoir lu ça sur hackmii
https://hackmii.com/2009/02/bootmii-and-the-new-boot1/
il semblerait que certaines wii ne supporteraient pas le bootmii
ces wii auraient le boot1 en version 3
voila ce que dit bushing a ce sujet
et comment vérifier votre boot1
faut verifier avec un éditeur hexa une sauvegarde d'un jeux
et vérifier sur le tableau ci dessous
bushing // Feb 19, 2009 at 4:05 am
Actually, we do have enough data to draw some conclusions.
You can get your ConsoleID (aka “NG ID”) by copying a savegame from your Wii to SD, then copying it to your computer and looking at it with a hex editor. All the way at the end, you’ll see something like
001dec0: 526f 6f74 2d43 4130 3030 3030 3030 312d Root-CA00000001-
001ded0: 4d53 3030 3030 3030 3032 2d4e 4730 3431 MS00000002-NG041
001dee0: 3462 3665 3300 0000 0000 0000 0000 0000 4b6e3...........
001def0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
In this case, the console ID is 0414B6E3.
If you sort the data we have received, a clear pattern emerges:
0201xxxx ... 021Dxxxx: boot2v2, boot1v1 (38 units)
021Exxxx ... 04A6xxxx: boot2v2 or boot2v3 (cutover at 043Cxxxx), boot1v2 (740 units)
0600xxxx ... 071Dxxxx: boot2v3, boot1v3 (89 units)
071Fxxxx, 0723xxxx: boot2v4, boot1v3 (2 units)
I’ll do up an article with graphs to illustrate this more clearly, and explain the difference between the different versions of boot1 and boot2, but in brief:
boot1v1 and v2 are almost identical; I’m still trying to find exactly what changed. boot1v3 contains the fakesign fix first seen in IOS37.
boot2v2 and boot2v3 are very similar; a small amount of code was added to send some extra commands to the DDR3 RAM chip upon startup. We’re still trying to get ahold of a copy of boot2v4.
source :hackmii
edit:
j'ai trouvé ca aussi
Current stats: 428 reports of “normal” (compatible) boot1 (2cdd…), 22 reports of “variant 1″ (4a7c…) and 40 reports of what I was calling the “Korean boot1″ (f01e…). The latter will not be compatible with BootMii, and it looks like it’s not just Korean Wiis (or, as noted in the comments below, they could be region-changed Korean Wiis). Console IDs greater than 0×6000000 appear to be using the new “Korean” boot1, and the rest are using either the normal one or the variant.
statistiques actuelles: 428 resultats “normal” (compatible) boot1 (2cdd…), 22 resultats de“variant 1″ (4a7c…) and 40 resultats de ce que j'apellerais le “Korean boot1″ (f01e…). Ce dernier n'est pas compatible avec BootMii, et il semblerait que ca ne serait pas juste les Wiis korenne(ou ca peut-etre aussi des Wiis Korenne "region-changed" ).l'IDs de la Console plus grand que 0×6000000 paraissent utiliser le nouveau “Korean” boot1,
et le reste utilisent soit la normale ou la variante.
note:
2cdd,4a7c,f01e :
visible sur l'ecran pendant l'execution du cheker bootmii
enfin si j'ai bien tout compris
https://hackmii.com/2009/02/bootmii-and-the-new-boot1/
il semblerait que certaines wii ne supporteraient pas le bootmii
ces wii auraient le boot1 en version 3
voila ce que dit bushing a ce sujet
et comment vérifier votre boot1
faut verifier avec un éditeur hexa une sauvegarde d'un jeux
et vérifier sur le tableau ci dessous
bushing // Feb 19, 2009 at 4:05 am
Actually, we do have enough data to draw some conclusions.
You can get your ConsoleID (aka “NG ID”) by copying a savegame from your Wii to SD, then copying it to your computer and looking at it with a hex editor. All the way at the end, you’ll see something like
001dec0: 526f 6f74 2d43 4130 3030 3030 3030 312d Root-CA00000001-
001ded0: 4d53 3030 3030 3030 3032 2d4e 4730 3431 MS00000002-NG041
001dee0: 3462 3665 3300 0000 0000 0000 0000 0000 4b6e3...........
001def0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
In this case, the console ID is 0414B6E3.
If you sort the data we have received, a clear pattern emerges:
0201xxxx ... 021Dxxxx: boot2v2, boot1v1 (38 units)
021Exxxx ... 04A6xxxx: boot2v2 or boot2v3 (cutover at 043Cxxxx), boot1v2 (740 units)
0600xxxx ... 071Dxxxx: boot2v3, boot1v3 (89 units)
071Fxxxx, 0723xxxx: boot2v4, boot1v3 (2 units)
I’ll do up an article with graphs to illustrate this more clearly, and explain the difference between the different versions of boot1 and boot2, but in brief:
boot1v1 and v2 are almost identical; I’m still trying to find exactly what changed. boot1v3 contains the fakesign fix first seen in IOS37.
boot2v2 and boot2v3 are very similar; a small amount of code was added to send some extra commands to the DDR3 RAM chip upon startup. We’re still trying to get ahold of a copy of boot2v4.
source :hackmii
edit:
j'ai trouvé ca aussi
Current stats: 428 reports of “normal” (compatible) boot1 (2cdd…), 22 reports of “variant 1″ (4a7c…) and 40 reports of what I was calling the “Korean boot1″ (f01e…). The latter will not be compatible with BootMii, and it looks like it’s not just Korean Wiis (or, as noted in the comments below, they could be region-changed Korean Wiis). Console IDs greater than 0×6000000 appear to be using the new “Korean” boot1, and the rest are using either the normal one or the variant.
statistiques actuelles: 428 resultats “normal” (compatible) boot1 (2cdd…), 22 resultats de“variant 1″ (4a7c…) and 40 resultats de ce que j'apellerais le “Korean boot1″ (f01e…). Ce dernier n'est pas compatible avec BootMii, et il semblerait que ca ne serait pas juste les Wiis korenne(ou ca peut-etre aussi des Wiis Korenne "region-changed" ).l'IDs de la Console plus grand que 0×6000000 paraissent utiliser le nouveau “Korean” boot1,
et le reste utilisent soit la normale ou la variante.
note:
2cdd,4a7c,f01e :
visible sur l'ecran pendant l'execution du cheker bootmii
enfin si j'ai bien tout compris
)