Ok,I put all the files I need on a flash, boot NTFSDOS, run dsam. I do the 10 second thing, and it works, and says to reboot the PC, I do so. Now when I try to run fsam:
360 on.
Mtkfash sees the drive.
360 off.
Pick the drive.
Now it says Port 8000
and no matter when I turn the drive on, it never goes pasts the screen.
If I plug the drive back in the 360 and turn it on, I get a red light in the lower right. And error code E65 on the screen.
I tried to rsam, I get stuck in the same spot.
I have the original bin, but I cant for the life of me get it to work.
What can I do to get this flashed? Or back to normal?
run mtkflash (or whatever the hell cockeyed thing you are using.. I only ever use sam360hack and mtkflash from a real dos prompt with samsungs).. wait till it finds drive and move cursor to select it.. but don't hit go..
etc etc... wait until it all stops or tells you to reboot and then turn off xbox.
turn off pc.. wire drive back into xbox and test.
took me 10 minutes reading and 5 minutes doing to flash 2 e65 360 drives having never even looked at them before.
Why didn't you read the guides and the other samsung flashing help and then maybe post this in the proper 360 section where it has been answered a hundred times at least already?
Ok...because if you read what I wrote, im doing that and its NOT working. It will not progress pass the step where you have to turn it on to flash. I know how to get it detected cause I used it to dsam. I'm using the IPREP method in the TEXTBOOK. I have flashed every other 360 drive except this one with out problems.
I just used my original firmware and wrote the key to the hacked 1.4 firmware using samtool. Now that I have a hacked 1.4 firmware with the right key, what method would you suggested for getting that firmware on the drive?
EDIT: I just tried mtkflash w /m /sata ix14.bin. I get the same problem.
I start it with the 360 on.
Get two the list, turn the 360 off.
Pick it in the list.
Wait 3-15 seconds.
Turn 360 on.
It says:
Port 8000, Master/Slave: a0
and never changes or does anything else.
No.. I read what you wrote first time and you are rebooting in the middle of everything.
The error shows a bad flash or invalid key.. so it's wrong. check your patched file has the right key in it. i don't trust that ix in the blah blah filename.. I call then new.bin or a52a.bin .. x especially has meanings to programs... also dump the /sata because I haven't ever found it necessary unless flashing from a usb on 64 bit hardware, and then only some times... which I don't do unless it's all that is available on a call out job.. I flash from real M$dos 6.22 on a hdd without any windoze.. because I'm a cool person who knows how to use it :)
Originally posted by varnull: No.. I read what you wrote first time and you are rebooting in the middle of everything.
The error shows a bad flash or invalid key.. so it's wrong. check your patched file has the right key in it. i don't trust that ix in the blah blah filename.. I call then new.bin or a52a.bin .. x especially has meanings to programs... also dump the /sata because I haven't ever found it necessary unless flashing from a usb on 64 bit hardware, and then only some times... which I don't do unless it's all that is available on a call out job.. I flash from real M$dos 6.22 on a hdd without any windoze.. because I'm a cool person who knows how to use it :)
