Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: infectus issue

  1. #11
    New Member
    Join Date
    Dec 2009
    Posts
    11
    Thanks
    0
    Thanked 0 Times in 0 Posts
    with XAVPROG??

    anyone?? i need a guide please for dont kill the wii more XD
    Last edited by nightstah; 10-31-2010 at 09:16 AM. Reason: Use The "Edit" Button --- There For a Reason

  2. #12
    Senior Member
    WiiHacks Staff
    Forum Administrator
    Only Site Donators Can PM Staff
    nightstah's Avatar
    Join Date
    Nov 2009
    Location
    Repatriated to WH
    Posts
    18,449
    Thanks
    1,837
    Thanked 4,307 Times in 3,617 Posts
    Blog Entries
    5
    Quote Originally Posted by shinjipsx View Post
    with XAVPROG??

    anyone?? i need a guide please for dont kill the wii more XD
    http://www.wiihacks.com/bricked-wii-...t-bootmii.html

    http://www.wiihacks.com/bricked-wii-...-tutorial.html

    Be aware, the latter-most user has an intolerance for... ineptness if you make a query within his thread.

  3. #13
    New Member
    Join Date
    Dec 2009
    Posts
    11
    Thanks
    0
    Thanked 0 Times in 0 Posts
    sorry, not happen again, was my mistake.

    now read the guidelines for the NAND flash boot

    thanks


    EDIT:
    i have a problem, i take the nand to a hex editor, and from offset 0 to 135152 I get this

    FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB

    from 135168 is fine. i dont wanna do something more wrong and if someone can edit my nand please i would be grateful, i can send you the link with the nand..
    Last edited by shinjipsx; 10-31-2010 at 10:29 AM.

  4. #14
    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
    i have a problem, i take the nand to a hex editor, and from offset 0 to 135152 I get this

    FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB
    This happens when you have a bad connection, short or a bad ground. Check all your connections and make sure everything is connected from the Infectus to the NAND properly.

    i dont wanna do something more wrong and if someone can edit my nand please i would be grateful, i can send you the link with the nand..
    Having someone edit your NAND file for you will do you no good since you can't properly transfer the data.
    Last edited by streamlinehd; 10-31-2010 at 11:34 AM.
    Cogita ante salis
    If you're happy with the help I provided, don't forget to hit my thanks button


  5. #15
    Junior Member
    Join Date
    Dec 2009
    Location
    England
    Posts
    1,304
    Thanks
    7
    Thanked 320 Times in 240 Posts
    Blog Entries
    2
    Why would you edit the NAND? Just load the bootblock and then press compare and update, this will erase and program what ever blocks are needed... I.e the first ones. It's quick and leaves all the other data on there

  6. #16
    New Member
    Join Date
    Dec 2009
    Posts
    11
    Thanks
    0
    Thanked 0 Times in 0 Posts
    everithing is good conected, maybe the boot1 is wrongh after too flashing or a bad flashing, but if i edit the boot1 in the hex editor and write that on the wii ??

  7. #17
    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 shinjipsx View Post
    everithing is good conected, maybe the boot1 is wrongh after too flashing or a bad flashing, but if i edit the boot1 in the hex editor and write that on the wii ??
    I'm assuming you all ready flashed the boot blocks with the files Bad_Ad provided you with correct?

    Use Xavbox to read blocks 0-7 only and open the output with your hex editor. The data should match the boot blocks you used to flash with exactly. If there's a change or if the data is all FB then you're getting data corruption for some reason. The data isn't being written to the NAND correctly.
    Last edited by streamlinehd; 10-31-2010 at 11:49 AM.
    Cogita ante salis
    If you're happy with the help I provided, don't forget to hit my thanks button


  8. #18
    Junior Member
    Join Date
    Dec 2009
    Location
    England
    Posts
    1,304
    Thanks
    7
    Thanked 320 Times in 240 Posts
    Blog Entries
    2
    He has already written to the NAND, that's probably why the first blocks look corrupt but the rest looks ok. First write was bad, that's probably why 1b didnt work as I'm pretty sure that's not a 1a wii

  9. #19
    New Member
    Join Date
    Dec 2009
    Posts
    11
    Thanks
    0
    Thanked 0 Times in 0 Posts
    hi again. i have other problem, i try to dump the nand again and the infectus nand flasher show me this



    im going to reprogram the infectus to nand flasher again and look whats happen..

  10. #20
    Junior Member
    Join Date
    Dec 2009
    Location
    England
    Posts
    1,304
    Thanks
    7
    Thanked 320 Times in 240 Posts
    Blog Entries
    2
    Like you have already been told, you have bad connections.

    Its ground bounce and AGAIN its covered in the threads you have been linked to.


    This is why I dont think we should have infectus tutorials, it makes it look a lot easier than it is and we have people who arent capable of doing the work attempting it.

Page 2 of 2 FirstFirst 12

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
  •