xboxscene.org forums

Author Topic: Dosflash And Benq 6038 Gives E65 Error  (Read 27 times)

SteeleW

  • Archived User
  • Newbie
  • *
  • Posts: 3
Dosflash And Benq 6038 Gives E65 Error
« on: June 25, 2009, 08:32:00 PM »

I followed this tutorial for flashing the Benq VAD6038 firmware: http://forums.xbox-scene.com/index.php?showtopic=627745.

Everything appeared to work perfectly, I was able to extract the original stock firmware ORIG.BIN and save it in several places. The ORIG.BIN file is recognized in JungleFlasher and I can read DVD key and the vendor and firmware type clearly in the program, so it appears that DosFlash read and saved the original firmware properly.

I then followed instructions to use firmtool to combine ixtreme 1.6 firmware with orig.bin to make a hacked firmware and flashed the drive and received "Writing Bank 0...OK!"...etc...etc...etc..."Writing Finished!" with no apparent errors. Then, when I attempted to turn the 360 on, I received the E65 error, and the drive tray will no longer open. Afterwards, I also tried benq ixtreme 1.5 firmware, which also proved unsuccessful. "E65: DVD Drive Error.... DVD Timeout, Wrong firmware, dvd is without f/w chip, etc. This can also be caused by the tray not being fully closed on boot."

So, I erased the firmware on the drive in both DosFlash 1.3 and 1.4 and attempted to reflash using ORIG.BIN to see if I could reverse the error. After successfully erasing I typed "A:\>DosFlash W A000 1 A) 1 4 A:\ORIG.BIN 0", and again DosFlash appeared to write successfully and have no errors. "Writing Finished! DataSum: 0739" However, even after reflashing back to ORIG.BIN I still get the E65 error and the drive tray won't open.

I've tried erasing and flashing using both my VIA 6421 PCI card and my motherboard, which is a VIA KM400 in my Shuttle XPC: Shuttle SK43G. At this point I'm pretty confused about the problem and any help would be greatly appreciated. I'm new to this so please try to keep it simple for me.

This post has been edited by SteeleW: Jun 26 2009, 03:36 AM
Logged

vb_encryption_vb

  • Archived User
  • Hero Member
  • *
  • Posts: 1082
Dosflash And Benq 6038 Gives E65 Error
« Reply #1 on: June 25, 2009, 08:40:00 PM »

Personally I would have used jungleflasher for the whole process. Benq's take less then a minute from start to finish with jungleflasher....

So my advice to the situation would be download the latest jungleflasher and the tutorial as well. Read it learn it, and happy flashing.

Logged

SteeleW

  • Archived User
  • Newbie
  • *
  • Posts: 3
Dosflash And Benq 6038 Gives E65 Error
« Reply #2 on: June 25, 2009, 09:26:00 PM »

Thanks for the instant response, I'm downloading SP3 right now because XP freezes whenever i start my 360 and other forums said I needed SP3 to correct.
Logged

SteeleW

  • Archived User
  • Newbie
  • *
  • Posts: 3
Dosflash And Benq 6038 Gives E65 Error
« Reply #3 on: June 26, 2009, 12:53:00 AM »

QUOTE(vb_encryption_vb @ Jun 25 2009, 06:40 PM) *

Personally I would have used jungleflasher for the whole process. Benq's take less then a minute from start to finish with jungleflasher....

So my advice to the situation would be download the latest jungleflasher and the tutorial as well. Read it learn it, and happy flashing.


It wasn't that I was missing SP3, I just had to delete the VIA drivers to get jungleflasher to see the VIA ports and now Windows doesn't shut off when I turn the 360 on. However, I selected the correct I/O Port (0xA000) and under vendor it still says "No Drive Detected". Benq UnLock also fails. Any ideas?
Logged

RedFarmer

  • Archived User
  • Newbie
  • *
  • Posts: 35
Dosflash And Benq 6038 Gives E65 Error
« Reply #4 on: June 26, 2009, 05:20:00 AM »

Did you install PortIO32?
Logged

jgsieve

  • Archived User
  • Jr. Member
  • *
  • Posts: 79
Dosflash And Benq 6038 Gives E65 Error
« Reply #5 on: June 26, 2009, 02:50:00 PM »

don't listen to them. use dosflash. it's easy and you don't have to mess with porti/o BS. get a fresh copy of iXtreme1.6 for benq again. I would bet money that there is something going on with your ix1.6 firmware. re-create firmware and give it another go.
Logged