I agree with you however not everybody can remove the nand chips so easy without breaking the board. I have a hot air station and then it is a breeze.DeadlyFoez said:In the end I am finding it easier to just remove the nand. I have noticed some slight problems when writing to the hynix chips when doing a full nand restore using the infectus. I have found that about 1 out of 100 blocks wont match when compared to the source. All I have to do is just erase and rewrite that particular block and everything is fine. But the overall best way to write to the nand is to just remove it and then use a tsop48 clip to write to it. It really is so much easier and more reliable.
delicator said:Hello All
I read every 18 pages of this topic, and I'm tired ^^
I think I understand one thing,
if bricked wii is to recent, it's not boot1 compatible, and I can inject bootmii in.
But, I read in one page, perhaps we can, take off nand with bootmii installed in boot2, and sold on bricked wii, just for booting bootmii, take the nand backup (wrong backup) but with the key of processor of bricked wii.
My idea if it possible, is:
1 do copy of nand with bootmii in boot 2 with an infectus
2 replace nand bricked with this copy,
3 boot bootmii and dump (wrong dump, good key)
4 take the key, and do stuff with betwin etc...
5 flash nand
?
I dont read or I dont understand if boot2 was encrypted too, and, if a bricked wii can boot bootmii for another nand
Thank you !
Let's try that again: Boot1 is stored on the nand but cannot be modified because its hash is stored in OTP memory. boot2 is also stored on the nand and can be changed, but with a fixed boot1 it cannot be fakesigned.Erikie said:boot1 is stored inside an eeprom in the cpu, boot2 is decrypted by boot1 and hash checked against the stored hash key in OTP memory.
QUOTE said:How your wii works. This information is solely for what I have specifically asked TeamTwiizer members. Anyone feel free to correct me if I am wrong. I might not be %100 accurate about the theory but the basic concept is correct;
When you turn on your wii the first thing that happens is there is code in boot0 which is stored in the Hollywood processor.
Boot0 does a hash type check on the boot1 code which is stored in the nand. If the hash does not match the the system halts. (so boot1 versions are incompatibly on wii's that have a different boot1)
Boot1 does a hash check on boot2. If that hash check passes the boot1 will execute boot2.
On older wii's, boot1 has the famous trucha bug in it so the contents of boot2 can be manipulated and boot1 does not correctly hash check boot2.
Thank you almighty forum contributor. I appreciate your quick response and helpful informationDeadlyFoez said:Natas666 said:Anyone have a nand/keys for a wii that would work with the following?
BootMii v1.1
SysMenu - 4.1U boot1b boot2v3
The bricked Wii is 4.9U boot1b boot2v2
I keep getting the mismatch
Yeah...I wonder why? Maybe because you have no clue of what you are talking about or doing. Read the thread in my sig, and there is also a link in that thread that will give you some info so you aren't so clueless. enjoy
I did everything correct with Betwiin. The area I'm confused about is the hex editing, I'm seeing first 1024, last 1024, but wait, it's 1057 etc... I'm familiar with 010 Editor and able to edit HEX files, just need the info.DeadlyFoez said:in case you didn't find it yet http://gbatemp.net/index.php?showtopic=199055 thats the other link. Although that will not be completely helpful to you in your situation it will at least give you a little bit more info on how the wii works.
But to answer your question, if you did run betwiin to convert a nand dump then you will have some hex ediiting to do to make the converted nand dump work with your wii.
By the way, no one can give you their keys to work with your wii, unless you are using it as a donor to convert to become for your wii.
So copy 1024 worth of keys from my good flash.bin to my outputted nand from betwiin? My nand from the output has 1024 more already.DeadlyFoez said:Natas666 said:I did everything correct with Betwiin. The area I'm confused about is the hex editing, I'm seeing first 1024, last 1024, but wait, it's 1057 etc... I'm familiar with 010 Editor and able to edit HEX files, just need the info.DeadlyFoez said:in case you didn't find it yet http://gbatemp.net/index.php?showtopic=199055 thats the other link. Although that will not be completely helpful to you in your situation it will at least give you a little bit more info on how the wii works.
But to answer your question, if you did run betwiin to convert a nand dump then you will have some hex ediiting to do to make the converted nand dump work with your wii.
By the way, no one can give you their keys to work with your wii, unless you are using it as a donor to convert to become for your wii.
I was asking for a donor, since I wasn't sure if what I posted will work, meaning my good wii has SysMenu - 4.1U boot1b boot2v3 and the bricked one has 4.0U boot1b boot2v2
By what you are saying, if what you are saying is correct, then it should have worked. Make sure you put the keys at the end of the nand.bin before trying to do a nand restore.
But really, if you got bootmii in boot2, just use comex's nand formatter. It is a lot simpler.