Print

[eyric101]

humpadilly had mentioned that he was able to rig a switch by shorting a couple points on the eject switch.  He mentioned that he would drop some photos of these points on me next time he opened his box.  If those points could be traced back, and i guess voltage monitored as well, then it seems that might be a good head start.

 

I think one problem is that there are so many ways to brick your drive, that focusing on one perticular way gets lost when people post about this problem or that problem.  They all result in non working eject buttons, but surely caused by very different situations.

[tomy12345]

I did the same mistake, i was watching the connector backwards and shorted pins 1-8. I have to tell you that your drive is dead, when you shorted those two pins you killed the motor in charge of ejecting the tray, i read this on a post in the "Technical DVD-ROM and Modified DVD Firmware Forum" by a guy that did the same, so i run as fast as i could to Walmart and said my Xbox360 just stop working   they couldn't exchange the console so they gave me a refund.

[eyric101]

QUOTE(tomy12345 @ Aug 30 2006, 10:12 AM)

I did the same mistake, i was watching the connector backwards and shorted pins 1-8. I have to tell you that your drive is dead, when you shorted those two pins you killed the motor in charge of ejecting the tray, i read this on a post in the "Technical DVD-ROM and Modified DVD Firmware Forum" by a guy that did the same, so i run as fast as i could to Walmart and said my Xbox360 just stop working they couldn't exchange the console so they gave me a refund.

 

The motor is absolutly not the problem.  That is evident when you start it in modeb, the motor works just fine.  Also, when it is attached to the PC, using the pc's eject commands cause the drive to eject and load just fine.  This is 100 percent not a motor problem.  Now I have read that the 360 uses a 'pulse' method.  using a 3.6 volt pulse to eject the drive, and a 0 volt to load.  I am not 100 percent sure of those values.

[caster420]

Ok, i have done a few preliminary tests, both of which lead me to one conclusion.  Here is what i currently have:

 

Drive A:  47DH, Oct. '05 - presumed broken

Drive B:  47DJ, Nov. '05 - replacement

 

Test 1:  Swap main control boards between drives....

 

    This results in both drives giving the open, close, reading error, no drive status, does not read disc in either drive.  This leads me to conclude that it is not the main board.

 

Test 2:  Boot with tray open, using both power and eject button.... (both with boards swaped and back in original)

 

    Both drives, whether using the original board or the swaped board, close the tray when booting, no matter if power or eject is used.  This leads me to believe that the tray motor works, the eject board is not fried (as suggested) and that the 360 can obviously send the signals fine.

 

These two simple tests lead me to believe that it is not the drives themselves and it must be something on the motherboard itself.  I will work on doing some more tests here shortly.  I thought i would do these simple tests before starting to check the boards themselves, try to give myself a definite starting point.  If anyone has some insight, please let me know.

 

Caster.

[caster420]

Ok, slightly different iteration of test #2.

On drive B with drive A's main board and the tray open, it will boot and load the game or disc in non-modeB mode.  I can also cycle from the main menu to select reading (instead of opening or closing) and it will load the game/movie.

With drive A with drive A's or B's board and the tray open, it will not load at boot or manually from the menu.


Caster.

[caster420]

Drive A's board, which is flashed with garyopa v2.1's fw, will load media and music just fine when starting with the tray open.  I can also manually select read from the menu to launch it.  Authentic 360 games will not boot and give me the error "Please insert this game into a 360 console", or something along those lines.  When i restore the fw to original, the drive has no function at all again.  It will not close the tray on boot and the center led flashes like it is going into modeB but doesnt have modeB functions (tested).  I get this response with the board in either drives.

Caster.