Print

[Carlitosbaby]

QUOTE(candp @ Oct 22 2007, 03:58 PM)

i am using a mtkflash boot disc in dos mode with via sata 6421 pci card done many samsung drive in the past no problems what so ever and as i said the flash process with this was no different that any other time just when put back into console got error 65 i then tried to reflash the drive but pc would not detect the drive and they wont eject so the flash must have gone wrong !

i have read all the firmwares from the drives and have all the keys i was gonna take the sst chips off them and flash them manually but i dont have the correct adaptor for my up48f programmer.

triedthe hotswap method using a 360 hdd but mtkflash wont even detect the 360 hdd althou on bootup the hdd is there !

any other suggestions??
p.s can not do the 10 second trick as i dont even get the an option to detect a drive like usual i get no disk detected!!! argh

btw when i said windows i meant dos!

I havent tried myself but have read a few guys that got it to flash by using mtkflash e and turning power on 360 and selecting the drive in mtkflash at the exact same time. from post I have read works very well. just do a search.

[candp]

QUOTE(Carlitosbaby @ Oct 22 2007, 10:18 PM)

I havent tried myself but have read a few guys that got it to flash by using mtkflash e and turning power on 360 and selecting the drive in mtkflash at the exact same time. from post I have read works very well. just do a search.

but it dosn't even give me a drive to select it says no drive detected

[two-rok]

after about 15 hours of trial i finally managed to read/write into a ms25 samsung, using the 10sec trick, every other method didn't work for me

this is a customer's 360 which came to me with the E65 error already and with a key only (that he assured me it was the right one because he tried another drive with this key and it got no errors), so my job is to get a new drive, insert this key with a firmware and it should work.


but because i've come across this thread, i decided to give it a try and like i said i managed to write an original ms25 firmware with the key that my customer provided, but when i plugged the sata cable and booted the 360 it gave me the e65 error again, so i'm not sure but i guess it's either one of these:

1. wrong key
2. defective drive
3. defective mobo


what do you guys think?

[Hercules Man]

QUOTE(two-rok @ Oct 23 2007, 12:52 AM)

after about 15 hours of trial i finally managed to read/write into a ms25 samsung, using the 10sec trick, every other method didn't work for me

this is a customer's 360 which came to me with the E65 error already and with a key only (that he assured me it was the right one because he tried another drive with this key and it got no errors), so my job is to get a new drive, insert this key with a firmware and it should work.
but because i've come across this thread, i decided to give it a try and like i said i managed to write an original ms25 firmware with the key that my customer provided, but when i plugged the sata cable and booted the 360 it gave me the e65 error again, so i'm not sure but i guess it's either one of these:

1. wrong key
2. defective drive
3. defective mobo
what do you guys think?

Maybe the original drive was a MS28. Putting in a MS25 could be the prob. I think you can put a MS28 drive in a 360 which had a MS25, but not the other way around. Try the ixtreme which will spoof your orig.bin from MS25 to MS28, just a stab in the dark, but worth a go.



H MAn

[two-rok]

QUOTE(Hercules Man @ Oct 23 2007, 01:15 AM)

Maybe the original drive was a MS28. Putting in a MS25 could be the prob. I think you can put a MS28 drive in a 360 which had a MS25, but not the other way around. Try the ixtreme which will spoof your orig.bin from MS25 to MS28, just a stab in the dark, but worth a go.
H MAn

thank you very much for taking the time to help me out

i'll try that when i get home, even though i never did flash ixtreme (only xtreme 5.2), can i use mtkflash to flash ixtreme into the ms25 or is another program?

cheers

[mookie_gr]

i got a problem of my own too...

1)I backed up my original firmware to "orig.bin"

2)Then i loaded in KDX the "ixtrem12.bin",and just deleted the "ff ff ff ..." in the key and pasted my original key.
(I think this was a mistake,i think i had to do more...) and saved it to modified.bin.

3) i successfully flashed the samsung drive with the "modified.bin"

4)The xbox boots up,but when i put an ORIGINAL game in,it gives me a message in multiple languages that i have to put an original game.

5)I tried several times to flash the firmware again,but i keep getting that it is in 51 mode,and it has to be in 70 (something like that, it is with mtkflash)

I dont know what to do, i have tried everthing that is in the tutorial,i must have tried like 100 times,but i couldnt get the drive in code 70 so i can flash it.

any suggestions?

[two-rok]

