ok.  I am excited to try this but I am not sure I understand what is going on here by this diagram.  Can anyone help me understand?  I have the Xecuter CoolRunner so I will have to figure out what to do from that as well.

TX Coolrunner with the debug lights.  I am doing this for a friend and he ordered it and brought all of it to me.  It shows the green light blinking and stuff.  not fast or anything like that but it is blinking.

I have an update.  I am able to make it glitch if I disconnect the fans then let it heat up to the point right before overheating then power it off and back on and it glitches.  sometimes I have to do it several times but I dont know what it is causing it.  I even reflowed it after that with same results.  normal nand image boots fine.  Sometimes while it is hot I have to hit the power button a few times but it glitches hot.  doesn't glitch from a cold boot though.

I am in the same boat with a Zypher board from a Halo3 edition.  I made a discovery yesterday though.  I found that if I leave the fans off and let it heat up to the point before it is about to over heat (Not all the way) and then turn it off and back on it glitches.  so it glitches when it is getting hot and not when it is cold.  I am not sure what is going on.  I am still working on it.  Even when it is getting hot though it is still not a consistent boot for the Glitch but it still could be the temp thing.  Try letting it get really warm and see if it glitches while turning it off and back on.  And if anyone has any ideas what to try next for mine please share.

plscsi isnt laid out very easy and the program is mentioned, but doesnt exactly show how the command was sent.  details on this are a bit low.  I've tried messing with it a bit but I just cant figure it out.  but your right the program is mentioned a few times and so is cdb and a few others.  Thank you though for your help.  Also I just wanted to say thank you to all that are out there working on this.  Your doing a awesome job!

backup the hddss.bin from the 20gb 360 drive so you have it in case you ever want to use it in the 360 again and then pop it in your pc and format it.  it will not work in the 360 again unless you have that hddss.bin that was on it originally.

Anyone?  You can PM it to me if it is more comfortable.

what model and all info does it have on the label?  does anything read differently then the normal lite-on sticker?

I just wanted to add that if you inject a different ss.bin into the drive it might be worth a shot because some people have restored other drive backup images to different drives and it has worked.  For the future I would make sure to backup the ss.bin on a hard drive at least before doing anything to it.  Also a plus that this might work would be if you hook the drive up and it shows like a 60gb drive but with corrupted data then you know it will work with a different ss.bin,  good luck.

I have been reading and see this post but it doesnt say how to send the commands to erase the firmware.  Can anyone give me the details on this?  The post was here:  http://www.xboxhacker.net/index.php?topic=9647.msg65348#msg65348  I have a drive I want to play with (Lots actually) but just cant figure out the erase command.  Wanna help contribute best I can.

As current legit testers test the NXE system they should have recieved an update for avatars on there hard drive.  Has anyone attempted to try and find this update for others to check it out?  I would be willing to test files out on my system to see if we can check out the avatars. 

Your DVD Key is not on your new drive.    You can swap the PCB Board from the old drive to the new one and that would fix your problem.  or you can reflash your new drive using the key from your old drives firmware dump.  PCB Swap would be easier.

ok.. I believe this is really looking like a bug on toolbox4.6, I have tried everything I can think of and checked my connections which before i even started I had hot glued them in place from the original install of the passkey. Everything checked out fine. Passkey support replied to me and said that it should read the firmware from the drive and pass the checksum even with it spoofed and that maybe my sata cord is too long so I tried the short SATA cord from the 360 and I got the same result.

Has anyone took a v79 drive and put it in an older 360 and had to spoof the drive as something else? If so has anyone been able to read the firmware from the v79 drive after spoofing it and open their firmware in toolbox4.6 with it passing checksum? Mine said it failed checksum and then shows it as unsupported firmware when opening in toolbox4.6 but the drive works fine in the 360 just wanted to reflash with iXtreme1.4

I dont want to double post and I am sorry in advance if I am but I think I posted this in the wrong area.  here is the link to my post.

http://www.xboxhacker.net/index.php?topic=9492.0

Well I broke down and got a passkey and all was good but you know how it is. I saw that the v79 drive didnt read all the media as well as my samsung so I decided to swap the drives. Got my ms28 drive in my halo3 edition and went to put my v79 drive in my other 360 but I believe I may have found a bug in Toolbox. I restored the drive back to original firmware then redid the key to match my ther 360 then forgot to reflash back to iXtreme1.4 and I spoofed it to a hitachi v47 drive like my samsung was spoofed to and then after putting it back in my other 360 realized it will only play originals because I did not flash it back to iXtreme1.4 so I hooked it back up to the PC got it back into modeB and loaded Toolbox4.6 and told it to dump the firmware first and it did but came up and said it could not validate the checksum and asked if I want to accept it anyway so I said yes then it asked to open it and I said yes and it came up like it is Unsupported Firmware and would not load it up. Then I decided to load the firmware I had of my v79 up on toolbox and see if I could unspoof it that way. It loaded I told it to flash just the spoof strings and it told me that Verify step failed for sector 3C000 and asks "Do you want to Retry?" and never can do it. I then tried the Restore option but it told me it sees a lot of differences and warns me that flashing to many sectors at once can brick the drive so I did not do it. Please help. Anyone have a clue how I could manually flash the sectors of the v79 drive so it is not spoofed anymore?

how does this one look?  http://www.newegg.com/Product/Product.asp?Item=N82E16822136072    will it work nicely?

thank you.  I guess I didnt look at it right.  I got my 7 sectors of mine backed up to a bin.  Thank you.

I am gonna sound like a big noob i guess but what do I open in Hex Workshop to grab the sectors? Not sure what to get them from. I have done hex editing but just need to know what to open and grab it from. Thanks guys.

UPDATE:  I made my own adapter for power and eject button and have a samsund SDG605 in my PC right now reads everything like a normal DVD Drive and yes there is no point in it because it will not read original or burns in the drive like xbox can but i can test Samsung drives and was a fun little project.  also there was a LG drive in xboxs it was the 8050 drive.  I recently bought the GDR8164B and adapter (http://www.xbox8164adapter.com/) and installed it in my xbox and now I can read anything.  and I mean anything and the drive with the new firmware can also let me extract xbox360 games like the original 360 drive on my PC!  These were my projects I had.   

I was just wondering if anyone has any guides on how to make a Samsung and Thompson and LG original XBOX drives work as PC DVD Roms with power connectors for the pc and everything?