Lite-on Write verify failed! Now it only returns Drive Status 0x80 and FF80 in DOS

Discussion in 'Xbox 360 - Modding & Hacking' started by mshockey, Feb 3, 2010.

  1. mshockey

    mshockey Member

    Joined:
    Jun 20, 2007
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    16
    I've been doing this for a long time now and I know my way around. I have flashed 50+ 360's and many of those were lite-ons. This particular one is a lite-on 74850c. This is someone elses code but this is exactly what I got:

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~~~~~~~~

    JungleFlasher 0.1.55 Beta

    Session Started Tue Mar 24 21:26:11 2009




    This is a 32 bit process running on 2 x 32 bit CPUs

    Found 1 I/O Ports.

    Found 1 Com Ports.

    Found 6 windows drives.

    Found 1 CD/DVD drives.



    Sending iXtreme DVDkey request to port 0xA000



    Extracted drive key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



    iXtreme v1.50-12x-



    Key data saved to C:\Documents and Settings\Riseabove\Dokumenter\iextreme\Key.bin



    0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS

    0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S

    0020: 37 34 38 35 30 43 41 30 - 41 31 44 36 30 38 43 47 74850CA0A1D608CG

    0030: 38 33 33 39 30 37 30 31 - 30 46 30 20 20 20 00 00 833907010F0 ..

    0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

    0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................



    Inquiry String saved to C:\Documents and Settings\Riseabove\Dokumenter\iextreme\Inquiry.bin



    0000: C0 85 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

    0010: 00 00 00 00 44 36 30 38 - 43 47 38 33 33 39 30 37 ....D608CG833907

    0020: 30 31 30 46 30 20 20 20 - 00 00 00 00 00 00 34 37 010F0 ......47

    0030: 35 38 43 30 20 20 4C 50 - 53 44 20 20 20 20 47 44 58C0 LPSD GD

    0040: 31 2D 44 36 53 32 20 20 - 20 20 20 20 20 20 20 20 1-D6S2

    0050: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 00 00 ..

    0060: 00 00 00 0B 00 00 00 04 - 00 02 06 00 00 00 00 00 ................

    0070: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

    0080: 03 00 78 00 78 00 E3 00 - 78 00 00 00 00 00 00 00 ..x.x...x.......

    0090: 00 00 00 00 00 00 00 00 - 02 02 00 00 68 00 40 00 ............h.@.

    00A0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

    00B0: 20 20 00 00 ..



    Identify String saved to C:\Documents and Settings\Riseabove\Dokumenter\iextreme\Identify.bin



    0000: 44 36 30 38 43 47 38 33 - 33 39 30 37 30 31 30 46 D608CG833907010F

    0010: 30 20 20 20 FF FF FF FF - 38 47 33 31 30 37 35 30 0 ....8G310750

    0020: 31 37 45 34 31 34 58 58 - 41 30 FF FF 00 00 05 0A 17E414XXA0......

    0030: 38 31 34 30 30 30 30 30 - 31 31 34 34 34 33 00 00 81400000114443..

    0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..





    Dummy.bin file saved to C:\Documents and Settings\Riseabove\Dokumenter\iextreme\Dummy.bin



    Loading DVDkey source file

    Inquiry string found

    Identify string found

    DVD key found @ 0xA030 key is xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

    Firmware is a Lite-On Dummy OSIG: PLDS DG-16D2S 7485

    Firmware type is: iXtreme v1.50-12x-



    Auto-Loading target file C:\JungleFlasher v0.1.55 Beta\firmware\ix151-liteon.bin

    Target File MD5 hash is: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

    Genuine Lite-On iXtreme 1.51

    Inquiry area found

    Current DVD key is 55AA55AA55AA55AA55AA55AA55AA55AA

    Firmware is a Lite-On encrypted iXtreme OSIG: PLDS DG-16D2S 7485

    Firmware type is: iXtreme v1.51-12X

    DVD Key copied to target

    Inquiry strings identical

    Identify string copied from Source to Target

    Serial strings copied from Source to Target



    Target f/w saved as: C:\Documents and Settings\Riseabove\Dokumenter\iextreme\fw\Lite_CFW.bin



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x50

    ....................

    Device Intro failed!



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x0

    ......

    Serial flash found with Status 0x72

    Sending Vendor Outro to port 0xA000

    Manufacturer ID: 0xC2

    Device ID: 0x11

    Flash Name: MXIC(MX25L2005)

    Flash Size: 262144 bytes



    Getting Status from port 0xA000

    SPi flash found with Status 0x72



    Sending Chip Erase to Port 0xA000

    Writing target buffer to flash

    Writing Bank 0: ................

    Writing Bank 1: ...............

    Flash Verification Test !

    Reading Bank 0: ................

    Reading Bank 1: ................

    Reading Bank 2: ................

    Reading Bank 3: ................

    Write Verify Failed !



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x0

    ....

    Serial flash found with Status 0x72

    Sending Vendor Outro to port 0xA000

    Manufacturer ID: 0xC2

    Device ID: 0x11

    Flash Name: MXIC(MX25L2005)

    Flash Size: 262144 bytes



    Getting Status from port 0xA000

    SPi flash found with Status 0x72



    Sending Chip Erase to Port 0xA000

    Writing target buffer to flash

    Writing Bank 0: ................

    Writing Bank 1: ................

    Writing Bank 2: ................

    Writing Bank 3: .......

    Flash Verification Test !

    Reading Bank 0: ................

    Reading Bank 1: ................

    Reading Bank 2: ................

    Reading Bank 3: ................

    Write Verify Failed !



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x80

    ....................

    Device Intro failed!



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x80

    ....................

    Device Intro failed!



    Getting Status from port 0xA000

    Invalid Status 0x80



    Getting Status from port 0xA000

    Invalid Status 0x80



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x80

    ....................

    Device Intro failed!



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x80

    ....................

    Device Intro failed!



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x80

    ....................

    Device Intro failed!



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x80

    ....................

    Device Intro failed!

    Sending Vendor Intro to port 0xA000

    Status 0x80

    Re-sending Vendor Intro:

    ......................................

    Device Intro failed!

    Sending Vendor Intro to port 0xA000

    Status 0x80

    Re-sending Vendor Intro:

    ......................................

    Device Intro failed!



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x80

    ....................

    Device Intro failed!



    Sending Lite-On-Erase request to port 0xA000

    ..............

    Drive returned Status 0x80

    ....................

    Device Intro failed!

    I have since tried everything I could think of. I have tried using DOS with L-O-ERAS and I only get status FF80. I have ran dosflash but it reports "No ATAPI devices found". I have tried cycling the power to the drive at numerous different times to no avail. The drive does not respond to the connectivity kit ejection button (as is expected) but I have been opening the drive manually and leaving it half opened during the procedures. I have also tried using Lite-On-Erase in Windows. I have tried to resend the intro and power the drive off/on quickly, as JF requests, but all it does is return a continuous row of dots. I am running Windows XP 32 bit. I have a VIA 6421 sata chipset with the drivers uninstalled. This setup has worked for all other systems in the past. I am open to any ideas. Any help would be much appreciated.

    Cheers
     
  2. mshockey

    mshockey Member

    Joined:
    Jun 20, 2007
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    16
    I was using JF 1.67 and I was going from Ixtreme 1.60 to Ixtreme LT.
     
  3. Mik3h

    Mik3h Regular member

    Joined:
    Oct 18, 2004
    Messages:
    2,847
    Likes Received:
    0
    Trophy Points:
    46
  4. rlils

    rlils Member

    Joined:
    Dec 13, 2007
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    11
    I have the same problem with one of my liteon's... tried JF, Dosflash, Dosflash32, Iprep... all to no ends. I receive the same No ATAPI Devices found...or FF80, 0x80, tried l-o-eras and port number, everything I could find here and other forums...

    I have since given up..... I have pretty much the same setup as you, and have the latest JF, etc.

    I will keep a look at this post to see if u happen to find a cure.

    Best of Luck.
     
  5. xnifex

    xnifex Member

    Joined:
    Apr 25, 2008
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    11
    try changing which port on your SATA card you're using. Use the one in the back of the card. I flashed my drive the other night & it failed on Write & afterwards it wouldn't see the drive anymore. I remembered reading somewhere to switch to the back port on the SATA card & when i did that it recognized the drive instantly & flashed with no issues.

    Hope that helps.
     
  6. mshockey

    mshockey Member

    Joined:
    Jun 20, 2007
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    16
    Ya, I noticed that I was using the wrong one after I had the problem. I tried to use the v1.7 immediately afterwards but still got the same thing. It might just have been too late.

    I have also tried using the back port of the VIA card. It doesn't seem to even recognize the drive now. I just get a status FF with continuous dots when I send the Intro.
     
  7. xnifex

    xnifex Member

    Joined:
    Apr 25, 2008
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    11
    walk away from it, try again tomorrow. For some reason that works too
     
  8. lenselije

    lenselije Member

    Joined:
    Jan 16, 2010
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    11
    read the jungleflasher.pdf file, it has a fix for your problem :)
     
  9. mshockey

    mshockey Member

    Joined:
    Jun 20, 2007
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    16
    Thank you for the response. I've read through the pdf file but haven't found what you're referring to. Could you specify which part you were referring to? I am eager to see what I've done wrong and I have a few other people who are experiencing this same problem and are hoping for a solution. Thanks in advance.
     
  10. mshockey

    mshockey Member

    Joined:
    Jun 20, 2007
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    16
    Well, I've now successfully flashed a different Lite-On drive using the same setup as I was trying to use to flash this one. I can now say that, whatever is wrong, it is with the drive and not the way I am doing it. I know that every drive is different, but I have honestly tried everything I could think of. I am posting a video on youtube that shows my numerous failed attempts to get this to work. The solution is: If you were able to get the key off the drive then just get another drive for $20 and spoof it into your system. It appears that the drive is bricked.
     
  11. Mik3h

    Mik3h Regular member

    Joined:
    Oct 18, 2004
    Messages:
    2,847
    Likes Received:
    0
    Trophy Points:
    46
    Unless you plan on going live, because doing that will get you banned.
     
  12. mikeismad

    mikeismad Regular member

    Joined:
    Feb 19, 2007
    Messages:
    2,426
    Likes Received:
    0
    Trophy Points:
    46
    If your drive is on 0xA000 why did you pull the key from a different port?

    Also, it's a lite-on, it can't be bricked, just keep trying and it will erase itself.
     

Share This Page