thanx for all help recived, but its ok ive managed to sort this out myself and the 360 is alive and well

this is strange as E64, i thought was a BRICKED gdr 3120, as in no power no eject or anything,
anyway i was upgraging to the new 2.4firmware and had the drive in mode b etc ,drive was showing in windows etc, so started to flash which started ok
and made the back up files etc,but stopped before it flashed the drive and only had 4 files in the folder, (should be 5) the now .bin was not there, the error message said drive not in mode b and drive not flashed??
yet when i turn the 360 on it will bring up e64!!! but if i open the tray by hand and power on the 360 then pc it will close the tray its self ,shows up in pc ,even gos into mode b ,but then my pc lags and lags ............any ideas please

           i lent a freinds pc with a cheap motherboard and via chip set and worked a treat , total respect for this
                              donation on its way

cant see that being the case ,as when the drive has powered pulled out or plugged in the 360 restarts

did you have both 360's powered up etc or just the first one (working one) then turned dead drive on ?

nice one, did u use mtkflash to flash etc

  true ive had to update on some games to play them,i thought blazintildadeath was a newbie without abox nxt thing he m/soft pro on xbl,,,lol

   is it possible to hotswap the gdr 3120 drive with an --E64-- message using the samsung drive to fix the gdr 3120 drive