Page 14 of 17 FirstFirst ... 41213141516 ... LastLast
Results 131 to 140 of 169

Thread: Infectus Nand Flashing Guide

  1. #131
    New Member
    Join Date
    Mar 2011
    Posts
    15
    Thanks
    0
    Thanked 1 Time in 1 Post
    I just received Infectus 2.

    Before proceeding to soldering and folow the tutorial, i whant to make sure if i understand correctly, as programing onboard is not so well documented, only Jordan5 has written some steps on page 11.

    Pin DATA 0 from NAND need to be connected to GND of console for 1 sec after powering the WII and then connected to Infectus, right? If keeping D0 to GND for 2-3 sec i guess there is nothing wrong, i just need to try a few more times to mach the timing to block Hollywood preccessor to acces the nand and to recognize the nand in Xavbox.

    Also i have observe that t 5v and GND from Infectus are solder to wii motherboard.

    Dosen't Infectus power up from USB?

    Thanks in advance.
    Last edited by zyx1141; 04-13-2011 at 01:29 PM.

  2. #132
    Junior Member streamlinehd's Avatar
    Join Date
    Mar 2010
    Location
    East Coast, USA
    Posts
    1,369
    Thanks
    114
    Thanked 557 Times in 377 Posts
    Blog Entries
    3
    You have to short D0 to ground before you power on the Wii. Once the Wii is powered on you can then connect D0 to Infectus. The use of a momentary switch will make this process a little easier. When programming on-board you need to make the 5V connections to Infectus as the power supplied by USB isn't good enough to get the job done.
    Cogita ante salis
    If you're happy with the help I provided, don't forget to hit my thanks button


  3. #133
    New Member
    Join Date
    Mar 2011
    Posts
    15
    Thanks
    0
    Thanked 1 Time in 1 Post

    Flashing Smasung nand - onboard

    Thanks for explanations, but the issues where somewhere elsewhere.

    After soldering the nand to Infectus, tried to recognized with Xval triggering D0 to GND but keep getting "Fabricant inconnu/ Type inconnu".
    Tried without triggering D0 to GND and the nand is detect in Xval.

    Do the test with read, and when write, every first block that has to be written gives different block warning and display instantly Finished! ( tried with different address)

    After google it a little bit more it came with a solution.
    Samsung nand's are a bit fussy when programing onboard and there is needed an extra 3.3V power up to Infectus.

    After soldering 3.3V to Infectus writing came without problems.
    It took about 3 hours to write full nand 512. Also, received many, many different bloks, as the nand image was done right after i installed bootmii and IOSses where changed.
    Also i haven't trigger D0 to GND as Jordan5 said.

    The diagram to solder to 3.3V is the folowing
    http://img7.hostingpics.net/pics/84607img4025m.jpg

    Firs power up where also a black screen, but after installing wireless module it booted to menu. Hopefully this time wouldn't hang up on Priiload installation, or i'll give up on it.

    @streamlinehd, Bad_Ad84
    Thanks for reply, keep it going.


    LE:
    @streamlinehd
    Actually is not my soldering, the indication can be found here
    Mine is a little bulky, i haven't tried to make it art in 40 min.
    It would have been easier to do it externally but, I don't have an TSOP48 adapter handy around...
    Last edited by zyx1141; 04-15-2011 at 10:52 AM.

  4. #134
    Junior Member streamlinehd's Avatar
    Join Date
    Mar 2010
    Location
    East Coast, USA
    Posts
    1,369
    Thanks
    114
    Thanked 557 Times in 377 Posts
    Blog Entries
    3
    Man, very nice soldering job . I'm glad to hear you were able to get it working and yes Samsung chips are very difficult to program on-board. I've never been successful at programing Samsung chips that way. Then again, I've done just about all of my flashing externally. Thanks for the additional info and hopefully your trick helps others stuck in the same position.
    Last edited by streamlinehd; 04-15-2011 at 09:01 AM.
    Cogita ante salis
    If you're happy with the help I provided, don't forget to hit my thanks button


  5. #135
    Junior Member
    Join Date
    Dec 2009
    Location
    England
    Posts
    1,304
    Thanks
    7
    Thanked 320 Times in 240 Posts
    Blog Entries
    2
    <Insert rant about infectus here>


  6. #136
    Junior Member streamlinehd's Avatar
    Join Date
    Mar 2010
    Location
    East Coast, USA
    Posts
    1,369
    Thanks
    114
    Thanked 557 Times in 377 Posts
    Blog Entries
    3
    Quote Originally Posted by Bad_Ad84 View Post
    <Insert rant about infectus here>

    How'd you do that? I saw your rant command and your entire Infectus rant popped into my head. Now how do I make it stop
    Last edited by streamlinehd; 04-15-2011 at 03:41 PM.
    Cogita ante salis
    If you're happy with the help I provided, don't forget to hit my thanks button


  7. #137
    New Member
    Join Date
    Dec 2010
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Hey lads,

    Having a few issues writing to my chip in the tsop, reading seems to be ok though, here's what I get when I try to eraise the first 10 blocks.












    with the debug log file here in french.

    At first I thought the chip was bad, and so I got another chip, but having the same result!

    I've checked, rechecked and done more checking, wires are in the correct locations and the connections are good, I've reseated the chip loads of times, it's clean etc..

    I'm working from win7 64bit, does'nt seem to be a driver issues, I'm guessing it might be a wire issue, do I need 2 gnd's and 2 v's instead of just 1? I have the 2 connected at current, but might try removing the second on pin's 36,37.

    Any other pointers would be helpfull!

  8. #138
    New Member
    Join Date
    Dec 2010
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts
    ok,

    Disconnected pins 36 and 37, leaving pins 12 and 13 connected instead, and got the following when trying to do the erase, same erros but different locations!



    Any ideas?

  9. #139
    Junior Member streamlinehd's Avatar
    Join Date
    Mar 2010
    Location
    East Coast, USA
    Posts
    1,369
    Thanks
    114
    Thanked 557 Times in 377 Posts
    Blog Entries
    3
    You need voltage and ground connections on both sides of the NAND V = 12, 37 Ground = 13, 36. I don't understand why you want to delete anything? This guide doesn't tell you to do that and there's really no point. Use the update and compare option to write to the chip and make sure that function works first by writing to a test area in the high block range 4080 - 4095. If you can't write to the chip then you can't continue flashing until you figure out and fix the problem.
    Cogita ante salis
    If you're happy with the help I provided, don't forget to hit my thanks button


  10. #140
    New Member
    Join Date
    Dec 2010
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Hey, thanks for the reply. I was just testing with the erase to make sure I was able to complately wipe the chip, looking at the data in a hex editor is would be easier to notice as they should all have the same value.

    After rewiring 2 times, I finally found the issue, it was the infections2 unit itself!! Some of the pines on the large chip were connecting to each other, after poring some flux onto them and running the soldering gun along them its cleaned them up and I'm now able to read/write, well kinda.

    I' getting a bad update on black 477, and then it drops out, I can remember someone else having an issue like that and they bypassed the block and started the updating after the block that was giving them the issue.

    What I'd like to do now is find out how large a block is, in terms of offset, so I can edit the nand.bin backup I have to start at block 478, check the Relative offset and continue with the programming, and then I can come back to the blocks that have errors and work on them.

    On a side note, when I did the nand dump with bootmii I did have 1 maybe 2 bad blocks, but the tutorial said it was ok, could this be the cause or should it just write the bad blocks back to the chip?

    Cheers.

Page 14 of 17 FirstFirst ... 41213141516 ... 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
  •