Print

[Zell-]

after killing about 10 DVD-DL tring to get the system to work, I decied to re-flash my FW with xtreme.bin again, after doing this the box then booted with an error 65 I didnt panic at the time becuase i have had this problem in the past but this time was different this when I powered back up the drive just died on me and stoped responding.


the unit still boots and I have a copy of my orig.bin, is there an ideas about how to get this drive running again? my only option at this point is to buy another unit, quite upseting ive had to struggle thought this whole guide with problems at every turn only for this to happen right when I was so close to finishing.  

thanks

M

[Zell-]

someone mentioned a hotswap method, power on with another drive so it detects in BIOS & then do a hotswap with another drive and then re-flash, think this will work?

M

[Zell-]

YES! the hotswap method works!!! Had to buy another box to do it, least my room mate will buy it off me.

thank you Jesus, ala, budda...whatever I love you all

 

[easyguy]

i dont think any hotswap is necessary.
just let ur pc boot normally even if it's not detected.
then issue the write command and it will still be flashed.
at least that's what i did

[uknowme3]

Ok guys I'm feeling pretty crap right now. ok I'll start from the beginning....Well I managed to open and connect the XBOX360 Samsung DVD to my computer and got it to boot up using the bootable floppy drive with no other IDE devices attached. So basically just a 3 1/2 inch floppy drive and the Samsung drive itself. Now I tried using the following command line to execute the read "mktflash r /m orig.bin" but it did not work. So i looked at the other switches and found one that seemed to work just fine and that was "mtkflash r /sata orig.bin".

Now after making the backup I went back into windows and  saved it onto my desktop and used the KDX 1.5 GUI software to read the orig.bin firmware and extract the hex code. I then opened the modified xtreme.bin and pasted the hex into that. Finally saved the edited version of xtreme.bin that I made myself with my hex code as moded.bin onto the boot disk ready to be written back to the samsung.

Then went back to the XBOX360 and booted it up with my PC (it was being recognised at this point by the bios) into MS-DOS as before and ran the following command line to upload the new firmware "mtkflash w /m moded.bin" again this did not work so using the previous switch I tried "mtkflash w /sata moded.bin" and then it started updating all four banks with success after which I was asked to reboot my PC.

I then proceeded to reconnect the XBOX360 sata cable back into the samasung drive to see if all was ok and when it started up it. it would blink the first two lights going from left to right on the power button and then flash red continiously in the bottom right hand corner. When I plugged it into a screen it was showing error 65. At this point I was devastated... but knew I had a backup soooooooo....

I went back to my PC and reconnected the samsung and booted it up using the MS-DOS boot disk to reflash with the orig.bin file back to its original firmware. ONly except this time even the PC bios wont pick up the drive anywhere and neither does the xbox or the bootdisk. I've only had it for a week and feel like like my world has ended and sleepless, basically a really big git. Now if anyone can help me here and restore some peace back into my life I will be deeply grateful...thanks in advance guys for those that bothered to read this far for which I am sorry but did not want to leave out details. Anyway I'll be looking forward to any type of assistance. I just want my XBOX360 working again  

[sniffinpoprocks]

try what easyguy just suggested, flash back to original even if it's not detected

[uknowme3]

Hi sniffinpoprocks, I've already tried flash the drive from the boot disk and it simply comes back saying that it's not recongnised or doesn't exist. Unless I am doing something wrong.

I am using the same write command as before "mtkflash w /sata orig.bin" when I get the error message. Perhaps you could enlighten me here guyz

Just as a note the original command "mtkflash w /m orig.bin" didn't work for me at all.

[Hajaz]

hotswap with any other sata device (eg sata hd)

[Sharky]

ok, check the power cable coming from the xbox to the dvd drive it may have come loose.
if not unplug it from the drive and plug it back in, do the same with the sata cable connected to the xbox and pc.  if you have a spare sata cable try replacing the one you are using.

one other thing that may help, reset your pc's bios settings  to load fail safe defaults.

make sure that you dont switch on your xbox until after you have typed in the command to flash the drive, then switch on the xbox and hit enter on the pc keyboard, it may take a few goes to flash but it will work.

[homelesschicken]

saw this in "xbox360firmwaretutorialv12.pdf"  sounds like the problem you are having

QUOTE

Bad Flash Recovery:
(thanks to Andy H.)
 
OK, I've seen lots of posts in various topics about people with apparently dead drives.
I had exactly the same problem after my floppy decided to give up the ghost mid-flash and the drive Borked.

Various solutions were offered by the group, none of which worked, so I was left with the task of finding another drive to hotswap with (Yeah, right!) or find my own solution.

This is what I found worked for me. (Twice, as I tested again by borking it a 2nd time)

You'll need a Bootable Floppy with MTKFLASH and your firmware. (we'll call this your original.bin)
Your Borked DVD drive attached to SATA 1 on your motherboard.

Boot from Floppy and get to a Dos prompt.
Type in "MTKFLASH W /SATA /M original.bin
You should get a response from the system with a list of possible sata ports to flash to.
(For arguments sake this is SATA 1 and SATA2 in this tutorial)
Turn off the power to the DVD drive wait a second and turn it back on again.
Now hit 1 on the keyboard to start the flash. (in response to the Sata 1 port on the screen)
OK, now it will start flashing or sits waiting at "Port: d800, Master/Slave: a0"
If it is waiting for more than a few seconds hit escape twice to stop the attempt and power off the drive again and keep trying the last part again. It will work after a few attempts.

This is what I have figured out so far and why this works.

MTKFLASH is looking for a response code 70 from the drive to start flashing.
Whilst the hitachi drives have a distinct recovery mode the samsungs show a code 70 JUST after power on.
I'm assuming this is a small recovery window that we can use.

The MTKFLASH software doesn't really care what device is on the SATA bus at the beginning, as long as it can detect something. Hence is people put a hot swap drive or hard drive on the sata bus, the software says "Ahh, SATA 1 has a device on there" and gives to the option to flash that port.
Only when you press 1 on the keyboard to start flashing does it try to detect what KIND of device it is and waits for the required 70 code to start flashing.

So in summary ..
Get MTKFLASH working so it detects a device on your Sata bus (Either the DVD drive or a hard drive)
Then start the flashing procedure JUST AFTER the dvd is given power, after a couple of attempts it should catch the Code 70 and start flashing.

Hope this helps.

[uknowme3]

Hi again guys, I think i broke out the champagne too early. Its still messed up. Well right now my 360 dvd-rom is working in the xbox drive. However ehnri insert originals into it, i get a message sayin This is an xbox360 game dvd. Please insert the disc into your xbox360 to play. Something like that. Anyway its not recogonising originals past that point.

Backups thats another story I dont have any to test at this time but if it can't do originals something is still very wrong

Again I'm baffled. I've not hex edited the firmware only copied over the key from my original firmware to the xtreme.bin firmware using KDX 1.5.

Again please help me guys. I've looked around the forum and there are a few posts where people have mantioned the exact problem but no fix. Maybe someone here might know    

[sniffinpoprocks]

also, you could try to just flash back your original firmware first and test with originals to be sure all is well, then you'll know for sure it's just your patching thats the problem.

[b1azin]

try using xtreme proper firmware

[homelesschicken]

try manually editing the xtreme.bin using hexedit... i posted HERE on how to do it just in case someone doesnt know how.