Post by: Hertz2P on July 18, 2006, 02:55:00 PM
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...
Post by: Hertz2P on July 18, 2006, 05:36:00 PM
Post by: x8ox on August 08, 2006, 04:40:00 PM
Post by: Exobex on August 08, 2006, 04:48:00 PM
Post by: Havok on August 08, 2006, 05:13:00 PM
If it did not dump correctly then you key is in the wrong spot and anything you do with the firmwarfe wont work.
Post by: x8ox on August 08, 2006, 05:34:00 PM
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
Post by: burnzy3 on November 23, 2006, 11:59:00 PM
Post by: langnao 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?
Post by: burnzy3 on November 24, 2006, 02:28:00 AM
Post by: angry_rabbit on November 24, 2006, 04:49:00 AM
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.
Post by: langnao 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 ...
Post by: burnzy3 on November 24, 2006, 11:42:00 AM
Post by: burnzy3 on November 24, 2006, 06:16:00 PM
Post by: myfranco on November 24, 2006, 07:53:00 PM
Post by: burnzy3 on November 24, 2006, 08:15:00 PM
Post by: burnzy3 on November 25, 2006, 08:02:00 PM
http://filesnow.net/597411
Post by: majik655 on November 25, 2006, 09:57:00 PM
QUOTE(myfranco @ Nov 24 2006, 06:53 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
Uhh.. just to clarify for this thread...
E65 IS hardware or firmware error. This is either because the firmware is bad.. OR there is something wrong somewhere on the dvd drive that is causing the xbox to THINK the firmware is bad or not there.
E66 IS the update from xbox live error. This error happens because of the original drive being changed either physically or firmware wise to look different than original.
1. ms25 flashed with 4.2 will look like a ms28 drive.. may get error. flash back to original or v3.3 firmware(based off ms25)
2. ms28 flashed with 4.2 looks like a ms28 drive good to go... unless this drive is not the original version in 360. if flashed with 3.3 this may give an error after updating.. this will look like a ms25.
There are fixes for this so ms25 drives can update to 4.2 and be ok. find this update in "usuall places".
Post by: langnao on November 25, 2006, 10:41:00 PM
Anyway, u can try power up the 360 without the SATA cable plug in or without the drive plug in. Just give it a shot, who knows, thing may just be okay again ???
P/S I think it is better to remove the link to your orig.bin. Don't think you are supposed to let anyone & everyone download your drive firmware ...
Post by: burnzy3 on November 26, 2006, 04:08:00 AM
Post by: langnao on November 26, 2006, 05:58:00 AM
QUOTE(burnzy3 @ Nov 26 2006, 07:08 PM)
my drive is an ms28 and is the original drive in the xbox. wierd thing is that i was getting e65 even before hotplugging the dvd rom in. all that happened was that it froze at 50% during a flash, showed up e65 and nothing i did after that could get rid of that e65 even flashing with orig.bin. wierd thing is that if i flash with a non manually hex editted xtreme 4.2 i get an e66. anyhow i've ordered a new drive from gameconsolehk on ebay for $90 so hopefully all is well. the only thing i can think of that stuffed things in the first place is not grounding properly. maybe the not grounding is what caused the flash to freeze at 50% in the first place. thanks for your help langnao, i'll keep u posted on teh replacement drive. also i can't seem to edit my posts
What do you mean by 'if i flash with a non manually hex editted xtreme 4.2 i get an e66' ? Can you still get it now? If you have gotten E66, it can be fixed. At least, the 360 is reading your drive right and not return the E65 error ...
Post by: majik655 on November 26, 2006, 07:15:00 AM
QUOTE(burnzy3 @ Nov 26 2006, 03:08 AM)
my drive is an ms28 and is the original drive in the xbox. wierd thing is that i was getting e65 even before hotplugging the dvd rom in. all that happened was that it froze at 50% during a flash, showed up e65 and nothing i did after that could get rid of that e65 even flashing with orig.bin. wierd thing is that if i flash with a non manually hex editted xtreme 4.2 i get an e66. anyhow i've ordered a new drive from gameconsolehk on ebay for $90 so hopefully all is well. the only thing i can think of that stuffed things in the first place is not grounding properly. maybe the not grounding is what caused the flash to freeze at 50% in the first place. thanks for your help langnao, i'll keep u posted on teh replacement drive. also i can't seem to edit my posts
You say non manually hex edited extreme I am assuming you mean that you get e66 when you allow the make 42a.bat ..
basically you say WHEN you manually hex edited the dvd key? you got e65 when the drive froze durring flash at 50%... this makes sense. The firmware froze and now you do not have a good firmware or even a complete one.. so it gave you e65. This is correct.
Then you allowed the dvd key to be inserted automatically and it gave an error 66.
This is strange because the original drive is ms28 and the firmware you are flashing it with is made for ms28 so this error does not make sense unless you screwed up somewhere,.
Anyway to recover from this.. I believe you will have to get that via sata card and do the bad flash recovery.
Simply going through the motions normally will not work.
Have you tried the bad flash recovery?
Post by: burnzy3 on November 26, 2006, 11:38:00 AM
QUOTE(majik655 @ Nov 27 2006, 01:22 AM) 
basically you say WHEN you manually hex edited the dvd key? you got e65 when the drive froze durring flash at 50%... this makes sense. The firmware froze and now you do not have a good firmware or even a complete one.. so it gave you e65. This is correct.
i get an e65 when it flashes to 100% also and with uneditted firmware.
Post by: langnao on November 26, 2006, 06:44:00 PM
Post by: burnzy3 on December 03, 2006, 11:34:00 PM
Post by: m0z on December 04, 2006, 04:48:00 AM