Fixing error 13 and 21 with EEPROM and C Drive

Discussion in 'Xbox - Hardware mods' started by valbaler1, Apr 13, 2008.

  1. valbaler1

    valbaler1 Guest

    I Softmodded my xbox with mech. Then i got the eeprom and the c drive from it. now i am trying to upgrade to a 160 GB Seagate hard drive.

    I used xboxhdm to make a iso and burned it. Xbox hdm worked and i was able to copy the c drive to my new 160 GB hard drive. I then locked it. When i connect it to my xbox, it freezes at xbox Logo then gives me error 13. Then i tried it with an original game and restarted it. The xbox again freezes at the xbox logo but now it also has the Microsoft logo and then i get error 21.

    I have been looking online and trying things for hours, please someone help me
     
  2. C4RN1

    C4RN1 Regular member

    Joined:
    Feb 14, 2008
    Messages:
    1,212
    Likes Received:
    1
    Trophy Points:
    48
    Is your C: stock or modded and does your new hard drive have cable select enabled on the jumper setting?
     
  3. valbaler1

    valbaler1 Guest

    Thanks but i tried both a stocked hd and a modded hd. they both did not work. I also tried cloning them into the hardrive. The cloning was succesful but it still gave me error 13 and 21
     
  4. DLyon4

    DLyon4 Regular member

    Joined:
    Oct 11, 2007
    Messages:
    132
    Likes Received:
    0
    Trophy Points:
    26
    Okay let me ask you a question, you stated that you used both a stock HDD and a modded HDD. When you say stock, what do you mean? You understand that a softmodded console still requires the matched HDD that is locked with the eeprom code from the eeprom chip on the motherboard. If you put your original HDD back in, what happens? Error 21 means you rebooted or something rebooted you from a previous error. 13 is a dashboard software error, either it's corrupt. or you had an older dashboard and when you made the new HDD, the version was updated somehow. or it's a bad key or anything along those lines. Can you go back to your original state? Start there and redo the HDD upgrade. If you can't, repost with the questions answered above and we'll go from there.
     
  5. valbaler1

    valbaler1 Guest

    thanks, but i found the answer.

    I was doing everything right, but the problem was some of the ide connectors were bentover/damaged. This was causing the error because the xbox could not properly access the disk.
     

Share This Page