Notes from inside your Wii

HackMii header image 2

Even More NAND Flash Hax

July 25th, 2008 by bushing · 61 Comments

ChipD is a lean, mean, solderin’ machine — I have some of these TSOP sockets, and they are really really hard to solder down to a PCB that you actually care about. Also, they tend to melt if you breathe on them — but maybe that’s just me. I really like the way he made that slick cutout panel for the socket.

Around The World (ChipD’s 3-region Wii)

Beyond soldering a socket in place of the NAND flash chip, he programmed two spare flash chips with dumps from a PAL Wii and an NTSC/J Wii. He converted those two dumps to run on his Wii using an early version of some of my UnbrickMii project code (“betwiin”). No news yet on release plans; it still needs a lot of work, but it’s interesting to note that there are absolutely no hardware differences between Wiis from different regions.

Tags: Wii

61 responses so far ↓

  • 1 kwijibo // Jul 25, 2008 at 1:59 am

    So where did he get the spare flash chips?

  • 2 Naamah31 // Jul 25, 2008 at 1:59 am

    So great !!! I can’t wait to transform my JAP Wii in a USA one (don’t understand japanese)…
    BTW, did ChipD managed to use the dual CE NAND ?

  • 3 Hatch // Jul 25, 2008 at 2:27 am

    Can this be done the “soft” way – burn the entire NAND in one go (reading it from e.g. SD)?

  • 4 Louise // Jul 25, 2008 at 3:02 am

    I thought the unique keys prevented from swapping the flash???

    For those who would like to dump the video on to your harddrive open the URL “about:cache” and click “disk” and seach for “flv”. In Firefox, of course.

    I am going to keep it for some time =)

  • 5 Homebrew - Die 3 Region Wii - Wiihack.de // Jul 25, 2008 at 3:38 am

    […] Die 3 Region Wii In bushings Blog ist ein Video aufgetaucht welches eine 3 Region Wii zeigt mit 3 verschiedenen NAND Flash Überzeugt euch selbst: Video: http://www.metacafe.com/fplayer/1542…region_wii.swf bushings Blog: Even More NAND Flash Hax […]

  • 6 IBNobody // Jul 25, 2008 at 5:34 am

    Good job, ChipD. I know that those sockets are a pain, but you only had to do it once!

  • 7 daedalus // Jul 25, 2008 at 6:13 am

    YP, he’s not going to release the exploit. I know this is a crazy idea, but consider buying your games. You know, like from a store, or a website.

    Anyway, if the only difference between different region Wiis is on the flash chip, does that mean we could create some kind of region swapping homebrew program? Of course this would be absurdly risky and likely to brick a few Wiis in testing etc. etc., but it’s possible?

  • 8 TioSolid // Jul 25, 2008 at 7:31 am

    Me too. What about the video hardware? Since the signal between PAL and NTSC are different, the hardware should be too, shouldnt it?

    And Bushing, why dont you syndicate your full RSS feed? ;/

  • 9 ProdigySim // Jul 25, 2008 at 8:15 am

    @Louise: The unique keys can be dumper, per the recently-released xyzzy. ChipD presumably dumped those NAND with Infectus hardware, decrypted them, and then re-hashed and re-encrypted their Content’s with his Wii’s NAND keys.

    @TioSolid: Nope, not even that is different :). What mode is used is completely set by software.

  • 10 ProdigySim // Jul 25, 2008 at 8:17 am

    Bah, no edit. Sorry about the horrid number of typos I left in that comment :/

  • 11 Comedy // Jul 25, 2008 at 8:37 am

    Man, I wish I could solder tat well with shakes like that.

    Nice work though… I’m cusious, how much are these chips?

  • 12 Raul // Jul 25, 2008 at 9:31 am

    This means that someone has discovered the HMAC algorithm?

  • 13 ChipD // Jul 25, 2008 at 10:09 am

    @ Naamah31

    Yeah the dual CE nand did work, well atleast one of the banks worked, but the other bank had a bad block in a bad spot that prevented the system menu to boot, so it just hung at the warning screen.

    @ TioSolid
    yeah the video signal between PAL and NTSC-U/J is different,so its probably all in the software on the video decoder, but my plasma supports NTSC & PAL.

    @ Comedy
    LOL yeah i do drink alot of coffee, but i am shaky without coffee, just not as bad as i was in the video,i had to lean over the table so that made it worse, but when im soldering, xanax works wonders :)

    About the nand chips…..
    I yank them out of usb flash drives.Besides the 2 nands found in Wii’s , I found two others that work:
    Hynix HY27UG084G2M
    Samsung K9K4G08U0M

    You can find the Hynix in sony 512 microvault plus flash drives.

  • 14 Zim // Jul 25, 2008 at 10:20 am

    Ssswwweeeeeettt hack. I wish I had the tools and the time to do all of this.

  • 15 Knocks // Jul 25, 2008 at 11:57 am

    So eventually we can stick two of these in a Wii and change system region with a Radio Shack switch? :)

    That’s the only GameCube feature still missing on my Wii.

  • 16 Link // Jul 25, 2008 at 12:34 pm

    That’s interesting to watch.. for the hardware differences.. I’d be kinda interested: is it really absolutely identical or is the Wii outputting a signal with the wrong color system (like NTSC using NTSC-J firmware and still NTSC with the PAL firmware) or does even that switch? I know that’s basically TioSolid’s question but I am interested in that.. btw. a dirty trick to check the color output if the TV supports both NTSC and PAL.. if you plug a RGB cable on a NTSC Wii the screen should go completely red. If you use component, PAL and NTSC “do not exist” anymore.

    I could also imagine an S-video cable on a PAL Wii behaving strangely, though I haven’t tested.

  • 17 bushing // Jul 25, 2008 at 12:52 pm

    The hardware is 100% identical. The only differences between a PAL Wii and an NTSC Wii are:

    * PAL System Menu
    * PAL Channels
    * The data file in flash that specifies the region and serial number.

    This probably reduces a lot of the cost for Nintendo, since they only have one design to test and troubleshoot. To convert a Wii from one region to another, you need to replace five files in order to get it to boot, and then install the right versions of the channels. This is tricky, but not *that* tricky — as with most of these things, the problem is that we still have no real recovery if something goes wrong part-way through.

    And, yes, it should be possible to create a “universal-region Wii” in software — the challenge there would be figuring out the right way to do it (do you make it autodetect the region from the game, so that the game will always work in its native video mode, or do you make it try to force the game to work with your preferred video mode? etc)

    @Raul: Yes, one of my iphone-devteam buddies (gray) helped me out with reversing the HMAC scheme.

  • 18 TioSolid // Jul 25, 2008 at 1:39 pm

    Bushing, probably the first. You can already patch images and their region code and sign them again, but some games refuses to boot (or boot and dont show anything, I dont know).

    About the HMAC algo, this means that you can recovery a bricked Wii if you have their unique keys and are able to physically replace the chip? (since you can take a firmware dump, change it keys and sign it again)

  • 19 ChipD // Jul 25, 2008 at 2:10 pm

    Anyone wanna send me a bricked wii to fix for them, free of charge, you just pay the shipping fee’s? :)

    Of course by bricked i mean no physical hardware damage, unless its a bad nand chip, ive got an extra i can spare :)

  • 20 Knocks // Jul 25, 2008 at 3:03 pm

    Bushing: region switching would have to be done manually, otherwise, you won’t be able to manage out-of-region memory card saves without a disc in the system. Wii/Gamecube doesn’t recognize foreign memory cards and prompts you to format them.

  • 21 Raul // Jul 25, 2008 at 5:01 pm

    Then now the recovery mode can be a reality. I believe that with this discovery you will be near of obtaining it.

  • 22 Newbie // Jul 25, 2008 at 9:20 pm

    Apparently ChipD is able to get another [region] Wii NAND dump, decrypt it, encrypt with his Wii keys and flush it.
    One missing piece for recovery mode is the NAND programmer for bricked Wii.
    It was a discussion started by bushing around two month ago on this site on how made cheap one, but it was died…

    I was wondering if “Infectus chip” is a best option still.
    IMO, it might be the thing that really hold people to experiment with their Wii – not able to rollback in case it’s get bricked.

  • 23 ChipD // Jul 25, 2008 at 10:18 pm

    @ Newbie

    Infectus/nand programmer is the only option for a bricked wii with no nand or keys backed up.If you dont have either of them your out of luck.
    So in general if your waiting on a software solution to unbrick a fully bricked wii, dont hold your breath.

    Recovery mode referrs to a preventitive measure for non bricked wii’s, so that in the future you can hopefully recover from a currupted file system.

  • 24 buntyverma5515 // Jul 25, 2008 at 10:26 pm

    Great work ChipD and Bushing ,cant wait for it ,i have an ntsc-J wii and tired with that jap menu ,Could you please tell me any rough estimates by when would u be releasing this ? and also may be you can release these on partly basis ,like for example converting the jap menu -> english first since a lot of ppl are waiting for this thing ,thank you so much ,you guys ROCK !!! :)

  • 25 CrazyD // Jul 26, 2008 at 12:38 pm

    @ ChipD :

    “Infectus/nand programmer is the only option for a bricked wii with no nand or keys backed up.If you dont have either of them your out of luck.”

    Can i assume from this that it is possible to make a sofware only, Unbricker? (if one has enough foresight to dump their nand and keys before it is bricked)

  • 26 CrazyD // Jul 26, 2008 at 12:39 pm

    nvm… sry i got it… there REALLY should be an edit button…

  • 27 dwalker615 // Jul 26, 2008 at 4:32 pm

    i know this is probably a noob comment, i have always been good at following peoples instructions, and i’m really good with a soldering iron, but i have absolutly know clue why or how any of this works, i would appreciate if you could point me in the right direction to even beginning to learn what exactly is done and how to do it, i would like to think i am creative and intelegent enough to do it, and could be benificial to the scene if i was more educated in actuall programming. i was hoping you could point me in the right direction of learning the more technical side.

  • 28 Newbie // Jul 26, 2008 at 5:06 pm

    Infectus/nand programmer is the only option for a bricked wii with no nand or keys backed up.If you dont have either of them your out of luck.
    I hope you meant: to unbrick a Wii, one need a nand programmer AND the Wii nand backup.
    A nand backup for the Wii can be created from ANY other Wii nand backup, providing both source and bricked Wii keys are known.

    So in general if your waiting on a software solution to unbrick a fully bricked wii, dont hold your breath.
    Actually I do! :-)
    It above assertions are true,
    We (community) don’t have a program to decrypt/encrypt nand images still. I guess, ether the program OR full spectrum of decrypted nand images will be available soon enough.

    We don’t have Cheap Nand Programmer (CNP) schematic for in-place programming.
    What you did is amazing, but your solution is obviously not for everybody.
    IMO, it should be DoItYourself project around 40-60$.
    So again: I was wondering if “Infectus chip” is a best option still.

  • 29 Newbie // Jul 26, 2008 at 5:22 pm

    The previous posts on NAND programmer I was referring too are:

  • 30 ChipD // Jul 26, 2008 at 10:22 pm

    @ CrazyD

    Yeah it is confusing the way i worded it (i wanted to edit it after i hit submit…oh well)


    What i was trying to say is that once your system menu is corrupted, and you cannot get past boot2, (into the system menu) there is no way to fix it without hardware like the infectus or another type nand programmer.But it is possible to fix even without having already backed up your keys or dumped your nand prior to the bricking.And thats what im working on now, just waiting on a bricked wii.Yes i could brick my wii on purpose, but whats the fun in that when i already have the keys and dumps to recover.I want to do it from scratch.Its just a better challenge for me, just like cookies taste better from scratch :) (that was my attempt at an analogy)

  • 31 Newbie // Jul 27, 2008 at 11:25 am

    Once a Wii is bricked… it is possible to fix even without having already backed up your keys or dumped your nand prior to the bricking.

    And thats what im working on now, just waiting on a bricked wii.
    I guess you meant “a bricked Wii with signing bug in boot0″, right?
    And you, probably, work on boot1 replacement able to extract keys. That’s totally cool man! :-)

    @bushing & co.
    Why does everybody keep ignoring Cheap Nand Programmer (CNP) questions?
    This is the major reason why you guys works alone – nobody has a way to recover from mistake, except you!
    The way I see it – Bushing keeps this site to let us start/learn Wii programming, but nobody wants to accept the risk bricking it without a way to recover. IMO, I have repeated it more than ten times already… Of course, it IMO only… Do you think I’m wrong?

  • 32 ChipD // Jul 27, 2008 at 12:12 pm

    @ Newbie

    Whats being ignored? The cheapest Nand Programmer i know of is the infectus.Thats what i use along with amoxiflash.I would guess the reason nobody else attempts any of this stuff is the level of difficulty working with nands.But with that said, I have verified that YAWND (yet another wii nand dumper) version 0.3 does infact dump a useable image that you can write back to the nand with an infectus as long as you choose the normal +ecc option.And along with xyzzy your in good shape if you have those two things prior to messing with the nand.Even if you are really bad at soldering and you toast your wii’s nand, you can always recover by replacing the nand with one of two comparable nands from samsung and hynix which i listed in comment #13.I even listed a usb flash drive that contains one.So really the only real danger is lifting the tsop pads on the wii’s mainboard.So if you think you can tackle soldering with nands, then make sure you take those steps before doing so.

  • 33 Newbie // Jul 27, 2008 at 1:10 pm

    Whats being ignored?
    Could somebody put together a total dummies guide “How to mess with Wii NAND”
    I can provide initial draft!
    Something like:
    1. Get Wii NAND dump using YAWND (link)
    1a. Get Wii keys (link)
    2. Verify dump using this program (links linux | win)
    3. Get infectus chip this version (“InFeCtuS 2″???) with PC programmer (link)
    4. Install it
    5. Install additional button using this bushing post (link + schematic)
    5a. It there any unused ports on infectus to use instead of bushing/D0 button*?
    6. Use amoxiflash (link)
    7. Test amoxiflash & invectus by overwriting some unimportant NAND block.
    8. Verify #7 by reading/hash calculating by Wii program (very easy, but need to be written still)
    9. Restore whole NAND from backup on step #1 (scary!)

    A program to decrypt/encrypt NAND dump using corresponding Wii keys.

    Please correct if miss anything.

    Still wondering, am I the only one thinking this would be very useful?

    * bushing/D0 button is pushbutton to short D0 to ground during Wii powerup (check amoxiflash link for further details):
    … follow this sequence:
    Plug in power cable to Wii. Observe power light coming on (red or orange LED).
    Hold down special pushbutton to short D0 to ground.
    Press Power button on front of Wii — watch LED turn green.
    After LED turns green, release D0 button. You only need to keep that button held down for maybe half a second.
    When the Wii turns on and the LED goes green, boot0 will run and it will try to load boot1 from the NAND flash. If you hold down D0, it will fail, and everything will halt; this will keep power applied to the NAND flash chip, but it won’t try to access the chip.

  • 34 Newbie // Jul 27, 2008 at 1:11 pm

    Few related questions:
    1. The latest one is “InFeCtuS 2″ chip, does it address bushing button problem?
    2. How long does it take you to write whole NAND image? Bushing said it was ~8 hours…
    3. Does it make any sense to modify amoxiflash to restore only blocks with changed content and leave unchanged alone. It might speedup NAND restore drastically and prolong NAND life as well.

    4. Does anybody know what the difference between “InFeCtuS 2″ & “InFeCtuS”chips?

  • 35 ChipD // Jul 27, 2008 at 2:05 pm

    @ Newbie

    The D0 trick isnt related to the infectus 1/2 itself.It just shorts D0 to ground and halts activity to and from the nand.Ive always took the external approach to dumping & writing so i really cant help you with it.I compile the amoxiflash source code for linux, and it takes roughly 90 minutes to dump, and 3 hours to write using rev 28.

    Bushing will have to answer 3.

    I have the original infectus so i cant help with infectus 2 , but im guessing either should work the same.

  • 36 Newbie // Jul 27, 2008 at 2:52 pm

    Right, with “external approach” you don’t have to care about halting Wii activity.

    Infectus 1 + Amoxiflash v28 read/write times are 1.5/3 hours (full NAND dump)
    But it means write time will be never less than 1.5 hours, unless somebody modifies Infectus microcode to make if faster:
    1. Work with 4K blocks
    2. Skip overwrithing same pages.
    3. Not sure where is the slowest chain element, but it is possible compare Hash instead of data itself.
    Not sure if every NAND page has its Hash calculated ether. Or compare ECC if Hash is not available.
    What is the probability of 32 bit ECC collusion on 4K blocks?

    About infectus vs infectus 2 – the later has 2 boards connected with a flat cable, USB connector sits on the second one. I.e. you don’t need to open console to reflash it.

    Infectus 2 is USB2, don’t know about Infectus 1…
    I.e. with the right Infectus microcode Wii firmware update would be instantaneous! :-)

  • 37 buntyverma5515 // Jul 28, 2008 at 6:20 am

    Guys Please atleast tell us when ru releasing this ,I have a friend who has a bricked wii ,unfortunately i told him abt this and hes gone pretty impatient ,and even i am tired with my japenese language of my wiii ,Please Please please

  • 38 Zim // Jul 28, 2008 at 11:19 am

    @ ChipD:

    If you were to dump the flash mem from the original chip to the chip of, say, an 8 GB USB flash drive, then install that chip in a Wii, Would that mean that the Wii would have about 8 GB of space for channels and such?

  • 39 cap9qd // Jul 28, 2008 at 1:05 pm

    I have a couple of questions.
    > Where did you find the sockets?
    > Did you use a hotair station or a reflow oven to get them soldered?

    I am working on a CPLD NAND interface along with an FTDI chip based programmer and it would be nice to use a socket instead of soldering the thing to a board. Thanks.

  • 40 Newbie // Jul 28, 2008 at 7:15 pm

    I was trying to make dump using YAWND 0.3
    Got following error twice:

    step 2 of 4

    Reading 0x15000 …..
    Error reading flash at 87047 (Error -11)

    Any suggestions?
    I guess, the memory is non-readable at that location for some reason.
    I was wondering what would l happen if I start formatting flush and same block happens to be non-writable ether? Will some wear-leveling mechanism kick in and fix it or I’ll get new kind of bricked Wii?
    I bought it 1 year and couple days ago :-(

  • 41 Newbie // Jul 28, 2008 at 7:53 pm

    From source code:
    res = IOS_Read(flash_fd, block_buffer, flash_block_size);
    -12 is the “bad block”, but what does -11 mean?

  • 42 ChipD // Jul 28, 2008 at 8:57 pm

    @ buntyverma5515

    Im still waiting on a bricked wii to do further testing.

    @ Zim

    If you put any nand larger then 512 the wii would not boot.Every nand has a specific chip ID and the wii only supports samsung and hynix brand 512 nand ID’s.Also there is no support for anything larger then 512, so even if you add support for larger nand ID’s, the wii wouldnt see the extra space.Alot of work needs to be done to accomplish this.

    @ cap9qd

    I got the sockets from http://www.meritec.com
    Item # 980020-48-P1
    And i soldered it in the old fashion way with a 15watt soldering iron and a desoldering braid, and some amazing chip-quik ( i swear by this stuff) Good luck :)

    @ Newbie

    Honestly i dont know what to tell ya, ive never spoke with the author of yawnd, i just tested to see if the dumps it created worked.And ive never had that error.My guess is your nand may have bad blocks, but i wouldnt attempt to use any dumps from yawnd if your getting errors.Instead, if your really set on testing this stuff out, the best option would be dumping via external hardware (infectus..ect) and comparing the dumps.Once you get some dumps that match, your best bet is to get one of the replacment nands i listed on comment #13 and see if it boots.Otherwise you could risk bricking if theres bad blocks because wear leveling/bad block correction isnt supported with infectus+amoxiflash.

  • 43 Newbie // Jul 28, 2008 at 9:54 pm

    Thanks for reply.

    I really hope, bushing or marcan may shed some light on IOS_Read return codes before I jump on Infecuts…

  • 44 buntyverma5515 // Jul 29, 2008 at 6:37 am

    @chipD : thanks for the reply ,but atleast give us some idea by when u would be releasing this ,please

    ok i understand that ur still waiting for the bricked wii ,but may be u can release it partly ,i am tired with my JAP language of my wiii ,may be u can release this first ,I am sorry for sounding desperate but the way things are going in wii’ s scene ,it more kinda talking and ntn doing ,I am sorry if i am sounding rude

  • 45 Zim // Jul 29, 2008 at 8:40 am


    It’s too bad that that wouldn’t work, but I guess it wouldn’t matter anyways. Nintendo announced that they were doing something about the minimal space problem, so instead of spending a bunch of time trying to get the Wii to read 8 GB NAND chips, we only have to wait :)

  • 46 ChipD // Jul 29, 2008 at 10:04 am

    @ buntyverma5515

    Im not in charge of releasing software.I simply test software along with the hardware side of things.And i respect bushings wishes to not release something that he feels isnt ready.

    You have to have patients my friend, all in due time.
    Right now this is a long process and requires an infectus, extra nand chips,you have to be running linux,have to compile code..ect..ect

    Just give it some time and im sure when bushing is ready he will make it alot easier.

  • 47 Newbie // Jul 29, 2008 at 11:20 am

    Just got another crazy idea.
    IMO NAND bad blocks might be handled properly by NAND file system.
    The same true for any other FS: FAT, NTFS, etc.
    The only requirement (obviously!) bad block shouldn’t be in system area.
    Just imaging copying diskette with bad block (BB).
    If you do raw dump you will run into BB.
    If you read file allocation table (FAT) you will know about BB, and you may copy only actual data and skip bad, empty, previously used (left from deleted files) or blocks.

    I do realize, Wii NAND might me more like hard drive than diskette (i.e. has different partition with different file systems).
    And therefore writing a smart backup is not a trivial task. :-(
    Oh, well those are just my thoughts…
    Still waiting for big gurus like bushing or marcan to give me a hint what to try next :-)

    I guess, this is just my problem and it shouldn’t be in this thread.
    Where else I should post it then?

  • 48 ChipD // Jul 29, 2008 at 5:32 pm

    @ Newbie

    I would try asking the redbird, the author of yawnd, he should know what that error is more then anybody.

  • 49 friiwii // Jul 31, 2008 at 2:45 am


    Hallo. First -> great work !

    I’ve got an bricked wii here in front of me. Infectus is allready installed on mainboard. I would like to try unbricking.. its an German PAL Console with Paper Mario Brick 2.1E.. NO keys.. NO backup

    Whats the way to recover.. i would like to do it here. Could you help me unbricking please..

  • 50 ChipD // Aug 1, 2008 at 9:02 pm

    @ friiwii

    Im still in the process of testing unbricking, but hopefully soon.You say you have an infectus installed.You will need to do the D0 trick to halt activity to the nand.I personally havent tried this approach,since i do everything externally, but i think it should work.Once im finished testing, providing everything works well, i will document the process.

  • 51 bob12x // Aug 3, 2008 at 1:03 pm

    Hello ChipD,

    can you help me or give me advise?
    I have this error.

    This message came sudden, I have nothing modified.
    Do I have any chance to unbrick my Wii ??
    Is there any way to modify a nand dump?
    I have no keys. (cpu-key)
    But I have infectus installed and made a backup of my nand flash.

    thx in advance!

  • 52 ChipD // Aug 4, 2008 at 10:05 pm

    @ bob12x
    when are you getting this error? If your trying to dump your nand while the wii is powered on, this is normal because your wii is trying to access the nand while the infectus is trying to read it.You need to short D0 to gnd to halt activity.
    Also this could be caused by interference from crossed wires to the infectus.Even if your infectus isnt connected to your pc, the pins on the nand that the wires are connected to maybe crossed and picking up interference.
    All i could suggest is that you remove the infectus from your wii and try turning on your wii and see if you get the corrupted error again.

    Ive had that same error last year when i first started playing around with the wii nand and infectus, so its common.Try what i suggested and let me know how it goes.

  • 53 bob12x // Aug 5, 2008 at 5:49 am

    @ ChipD
    the error comes up after pressing button A
    I got this message befor installing infectus.
    (Thit was the only reason why I bought infectus)
    I did the D0 trick and dumped the nand.
    I also desoldered the nand and maked a dump, compared both files, they are equal.

    Yesterday I reprogrammed brand new Samsung K9K4G08U0M, to exclude corrupted nand, and still get same error.

    The message says the system files are corrupted.
    Can’t we fix it?

  • 54 ChipD // Aug 6, 2008 at 1:01 am

    @ bob12x

    Well…I know i got that error message a few times.One time it was interference from crossed wires.The second time i got it was probably a bridge between two I/O data pins on the nand, and i think another was when i forgot to connect the bluetooth module.
    So if your saying you got this error before modifying anything, or installing the infectus, im thinking your bluetooth module might be bad.
    I can take a look at it, and pin point the problem.If its the bluetooth module, your kinda screwed.If your nand someone got corrupted i can fix that.

    join #wiidev and PM me, and we can try and trouble shoot it.

  • 55 9562 // Aug 9, 2008 at 10:33 pm


  • 56 9562 // Aug 10, 2008 at 5:18 am

    bluetooth module is not bad
    the error comes up after pressing button A
    my friend have one
    Demolition and equipment
    can be well
    but do that many times

  • 57 maddoc // Dec 13, 2008 at 4:47 pm

    Sorry to bump this old topic, I just messed a wii up – menu 290 with latest IOS30 from nus => full brick.
    I ordered a few TSOP48 sockets and in the mean time i build a flasher for the NAND.
    My concern is if it is possible to dump the flash, decode, put back the good IOS30 v1040, recode the flash and transfer it to the NAND or at least take a YAWND flash from my other wii and change the keys.
    I had the keys saved before the fatal error.
    Hope that you can help me!

  • 58 Wii brick and flash chips | Caesar's // Jan 15, 2009 at 9:17 am

    […] I wasn’t out of luck. I read before the brick about ChipD’s endeavour and was prepared with a nand backup. […]

  • 59 neygamers // Apr 11, 2009 at 11:30 am

    ChipD full Bricked have a wii, I would lend it to you to experience, but Noro in Brazil and not know the procedures for sending, I would like to contact, thank you and sorry for bad English

  • 60 ether2802 // Jun 7, 2009 at 9:01 pm

    Sorry to dump this old entry, but I have a full bricked Wii that just hangs on the HEALTH screen, and never appears the “press A” image, if ChipD is still interested in some testing, I can send you the Wii when I get back home in november, cause I left it on México, and I’m in Canada LOL

  • 61 mcrae // Aug 9, 2010 at 3:22 am

    The best if you give me your address to send the motherboard, to remove nand flash socket and put it to me, are small to work welder. And so to save the Wii. ChipD

You must log in to post a comment.