i've heard that it isn't a good idea to use KDX (i never used it so i can't tell for sure)

if you use FW Toolbox, and replace the fffffffffffff's for your drive's key and check if the key was successfully replaced, i'm sure it will do the work

maybe you had a bad flash

try this:

1. pc & 360 power off
2. plug a sata cable from your drive to your computer
3. power on the pc and boot from your usb key
4. type "mtkflash w /m /sata filename.bin"  (replace filename by the file you have made with fw toolbox)
5. do not hit ENTER yet.
6. power on your 360 until the loads the dashboard
7. hit ENTER
8. power off the 360
9. type the number that belongs to your sata chipset and immediatly start counting until 10 (something like 10 seconds), and then immediatly power on the 360 and it should start flashing your drive



if it doesn't work, try a few more times, also try different timings when counting to 10

make sure you've got the right key and the right firmware for your drive

also make sure you've got a compatible sata chipset

hope this guidelines helped you with your problem

cheers

[two-rok]

QUOTE(two-rok @ Oct 23 2007, 11:32 AM)

thank you very much for taking the time to help me out

i'll try that when i get home, even though i never did flash ixtreme (only xtreme 5.2), can i use mtkflash to flash ixtreme into the ms25 or is another program?

cheers

i tried preparing a usb key with iprep and then flash the ixtreme 1.2 into my ms25 (when i prepare i choose ms28 like you told me to), when booting it detects my sata onboard chipset but the 10 second trick doesn't work

because the other method didn't work i prepared another usb key with xtreme boot maker but at the end copied the ixtreme.bin to flash instead of xtreme (which i already know, didn't make any changes to the E65 error), after booting i successfully flashed ixtreme.bin into my ms25 drive, but when i boot the 360 i still get the E65 error


i mean, no matter what i flash into it, i get the E65 error, i guess i'll flash it with my own 360 key and see if the drive works on it, if it doesn't then a new drive is needed, right?

if the drive works on my 360, then the mobo is fried, right?

[two-rok]

QUOTE(two-rok @ Oct 23 2007, 09:42 PM)

i tried preparing a usb key with iprep and then flash the ixtreme 1.2 into my ms25 (when i prepare i choose ms28 like you told me to), when booting it detects my sata onboard chipset but the 10 second trick doesn't work

because the other method didn't work i prepared another usb key with xtreme boot maker but at the end copied the ixtreme.bin to flash instead of xtreme (which i already know, didn't make any changes to the E65 error), after booting i successfully flashed ixtreme.bin into my ms25 drive, but when i boot the 360 i still get the E65 error
i mean, no matter what i flash into it, i get the E65 error, i guess i'll flash it with my own 360 key and see if the drive works on it, if it doesn't then a new drive is needed, right?

if the drive works on my 360, then the mobo is fried, right?

guys, the drive is definitely fried i guess, i flashed it with my own 360 key and booted it on my 360 and it gave me the same E65 error, so this 360 problem is in the drive for sure, i'm getting a new drive for this customer's 360 and hope it solves the problem.

[mookie_gr]

how do i know if my motherboard is compatible? i have the asus p5b deluxe. But if i was able to read the flash, aint i suppose to also write to it?

from worse to worse,am i able to save my console from buying a new samsung drive from ebay? I still have the original firmware+key from my own samsung that i have right now.

This post has been edited by mookie_gr: Oct 23 2007, 11:34 PM

[Hercules Man]

QUOTE(two-rok @ Oct 23 2007, 10:12 PM)

guys, the drive is definitely fried i guess, i flashed it with my own 360 key and booted it on my 360 and it gave me the same E65 error, so this 360 problem is in the drive for sure, i'm getting a new drive for this customer's 360 and hope it solves the problem.

Sounds like a typical Samsung drive , pile of sh!te they are. I even get the same error on mine now and then when i power it up and press eject. Sometimes it throws out the E65 error because the machanism has failed ejecting properly, but i usually just close the tray, power it off and back on again, and its fine.

lets hope benQ drive is better, because i hate Samsung drives, they are cheap and nasty crap


H MAn

[two-rok]

QUOTE(Hercules Man @ Oct 24 2007, 05:36 AM)

Sounds like a typical Samsung drive , pile of sh!te they are. I even get the same error on mine now and then when i power it up and press eject. Sometimes it throws out the E65 error because the machanism has failed ejecting properly, but i usually just close the tray, power it off and back on again, and its fine.

lets hope benQ drive is better, because i hate Samsung drives, they are cheap and nasty crap
H MAn

yeh definitely, eject problems (due to a too loosen drive belt apparently) are on the top of the samsung drive problems i guess, but this fried board isn't a sweet either

thanks for the help mate

[Hercules Man]

Actually. its E74 error i get which apparently is video cable not connected properly, or in rare cases GPU problems, but the drive still sticks a lot and it drives me mad. I even had a friends 360 here recently and that sucker even dident eject properly stood up or lying flat, what a bitch. Anyhow, my 360 gets the E74 error from a cold boot the last few times i turned it on, but a second boot has turned out successfull, any one got any suggestions on the E74?, it might be going down the path of a clamp mod yet, dam, my own machine might need the x clamp mod , already done 4 360's with that fix, was hoping i dont have to do my own.


H MAn

[SuperStition]

Will this work on a Hitachi? I have no drive key, I would like to extract it.

[swampy1111]

QUOTE(SuperStition @ Dec 28 2007, 01:29 AM)

Will this work on a Hitachi? I have no drive key, I would like to extract it.

no it won't, you got to desolder the tsop and read it in a external programmer