Page 25 of 44 FirstFirst ... 15232425262735 ... LastLast
Results 241 to 250 of 433

Thread: NAND programming- Low Level Brick recovery without bootmii

  1. #241
    New Member erikie's Avatar
    Join Date
    Oct 2009
    Location
    Netherlands
    Posts
    524
    Thanks
    8
    Thanked 170 Times in 141 Posts
    Blog Entries
    2
    Use about 15cm q wire, works like a charm with both hynix and samsung.
    I was able to program both chips in system on the wii. Not necessary anymore as I use tsop48 socket and I always remove the nand.
    Much quicker than soldering the wires to the board and never have a problem with programming like this.
    If you think I helped you please click the little thanks button
    Send me a PM if you have any questions regarding unbricking with infectus mod chip or post a message in here http://www.wiihacks.com/bricked-wii-...installed.html

  2. 1 User Says Thank You erikie For This Useful Post


  3. #242
    New Member erikie's Avatar
    Join Date
    Oct 2009
    Location
    Netherlands
    Posts
    524
    Thanks
    8
    Thanked 170 Times in 141 Posts
    Blog Entries
    2
    Quote Originally Posted by Spzx0 View Post
    This thing annoyed me a lot, so I've done some testing to see if anything changes in various scenarios.
    And indeed it does.
    The Q wire length seems to have A LOT to do with the samsung's (as already pointed out by OP over @gbatemp).
    Too long or too short wire will only return junk.
    Now i get MUCH less data corruption than i previous had. However, i still get data corruption..

    Some of the corruption looks like it can be caused by a bug in the software.
    E.g. If the software is supposed to write: .... 0x87 0x1D 0xC2 0xFF 0x00 ....
    Instead it will write: .... 0x87 0x1D 0xC2 0xFF 0xFF 0x00 ....

    Notice the double 0xFF's that get written.
    This will cause every byte in some areas to be "pushed" one byte ahead, causing corruption.

    Tested with "Infectus NAND Flasher 1.03" and "Xavbox 1.0.0.7 ?".
    Both produce exact same result.

    @ erikie
    It would be nice if you could tell us approx length of the Q wire you use and post some pictures of how you've set stuff up.
    Possible also small details, if any.

    I think it would be very interesting to see if we're able to come up with a simple solution for us people with "unwritable samsung's".
    I tested programming samsung nands in system with xavbox and nand programmer 1.03. It only works with the 1.03 version of the nand programmer. Xavbox cannot program samsung nands. Don't even try it. It only works if you remove the nand.
    I flashed 2 this morning without problems but both hynix and removed from the board.
    If you think I helped you please click the little thanks button
    Send me a PM if you have any questions regarding unbricking with infectus mod chip or post a message in here http://www.wiihacks.com/bricked-wii-...installed.html

  4. #243
    New Member
    Join Date
    Mar 2010
    Posts
    10
    Thanks
    1
    Thanked 0 Times in 0 Posts
    I am also having corruption problems with a Samsung NAND. Extra 0xFF getting written and byte shifting. I'd like to try and narrow down the exact issue here. Could everyone who has had success or failure please report what type of setup they are using.

    Hardware and loader: Infectus 1 or 2, Actel chip A3P060 or A3P125, Loader 0.22, 0.24, 0.28 or 0.32. Programming with Samsung NAND attached to Wii system board or externally in a tsop48 socket.

    Software used: Infectus Programmer, Infectus Nand Flasher 1.03 or Xavbox 1.0.0.7.

    My setup: Infectus 2, Actel A3P125, Loader 0.32. Tried all Infectus Programmer 3.9.X.X series software and after erasing, running a Blank Check reports that 00000800 is not blank. As with Spzx0, Xavbox and Infectus Nand Flasher both produce the exact same result. I have several ground wires going from Infectus to Wii and tried several different lengths for the Q wire.

    I have also tried the Bad Flash trick, which has been used successfully on the Xbox 360, by leaving the Nand attached to the Wii system board, but powering it from an external 3.3v source (Pin V on Infectus). The chip can not be identified using this method. Does anyone have any suggestions to get this to work?

    We can figure this out, I am sure of it. This seems to be a firmware or hardware problem (A3P125 not compatible with Samsung Nand's?) I'm pretty sure I can figure out a way to downgrade the loader firmware on the SiLabs F327. In the datasheet, it details how you can erase the chip, but the Infectus software may refuse to reprogram it if there is some type of authentication it performs before flashing the chip. Also willing to try removing the A3P125 and replacing it with an A3P060.

    If we can get the right people motivated, I am sure someone can crack the Infectus Programmer and rip out the binary code for the loader and actel firmware. I wish the Infectus team would just release their source code, or at least give us an option to downgrade the loader. People are still buying these chips...

    Does anyone know where I could find a compatible Hynix Nand to replace the Samsung? I am willing to try anything at this point.

  5. #244
    New Member erikie's Avatar
    Join Date
    Oct 2009
    Location
    Netherlands
    Posts
    524
    Thanks
    8
    Thanked 170 Times in 141 Posts
    Blog Entries
    2
    use a longer q wire and the nand programmer 1.03. Not xavbox it will not work.
    just experiment a bit. I flashed many samsungs in system before I moved to a stand alone solution
    If you think I helped you please click the little thanks button
    Send me a PM if you have any questions regarding unbricking with infectus mod chip or post a message in here http://www.wiihacks.com/bricked-wii-...installed.html

  6. 1 User Says Thank You erikie For This Useful Post


  7. #245
    New Member
    Join Date
    Mar 2010
    Posts
    10
    Thanks
    1
    Thanked 0 Times in 0 Posts
    Thanks erikie, I will give that a try. What is the loader version and Actel chip on your Infectus?

  8. #246
    Junior Member
    Join Date
    Dec 2009
    Location
    England
    Posts
    1,304
    Thanks
    7
    Thanked 320 Times in 240 Posts
    Blog Entries
    2
    I rigged up a stand alone adapter when I used to use my infectus and it still didnt work with samsung for me, to be honest it was just far too much hassle (im used to have the right tools for the job, which the infectus isnt)

    This is my current programmer:
    Attached Images Attached Images

  9. #247
    Member
    Join Date
    Jan 2009
    Posts
    2,692
    Thanks
    254
    Thanked 396 Times in 369 Posts
    hi erikie, would u mind to show the pic of the tsop48 socket with wiring for ref. it sounds so lovely that i would like to see and get one.....
    thanks much.

  10. #248
    Junior Member
    Join Date
    Dec 2009
    Location
    England
    Posts
    1,304
    Thanks
    7
    Thanked 320 Times in 240 Posts
    Blog Entries
    2
    Quote Originally Posted by neildmd View Post
    I am also having corruption problems with a Samsung NAND. Extra 0xFF getting written and byte shifting. I'd like to try and narrow down the exact issue here. Could everyone who has had success or failure please report what type of setup they are using.

    Hardware and loader: Infectus 1 or 2, Actel chip A3P060 or A3P125, Loader 0.22, 0.24, 0.28 or 0.32. Programming with Samsung NAND attached to Wii system board or externally in a tsop48 socket.

    Software used: Infectus Programmer, Infectus Nand Flasher 1.03 or Xavbox 1.0.0.7.

    My setup: Infectus 2, Actel A3P125, Loader 0.32. Tried all Infectus Programmer 3.9.X.X series software and after erasing, running a Blank Check reports that 00000800 is not blank. As with Spzx0, Xavbox and Infectus Nand Flasher both produce the exact same result. I have several ground wires going from Infectus to Wii and tried several different lengths for the Q wire.

    I have also tried the Bad Flash trick, which has been used successfully on the Xbox 360, by leaving the Nand attached to the Wii system board, but powering it from an external 3.3v source (Pin V on Infectus). The chip can not be identified using this method. Does anyone have any suggestions to get this to work?

    We can figure this out, I am sure of it. This seems to be a firmware or hardware problem (A3P125 not compatible with Samsung Nand's?) I'm pretty sure I can figure out a way to downgrade the loader firmware on the SiLabs F327. In the datasheet, it details how you can erase the chip, but the Infectus software may refuse to reprogram it if there is some type of authentication it performs before flashing the chip. Also willing to try removing the A3P125 and replacing it with an A3P060.

    If we can get the right people motivated, I am sure someone can crack the Infectus Programmer and rip out the binary code for the loader and actel firmware. I wish the Infectus team would just release their source code, or at least give us an option to downgrade the loader. People are still buying these chips...

    Does anyone know where I could find a compatible Hynix Nand to replace the Samsung? I am willing to try anything at this point.
    Ill swap you a hynix for your samsung if you want. As above, I have the right tools to program any chip so it makes no difference to me.

  11. #249
    New Member
    Join Date
    May 2010
    Posts
    13
    Thanks
    4
    Thanked 0 Times in 0 Posts
    After trying everything, including decoupling caps, without success, i finally managed to get somewhere!
    Steps for what i did:
    - Position the infectus chip as close as possible to the NAND, right above a GND point (hole).
    - Use a VERY short and VERY thick GND wire (i used a thick piece of a desoldering wick) and solder it as close as possible between the GND point and the infectus.
    - Use as short as possible wires, excluding the Q wire which MUST be around 15cm (as erikie said).
    - Add additional GND wires to both GND points on the infectus, going to different places on the Wii.

    All of this has actually been pointed out by others already. It must just be done VERY correctly it seems.
    Now i can flash the NAND just fine.
    I also have great success with Xavbox now, however, i only tried read/erase/erase verify/write/compare with 15 + 15 blocks, so i can't be 100% sure that it will work in all cases.
    I did the actual programming with "Infectus NAND Flasher 1.03".

    A big thanks to erikie for the tutorial & tips and a big thanks to you other guys for hints & tips!

    Now bootmii shows up fine and i got the keys, however, since this wii was a full brick (bought used on auction), i have other issues to solve now..

    Thanks again!

  12. #250
    Junior Member
    Join Date
    Dec 2009
    Location
    England
    Posts
    1,304
    Thanks
    7
    Thanked 320 Times in 240 Posts
    Blog Entries
    2
    if you have bootmii installed, just use the nand formatter.

    read the last 3-4 pages on this thread: http://www.wiihacks.com/bricked-wii-...n-here-59.html

    it will ask you 2 questions when you run it, say yes to both (its about keeping the serial number and the settings.txt), then you will have a fresh system with just the disc channel. put in a disk with 4.1 update and let it update and you are done.

  13. 1 User Says Thank You Bad_Ad84 For This Useful Post


Page 25 of 44 FirstFirst ... 15232425262735 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •