Topic: E65 Error (Read 139 times)

Hertz2P · « **on:** July 18, 2006, 02:55:00 PM »

Samsung Drive ms25 firmware
intel ICH5 board

I read the orig.bin, modded and wrote back the xtreme.bin. Started getting the E65 error. Got the new KDX42 and made the correct xtreme.bin for it. Still E65. I wrote back the orig.bin and still E65, I can even write a file and read it back and compare the two... So I wrote my orig.bin, read it back and byte for byte it's the same, but still E65.

Somebody please stop me from pulling all my hair out...

Hertz2P · « **Reply #1 on:** July 18, 2006, 05:36:00 PM »

I've tried switching out the sata cable and that didn't help. I can seemingly read and write the flash at will, but I can't seem to put anything on the 360 that doesn't cause it to give the E 65.

x8ox · « **Reply #2 on:** August 08, 2006, 04:40:00 PM »

I'm having the same fun lol

Exobex · « **Reply #3 on:** August 08, 2006, 04:48:00 PM »

Do you have access to another machine with onboard SATA? Perhaps things are getting corrupted on their way back, in which case flashing ORIG.BIN using a different PC may get you back on track. Hopefully your ORIG.BIN isn't corrupted, though!

Havok · « **Reply #4 on:** August 08, 2006, 05:13:00 PM »

I think your orig.bin is bad... What is the filesize??

If it did not dump correctly then you key is in the wrong spot and anything you do with the firmwarfe wont work.

x8ox · « **Reply #5 on:** August 08, 2006, 05:34:00 PM »

ive tried using the xtrm0800.bin aswell which has worked
for the last 3 go's before this happened but now loads with
mtkflash but then doesnt read under windows as before

ps this is my samsung and has been changed back and forth
im starting to think it could be 5 go's and out lol

all other sammi's have been fine aswell as the hitachi's

im using ICH5 which is the best id say out of all the sata
chipsets

Thanks Again

This post has been edited by x8ox: Aug 9 2006, 12:37 AM

burnzy3 · « **Reply #6 on:** November 23, 2006, 11:59:00 PM »

i'm having the exact same problem as you guys. did either of you find a solution? I can flash my xbox drive at will, it reads the 0800enable disc and correctly goes into 0800 mode, tray ejects, everything seems fine but i get an e65 no matter if i flash with xtreme 4.2 or with orig.bin. I've also looked through my orig.bin it is exactly 256kb and seems to be a legit dump of the firmware. Any ideas at all? It's a brand new xbox i never got a chance to play it yet even.

langnao · « **Reply #7 on:** November 24, 2006, 12:17:00 AM »

QUOTE(burnzy3 @ Nov 24 2006, 03:06 PM)

i'm having the exact same problem as you guys. did either of you find a solution? I can flash my xbox drive at will, it reads the 0800enable disc and correctly goes into 0800 mode, tray ejects, everything seems fine but i get an e65 no matter if i flash with xtreme 4.2 or with orig.bin. I've also looked through my orig.bin it is exactly 256kb and seems to be a legit dump of the firmware. Any ideas at all? It's a brand new xbox i never got a chance to play it yet even.

Right after u flash you gotten E65?

burnzy3 · « **Reply #8 on:** November 24, 2006, 02:28:00 AM »

yeah got e65 straight after i had the flash freeze on me. i then managed to flash the orig.bin back on but it still gives an e65. doesn't matter now tho.. i think i've shorted the drive by plugging the power plug in sideways. would anyone be able to verify my orig.bin for me so i know whether or not it's worthwhile to buy a replacement drive?

angry_rabbit · « **Reply #9 on:** November 24, 2006, 04:49:00 AM »

Plugged the power wrong way arround on the first sammy last may. The smoke escaped from the dual regulator near the sst chip. Tried to repair by replacing the dual reg with 2 individual LD regs. The sst chip and the mt chios were ok but the servo failed to spin the disc.

Had to buy a replacement sammy.... problem solved.
If the supply to the sst chip is faulty this can give an e65 error as well.

langnao · « **Reply #10 on:** November 24, 2006, 07:13:00 AM »

QUOTE(burnzy3 @ Nov 24 2006, 05:28 PM)

yeah got e65 straight after i had the flash freeze on me. i then managed to flash the orig.bin back on but it still gives an e65. doesn't matter now tho.. i think i've shorted the drive by plugging the power plug in sideways. would anyone be able to verify my orig.bin for me so i know whether or not it's worthwhile to buy a replacement drive?

check the key with toolbox. It should still be good ...

burnzy3 · « **Reply #11 on:** November 24, 2006, 11:42:00 AM »

fw toolbox detects my key as 4478FFE4E616A4516558B75115B0ADA9 . does that look about right. also would i be able to get an ms25 and flash to ms28 and not get an e66 error?

burnzy3 · « **Reply #12 on:** November 24, 2006, 06:16:00 PM »

sorry in the above post i meant e65 error not e66. could anyone please tell me if the dvd is capable of flashing,reading, ejecting, and spinning dvds but giving up an e65 is it possible that it is a hardware error still or do i have a bad orig.bin and i'm screwed?

myfranco · « **Reply #13 on:** November 24, 2006, 07:53:00 PM »

E65 is not hardware error.At least your drive functions very well.The problem is your drive seems ms28 now but it's normally ms25.That is why 360 is giving an error

burnzy3 · « **Reply #14 on:** November 24, 2006, 08:15:00 PM »

the drive is an ms28. i get an e65 with both original and hacked firmwares. i don't know where the problem lies.. if anyone could give me their email so i could send the firmware to be compared to a known working orig.bin tat would be great.

Author Topic: E65 Error (Read 139 times)