xboxscene.org forums

Author Topic: Dg-16d2s 1.91->2.0 / Dosflash 2.0 No Vendor Mode  (Read 75 times)

Oldxbox

  • Archived User
  • Newbie
  • *
  • Posts: 8
Dg-16d2s 1.91->2.0 / Dosflash 2.0 No Vendor Mode
« on: October 17, 2011, 11:08:00 AM »

Hmmmm, 60 views, no idea?  sad.gif
Logged

BoNg420

  • Archived User
  • Hero Member
  • *
  • Posts: 3403
Dg-16d2s 1.91->2.0 / Dosflash 2.0 No Vendor Mode
« Reply #1 on: October 17, 2011, 11:35:00 AM »

Did you erase the drive first?

PS

Make sure you have your orig.bin and key before doing so



Logged

dougiegillam

  • Archived User
  • Full Member
  • *
  • Posts: 112
Dg-16d2s 1.91->2.0 / Dosflash 2.0 No Vendor Mode
« Reply #2 on: October 23, 2011, 05:26:00 AM »

QUOTE(Oldxbox @ Oct 22 2011, 02:30 PM) View Post

Hello,

I've done nothing since dosflash 2.0 cannot make it enter vendor mode, so no erase.

Did you flash it to 1.91 in the first place? Just confirming your hardware is setup correctly.Have you tried doing it in Jungleflasher? A description of your hardware setup would be useful and why are you using Dosflash? Also have you tried putting the drive back in the 360 to check its still working?
Logged

death69inc

  • Archived User
  • Full Member
  • *
  • Posts: 185
Dg-16d2s 1.91->2.0 / Dosflash 2.0 No Vendor Mode
« Reply #3 on: October 23, 2011, 07:58:00 PM »

do you have your orig dump

if so use jf and see is liteon erase puts in vendor mode

if you dont i woudl still try jf to get the key

I was a dosflash lover till my old workhorse xp system died now jf all the way

I am thinking of trying it to get a mx slim board back to life after jf locked up during a flash now wont intro shakes head
Logged

tgnix

  • Archived User
  • Newbie
  • *
  • Posts: 8
Dg-16d2s 1.91->2.0 / Dosflash 2.0 No Vendor Mode
« Reply #4 on: October 24, 2011, 05:57:00 PM »

QUOTE(Oldxbox @ Oct 24 2011, 11:28 AM) View Post

Hello,

Yes, the drive is currently on 1.91 and still works fine in the console since I did nothing at the moment.
I also tried JF, with the same result, no vendor mode, and JF is not stable under my new Win7 x64 setup, BTW if I disable the VIA driver, JF does not see the card, and if I enable it, it is unstable and freezes.

I also had good and easy success with dosflash 2.0 and my Benq drive.

Thanks.


I had a similar problem updating my liteon drive thought i'd bricked it.

I usually use dos to erase/flash the liteon drive, but my computer wouldnt recognise the drive on my sata cable.

To fix the problem i connected an old hitachi drive to the sata cable 09E0 and switched on with CK3, booted up iprep with hitachi switched on from the startup.  This will recognise now that your hitachi drive is connected.  Switch off hitachi drive using CK3 disconnect sata cable and ck3, plug in liteon, switch liteon on and do l-o-eras commands as normal.

If your having a similar problem to me which sounds about the same, then this should work.
Mine messed up because i tried to flash to the drive twice but only done l-o-eras for the first flash, so got stuck inbetween normal mode and vendor mode i think, then pc wouldnt recognise that the drive was there coz firmware was locked out.

hope this helps.
Logged

Oldxbox

  • Archived User
  • Newbie
  • *
  • Posts: 8
Dg-16d2s 1.91->2.0 / Dosflash 2.0 No Vendor Mode
« Reply #5 on: October 27, 2011, 09:23:00 AM »

Hello,

In fact I just had to force erase of the drive from dosflash without the flash being recognized at first... (command "LITEON E"). Once erased, restarted dosflash then the eeprom was recognized, and successful 2.0 flash...
I thought the eprom had to be recognized by dosflash before being able to erase it (works like this with the Benq).
Thanks to all for your suggestions.
Logged

tgnix

  • Archived User
  • Newbie
  • *
  • Posts: 8
Dg-16d2s 1.91->2.0 / Dosflash 2.0 No Vendor Mode
« Reply #6 on: October 27, 2011, 10:03:00 PM »

QUOTE(Oldxbox @ Oct 27 2011, 04:23 PM) View Post

Hello,

In fact I just had to force erase of the drive from dosflash without the flash being recognized at first... (command "LITEON E"). Once erased, restarted dosflash then the eeprom was recognized, and successful 2.0 flash...
I thought the eprom had to be recognized by dosflash before being able to erase it (works like this with the Benq).
Thanks to all for your suggestions.


glad ya sorted it tongue.gif
Logged