xboxscene.org forums

Xbox360 Forums => Xbox 360 Hacking Forums => Technical DVD-ROM and Modified DVD Firmware Forum => Topic started by: Andy Hewitt on May 23, 2006, 03:47:00 AM

Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on May 23, 2006, 03:47:00 AM
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.


Title: Saving A Bricked Samsung After Bad Flash.
Post by: geebee on May 23, 2006, 04:31:00 AM
looks good...i will add this to the tutorial
Title: Saving A Bricked Samsung After Bad Flash.
Post by: drummerboy1984 on May 24, 2006, 08:54:00 PM
Hi, I tried that method, but when I type in "mtkflash w orig.bin" or "mtkflash w /sata /m original.bin" and press 1, it says "Failure to open Output file"?  I have the orig.bin, mtkflash.ex, and mtkflash.typ on the floppy disk!  Please help!.....  much appreciated....
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on May 25, 2006, 04:26:00 PM
ROFL ....

mtkflash W /SATA /m orig.bin

try that, the output file is just the firmware files name , yours is called "orig.bin" and mine was called "original.bin"

You SHOULD get a reply asking what port to flash too
(Unless only 1 device is found on a port and it auto tries)
at that point turn on the DVD and hit the associated key on the keyboard.

OR if it will not detect with the drive off.
Type the command, then powercycle the drive before hitting the confirmation key.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: flashfreak on May 25, 2006, 04:36:00 PM
Nice work, if this doesn't get found by a mod soon, PM one and ask em to put it in one of the sticky FAQ's.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on May 29, 2006, 04:36:00 PM
BUMP.

For those that need it or too lazy to search.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: mike69 on June 10, 2006, 12:52:00 PM
im trying to read my fw not flash it.. i get the error code.. and never seem to get passed it..
Title: Saving A Bricked Samsung After Bad Flash.
Post by: col55 on June 11, 2006, 06:29:00 AM
can anybody help heres my situation

i backed up my firmware 4 times and it locked up once in 4 times so i thought i would risk writting the firmware and would you believe it it locked on the 4th bank at 80%. damn it i thought ,so i panaked and write to it again and this time it froze at 40% on the first bank.tried one more time and now just hangs.

my setup was

pci card with ali m5283 chipset (i know this has problems)
boot with hard drive plugged in and nothing else
when get to a prompt un plug hd and plug in 360 un powered.
power up 360 type the usual mtkflash w mod.bin tried all other variations of command
nowit does not reconise drive do it again and it does
choose sata 1 and it backed up and wrote
i used edited mtkflash the ali version from grims posts.

now i have tried to write again to the flash by turning on 360 at command option where you choose sata 1 or 2 . press 1 straight away and just hangs every time saying the following, left for several mins each time and nothing
hangs saying

df00,master/slave :a0

now to get to option to choose sata 1 or 2 i have to power on 360 to get to sata option 1 or 2 then switch it off for a min switch back on then hit 1 straight away but just hangs tried this 10 times now.

i have read on these forums that some people have had bad flash but was able to write to it again to recover their drive any help would be great been tring to get this sorted now for over a week.thanks in advance


Andy Hewitt can you explain a bit more how you got your drive back from the dead, i have tried what you said in your post about 50 times and no luck any help would be great.thanks
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Sharky on June 11, 2006, 07:56:00 AM
The ali m5283 chipset is as buggy as hell, however what I have noticed is the only way to get it to flash correctly is to flash the chip from cold.
switch the x360 off for a few hours allowing every in the xbox to go cold, even unplug the power supply from the wall

when you ready to try flashing it again after the few hours are up boot up to the command prompt on the pc type in the command MTKFLASH W /SATA /M mod.bin
only at this point switch on the x360

count to 3 then press enter on the pc keyboard
hopefully it should flash the firmware

if it doesnt switch of the 360 and give it a couple of minutes and try again

the emphasis is on keeping the 360 as cool as possible  so that the ali chipset doesnt lock up while flashing

good luck
Title: Saving A Bricked Samsung After Bad Flash.
Post by: col55 on June 11, 2006, 10:17:00 AM
hey sharky thanks for the reply but tried everything and no luck all ready flashed it once but stopped halfway trying to reflash it but it always hangs and says df00,master/slave:a0
Title: Saving A Bricked Samsung After Bad Flash.
Post by: rtmcqueen on June 11, 2006, 01:41:00 PM
Thaks alot, you insturctions was on the money. dead drive is alive and kickin with the new firmware. I use the connectivity kit from team xecuter. I used the 360 20gig hard drive as the sata drive unplugged it and just plug in the dvd drive and BANG drive had a heart beat. thank alot you saved my $600 investment.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: col55 on June 11, 2006, 04:27:00 PM
rtmcqueen  

Thaks alot, you insturctions was on the money. dead drive is alive and kickin with the new firmware. I use the connectivity kit from team xecuter. I used the 360 20gig hard drive as the sata drive unplugged it and just plug in the dvd drive and BANG drive had a heart beat. thank alot you saved my $600 investment.


can you tell  us what you did to kill your drive did it hang why you flashed or is it a key thing.what pci or mother board you used.thanks
Title: Saving A Bricked Samsung After Bad Flash.
Post by: rtmcqueen on June 12, 2006, 09:58:00 PM
i have an asus board 800d, during flashing the drive the a drive diskett failed, cd drive would not come on no power (dead). so I read the post and tried a new method as stated a Bang. the drive works perfect.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: col55 on June 13, 2006, 10:31:00 AM
thanks for the reply will have to try mine again when i get a diff pci sata card one more compatable and hope that works fingers crossed, i dont want a £300 paper weight.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Goku60559 on June 17, 2006, 10:12:00 AM
any way to save a bricked hitachi drive!!!!...my damn system turned off in the middle of flashing the new firmware when the lights went out...wat luck...now the drive doesn't even eject...helpppppp thanks
Title: Saving A Bricked Samsung After Bad Flash.
Post by: drumow on June 20, 2006, 10:22:00 AM
Hi i used this system and always worked fine for samsung and hitachi a friend of mine used the one of windows where u cross wire the 9pin and 0pin but he left them crossed for a long time. Now he can't open the drive nor do nothing like its dead any way of saving it or is it the xbox with the prob

Thanks
Title: Saving A Bricked Samsung After Bad Flash.
Post by: neomod on June 20, 2006, 11:39:00 AM
QUOTE(drummerboy1984 @ May 25 2006, 03:54 AM) View Post

Hi, I tried that method, but when I type in "mtkflash w orig.bin" or "mtkflash w /sata /m original.bin" and press 1, it says "Failure to open Output file"?  I have the orig.bin, mtkflash.ex, and mtkflash.typ on the floppy disk!  Please help!.....  much appreciated....


Ahh yes... this satisfies my daily dosage of Noob. That is just too funny.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: drumow on June 20, 2006, 09:18:00 PM
QUOTE(neomod @ Jun 20 2006, 07:46 PM) *

Ahh yes... this satisfies my daily dosage of Noob. That is just too funny.

so what xbox is to trow away all just buy a new drive
Title: Saving A Bricked Samsung After Bad Flash.
Post by: jc0v on June 22, 2006, 04:46:00 AM
QUOTE(drumow @ Jun 20 2006, 05:22 PM) View Post

Hi i used this system and always worked fine for samsung and hitachi a friend of mine used the one of windows where u cross wire the 9pin and 0pin but he left them crossed for a long time. Now he can't open the drive nor do nothing like its dead any way of saving it or is it the xbox with the prob

Thanks


Yeah mate unfortunatley im with you does anyone have any ideas?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: feflicker on June 22, 2006, 11:11:00 AM
You should be able to use 2 drives, boot the good one, get it ready to flash, then connect the bad one and flash... But this is a good solution if you can't get your hands on a 2nd drive.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: drumow on June 26, 2006, 02:39:00 AM
QUOTE(feflicker @ Jun 22 2006, 07:11 PM) *

You should be able to use 2 drives, boot the good one, get it ready to flash, then connect the bad one and flash... But this is a good solution if you can't get your hands on a 2nd drive.

Woul seem a good ideaq but xbox shuts down as soon as u renove sata
Title: Saving A Bricked Samsung After Bad Flash.
Post by: ampedXR on July 06, 2006, 12:57:00 PM
I can confirm 100% that this DOES WORK! THanks so much for this info you have saved some of us a couple hundred dollars!

This should be made sticky!

(PS- Thanks to Grim for all his help when I had problems. Its greatly appreciated!)
Title: Saving A Bricked Samsung After Bad Flash.
Post by: feflicker on July 06, 2006, 04:12:00 PM
QUOTE
Woul seem a good ideaq but xbox shuts down as soon as u renove sata


Uh, then turn it back on. Or use another power source (homebrew or xecuter, whatever)...
Title: Saving A Bricked Samsung After Bad Flash.
Post by: DrLurch on July 06, 2006, 06:25:00 PM
I Bricked My Drive as well (backed up a couple of games then was flashing with xtreme then dead)
just woundering how meny times people had to try this befor they got there timing right, i would have tried 15-20 times and it always just come up with - port: #### (Cant Remeber) , mater/slave b0
 dose any one have any advice or a tip

thanks
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Seeker2002 on July 06, 2006, 07:01:00 PM
QUOTE(Goku60559 @ Jun 17 2006, 05:12 PM) View Post

any way to save a bricked hitachi drive!!!!...my damn system turned off in the middle of flashing the new firmware when the lights went out...wat luck...now the drive doesn't even eject...helpppppp thanks


Does anyone know the answer to this one? sad.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 08, 2006, 03:41:00 AM
QUOTE(Seeker2002 @ Jul 7 2006, 02:08 AM) View Post

Does anyone know the answer to this one? sad.gif


Sorry, cannot help with the Hitachi drive.
From what I understand there is no software released as yet to completely overwrite the firmware in the hitachi drive in 1 shot. If you could, everyone would be running the latest version and not have 4 or 5 diffrent patches depending on what revision you have.

I don't have a Hitachi drive to look at, but I'll see if I can source one out to kill and try to help folks out.

Oh, if you've bricked it due to shorting the wrong wires out, I'll look at that too.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: DrLurch on July 08, 2006, 10:01:00 PM
QUOTE(DrLurch @ Jul 7 2006, 12:25 AM) View Post

I Bricked My Drive as well (backed up a couple of games then was flashing with xtreme then dead)
just woundering how meny times people had to try this befor they got there timing right, i would have tried 15-20 times and it always just come up with - port: #### (Cant Remeber) , mater/slave b0
 dose any one have any advice or a tip

thanks


Ive Kept Trying And Still have had no Luck
Would Trying on a Different PC Help?? (my PC Dosnt have Any Trouble Detecting The Drive)
And Also Would This Same Technique work with Toshiba-Samsung_360_Auto_Flasher_v1.1 ??
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 09, 2006, 03:47:00 AM
QUOTE(DrLurch @ Jul 9 2006, 05:08 AM) *

Ive Kept Trying And Still have had no Luck
Would Trying on a Different PC Help?? (my PC Dosnt have Any Trouble Detecting The Drive)
And Also Would This Same Technique work with Toshiba-Samsung_360_Auto_Flasher_v1.1 ??


I have heard that some motherboards just don't work with MTKFLASH, but I reckon that if you can get it to read (make a backup) you should be able to get it to write.

If you have access to another PC, its not going to hurt to try. Is it?

Personally I've not used the Autoflasher and the whole point in my Tutorial was to Manually retry the flash over and over just after the powercycle.
I'd be carefull as I've heard the Autoflasher May overwrite your Orig.bin every time you try it.

This post has been edited by Andy Hewitt: Jul 9 2006, 10:49 AM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: jeajesper on July 10, 2006, 02:40:00 AM
QUOTE(Goku60559 @ Jun 17 2006, 06:12 PM) View Post

any way to save a bricked hitachi drive!!!!...my damn system turned off in the middle of flashing the new firmware when the lights went out...wat luck...now the drive doesn't even eject...helpppppp thanks


Same here  sad.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: gout on July 10, 2006, 02:56:00 AM
Flashed my drive after days of trying to connect only to find after the flash using Samsung autoflasher
all i get is the 65 error message.

Now when i flash my backup orig.bin file to it it writes the complete thing says its done then i just get the error 65 again.

I have used hexworkshop to find my key and would find it helpfull if some one could give me an idea of
what the key should look like.

offset 4000  block 200 in hex

 0111111111FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF02EEEEEEEEBBBBBBFFFFFFFFFFFFFFFFFFFFFF
 FFFF0311111111FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF04EEEEEEEEBBBBBBFFFFFFFFFFFFFFFFFF
 FFFFFFFF0511111111FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF06EEEEEEEEBBBBBBFFFFFFFFFFFFFF
 FFFFFFFFFFFF0711111111FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF08EEEEEEEEBBBBBBFFFFFFFFFF
 FFFFFFFFFFFFFFFF0911111111FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0AEEEEEEEEBBBBBBFFFFFF
 FFFFFFFFFFFFFFFFFFFF0B11111111FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0CEEEEEEEE4051D9F0
 D15EABEB3C8C05DA25CB61B3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF


Is this it ...

thanx for any help

Regards Josh
Title: Saving A Bricked Samsung After Bad Flash.
Post by: gout on July 10, 2006, 03:40:00 AM
update  

managed to flash drive with xtreme.bin  presumably the key is  inserted when i autoupdated  the first time ??   console kicks up but just says
"to play this disk put it in an Xbox 360 console" ...this applies to originals as well as my backups.

any help would be apreciated

Regards   Josh
Title: Saving A Bricked Samsung After Bad Flash.
Post by: MrEs on July 15, 2006, 09:01:00 PM
Looking for some clarification from somebody who has been successful in recovering from a bad samsung flash.
Was flashing successfully (had done read and wrote the 0800 firmware). Then was about to do 1 more flash and computer froze mid-way through.

Now im following the flash recovery section (thanks to Andy H) and can only seem to get codes 00 of 07 from my samsung drive...
Id like to know, how has this been done? by powering the drive via the console? or an after market converter/plug?
I'm using the console to try and power the drive.

Also what type of time frame am i looking at between turning the DVD drive on and pressing '1' to start flashing? Is it meant to be simultaneous?  (or as close to as i can)? 1 second? 3 seconds? I've tried with a variety of wait times and i cant get it to work, but i feel the closer these variables are the more chance of success i'll have...

Thanks so much for any help!
Title: Saving A Bricked Samsung After Bad Flash.
Post by: MrEs on July 15, 2006, 10:43:00 PM
ok i've been trying this for a few hours now...  blink.gif
Seems you have to select the 'number' to flash within <0.5 second.
But it's still not flashing for me, the best i get is mtkflash saying:
"Flash type 'SST(SST3..)'
Erasing.. Chip Erase"

Ive let it sit there for quite some time and nothing more happens, when i pres esc it says the response code was 'f0'.

I'm running with /sata and /m, eg:
mtkflash /sata /m orignal.bin
on a SATA card.

*SIGH*  wink.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: DrLurch on July 16, 2006, 01:05:00 AM
Keep Trying i Tried for 6 days befor i got it

i Typed - mtkflash w /m orig.bin

turned off then on pressed 2 then it flashed
Title: Saving A Bricked Samsung After Bad Flash.
Post by: MrEs on July 16, 2006, 01:31:00 AM
yea ive had enough for today, will give it another shot tomorrow or the day after lol.. sad.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: AddNtoX on July 16, 2006, 11:17:00 AM
if you dont have a backup of your original firmware with the correct key no firmware you put on the samsung will let you play games
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 16, 2006, 02:46:00 PM
QUOTE(MrEs @ Jul 16 2006, 04:01 AM) View Post

Was flashing successfully (had done read and wrote the 0800 firmware). Then was about to do 1 more flash and computer froze mid-way through.

Id like to know, how has this been done? by powering the drive via the console? or an after market converter/plug?


Thats how mine died "Exactly" ... After the 0800 firmware and starting to flash the Xtreme firmware

BANG .. Knackered Floppy Disk.

Just for information, I only ever powered it from the Xbox 360 console with a Sata to my Computer and a crocodile clipped cable to give an equal earth.






Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 16, 2006, 03:09:00 PM
As long as it doesn't get too out of hand.

If anyone is UK based and have bricked their Samsung, I'll gladly give it a go here, if postage is paid for BOTH ways.

Obviously if you don't have your Orig.bin (or a bios I can extract it from) I can only install the 0800 Software. But it should atleast get the drive up and running in some capacity until some other solution enables the 360 to work without the unique ID's.

I'll except the drives on their own or the complete 360 if you want it fully working and tested again.

Hopefully this SHOULD stop the amount of questions on this Topic and help to save my Inbox going into overload.

PM me if your interested.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: MrEs on July 17, 2006, 07:13:00 PM
I've still had no luck with this on the nforce5 chipset, just sits there and when i press ESC it says code '00' expected '70'.
Andy what chip-set did you use? im looking at buying a sata card specifically for this.. :\
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 18, 2006, 08:59:00 AM
My Motherboard is Intel 865G with IC5 Southbridge.

Nice simple and affective.

smile.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 18, 2006, 02:27:00 PM
OK, for the past few days I've been helping out folks via MSN with their Firmware problems.

I have a suggestion !

Stop using the Autopatchers

I reckon 9 out of 10 people who have managed to get their drive flashed, YET recieve Error 65, is due to the Autopatchers.

I've even had about 4 users who don't even have a reliable backup of their ORIG.BIN due to corruption.

If you MUST use an Auto Patcher, At the very least do a Manual Backup of your firmware and STORE ANOTHER COPY somewhere else. Then if things do go belly-Up, you can get your 360 working with a little patience.

This post has been edited by Andy Hewitt: Jul 18 2006, 09:28 PM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: amshaggy on July 18, 2006, 08:25:00 PM
i have the via6421l sata card and managed to read my orig firmware no probs. went to flash and floppy gave up after bank 1. evertytime i switch on the xbox to re-flash the green light just blinks. my sata card doesnt give me the option to chose 1 or 2 it just does it. but wehn i try to reflash the light just blinks on the 360 and nothing happens just sit at master/slave a0. tr to press escape and try again but the whole pc freezes. is there anyway i can get round this any help would be much appreciated?

btw its a sammy drive.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: davidrose9 on July 20, 2006, 09:04:00 PM
IF you have ORIG.bin  AUTOFLASHER v1.1 and Samsung:         Andy Hewitt IS gOD

LATE LAST NIGHT PANIC:

Hi, I have the Xecuter connectivity kit and the drive no longer ejects via this. I used the auto flasher 1.1, pressed 1 to extract original firmware and patch. This worked only after a few attempts as I only realized you have to power the DVD drive just after the prompt. Anyway, Once option 1 worked, I went into kdx and verified I had a key, I backed this up. I then flashed it with the xtreme firmware and it worked first time. I waited until it said please reboot pc. I tried it in the xbox and it came up error 65. I then tried to restore the original firmware but said something to the sort that the firmware wasn't recognized. I now cannot even eject the DVD ROM drive. Please help!!!


MEMBER REPLIED with:


If your confident that you have a good backup of your original firmware have you tried the bad flash recovery routine. Several people have been able to reflash their drives so they'd work by doing this but you need to have a good backup of your original firmware and you'll need to use mtkflash instead of the auto flasher. You'll find it in Geebee's latest tutorial or there is a post by Andy Hewitt on this board that covers it.



THANK YOU THANK YOU THANK YOU

WORKED GREAT WOW THANK YOU I AM DANCING AROUND IN MY LIVING ROOM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 21, 2006, 08:07:00 AM
QUOTE(davidrose9 @ Jul 21 2006, 04:04 AM) View Post

Andy Hewitt IS gOD


THANK YOU THANK YOU THANK YOU

WORKED GREAT WOW THANK YOU I AM DANCING AROUND IN MY LIVING ROOM



Thanks for the vote of confidence, I've got to admit that the response to my offer has been rather popular.

As everyone should know I offer a FREE service to (re)flash their drives. (although Donations are greatfully recieved) as long as Postage is paid for upfront.

Luckily I have managed to save about 60% over MSN just by helping folks through the process.
The others that I've had shipped to myself I have so far managed to ship EVERY UNIT back with recovered firmware. I have only failed twice with drives that there was no key file avaliable, so they have gone back with the 0800 firmware on, rather than being left corrupted.

Thanks again for the Kudos.  cool.gif


Title: Saving A Bricked Samsung After Bad Flash.
Post by: evo7 on July 21, 2006, 08:55:00 AM
managed to brick my samsung useing an ali sata card these are very unreliable it seems spent days trying to recover it with the card occasionally getting it to see the sst chip then stopping went out and got an asrock via8237 motherboard and worked first time done a few since both hitachi and samsung makes it so much easier
Title: Saving A Bricked Samsung After Bad Flash.
Post by: amshaggy on July 21, 2006, 09:29:00 AM
thanks to the great andyhewitt i managed to recover my xbox from a bad flash heres how i did it.

managed to make a backup of my orig firmware. went to write xtreme firmware and floppy gave up half way through. all i got was green light flashing on xbox and wouldnt let me flash xbox. pc just froze on the part where it goes to flash a400 master/slave a0. i was in despair as i tried everything and nothing would work.managed to get to talk to any one to one which helped a hell of a lot cos he could then properly understand the trouble i was having. he came up with the idea of leaving an ide cable plugged in and my drive so i could get the option of which drive to flash to as you need this to do the power cycle so heres a step by step of what i done.

boot up xbox without sata plugged in. boot up pc with one ide in. ( i used my liteon cdr as this was set to slave),

in dos type this command as its written mtkflash W /M and whatever you called your bin file ie. xtreme, orig.

plug in sata cable into xbox and then press enter.

should see something like 1 pri slave liteon 2 pri master v6421 sata.

switch of xbox. switch back on and wait a few seconds press 2 or whatever your sata shows could be 1 in your case, and hey presto it flashed and works a treat.

hope this helps alot of people that think they have bricked there drive but in reality have just made a bad flash and can recover.

Title: Saving A Bricked Samsung After Bad Flash.
Post by: Keltik on July 21, 2006, 09:42:00 AM
Yay (ish) this saved my second 360 - the first got twisted with the auto USB methode and didn't even get a backup of my original FW (just FF FF FF etc).

If I cock up this 360 I will probably get divorce papers from my wife.  (IMG:style_emoticons/default/jester.gif)

Ok I recovered from the bad flash and now the 360 does not frag - it boots to the dash but when I put in an original it tells me that if I wish to play this disk to put it in a 360 console ?????

Any ideas before I go at this again.

I presume it is bad FW or something.

This post has been edited by Keltik: Jul 21 2006, 04:42 PM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 21, 2006, 12:03:00 PM
QUOTE(amshaggy @ Jul 21 2006, 04:36 PM) *

Thanks to the great Andy Hewitt i managed to recover my xbox from a bad flash, I hope this helps alot of people that think they have bricked there drive but in reality have just made a bad flash and can recover.


Thanks mate, it was a blast talking to you and really pleased you managed to save both your consoles with a little over the phone help. It saved a few quid shipping them to me and you have the warm cuddly feeling inside that you managed it yourself. Not to mention your Brothers console isn't in the same situation.

Thats another tick in the completed box  (IMG:style_emoticons/default/biggrin.gif)


Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 21, 2006, 12:18:00 PM
QUOTE(Keltik @ Jul 21 2006, 04:49 PM) *

Yay (ish) this saved my second 360 - the first got twisted with the auto USB methode and didn't even get a backup of my original FW (just FF FF FF etc).

If I cock up this 360 I will probably get divorce papers from my wife.  (IMG:style_emoticons/default/jester.gif)

Ok I recovered from the bad flash and now the 360 does not frag - it boots to the dash but when I put in an original it tells me that if I wish to play this disk to put it in a 360 console ?????

Any ideas before I go at this again.

I presume it is bad FW or something.


It sounds a minor fault. Your not getting an Error 65 so its probably just the key slightly wrong.

Restore your orig.bin, test with an original game to make sure its ok.

Then try again with a new copy of the xtreme firmware and hex edit the key manually.

If you need any help just PM me your MSN details.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: amshaggy on July 21, 2006, 07:21:00 PM
yeah sounds like you have the same trouble i was having. are you using hex edit or kdx1.5? at first i was using kdx 1.5 and was getting the same problem until i used hex edit and copied the key over manually then it worked a treat.

Title: Saving A Bricked Samsung After Bad Flash.
Post by: Keltik on July 26, 2006, 02:04:00 PM
Manual is definately the only way no disrespect to the KDX guys but it just didn't work for me - I also took a while to realise that Hex Workshop had defaulted to decimal not hexadecimal - therefore I was copying  the wrong range of numbers manually - muppet

All working now though - thx Andy
Title: Saving A Bricked Samsung After Bad Flash.
Post by: sython on July 26, 2006, 03:13:00 PM
Andy, take a look at this...
http://forums.xbox-scene.com/index.php?sho...p;#entry3562237

can you have a look at my orig.bin file for me?

maybe u can help.....

This post has been edited by sython: Jul 26 2006, 10:17 PM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 26, 2006, 05:55:00 PM
QUOTE(sython @ Jul 26 2006, 10:20 PM) *

Andy, take a look at this...
http://forums.xbox-scene.com/index.php?sho...p;#entry3562237

can you have a look at my orig.bin file for me?

maybe u can help.....


Theres more than 1 way to skin a cat  (IMG:style_emoticons/default/smile.gif)

Good luck and don't forget to PM me with the results.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: SicilianBoy on July 27, 2006, 02:46:00 PM
does this tutorial work for a drive that doesnt even recognized by the bios anymore?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on July 27, 2006, 05:27:00 PM
QUOTE(SicilianBoy @ Jul 27 2006, 09:53 PM) *

does this tutorial work for a drive that doesnt even recognized by the bios anymore?


Please elaborate on the problem. 0800 firmware and bios recognition?

If its a samsung drive and your having problems flashing it, give it a shot.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: R1zz on August 04, 2006, 04:39:00 AM


I was having some questions and uncertainties about flashing my 360 drive and andy checked my fw and assured me i was gonna be oke.

i'm now the happy owner of a flashed XBOX360

Thank you very much andy.

A good community is build on people like you willing to invest time and help out people.
Keep up the good work.

Can't thank you enough.


Rizz
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on August 04, 2006, 08:43:00 AM
QUOTE(R1zz @ Aug 4 2006, 11:46 AM) *

I was having some questions and uncertainties about flashing my 360 drive and andy checked my fw and assured me i was gonna be oke.

i'm now the happy owner of a flashed XBOX360

Thank you very much andy.

A good community is build on people like you willing to invest time and help out people.
Keep up the good work.

Can't thank you enough.
Rizz


No problem and thanks for the Kudos.

Enjoy and just remember to keep the 20+ copies of your orig.bin safe.

I now officially present you with the title of "MOST CAUTIOUS FLASHER" I have ever met.

Glad to have met ya and only too glad to help.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: chinozzz on August 13, 2006, 01:28:00 AM
QUOTE(Andy Hewitt @ May 23 2006, 10:47 AM) *

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.


I got this tutorial to work for me PERFECTLY. I didnt even have to turn the xbox off and on, it immediately went into flashing my drive. I BOTCHED 2 drives and both of them were able to be restored just s good as new.

Thank You Andy Hewitt
Title: Saving A Bricked Samsung After Bad Flash.
Post by: davechann on August 14, 2006, 01:41:00 AM
can anyone help please??
I have followed all the instructions and it all seems to go as it should but when it is finished I plug the 360 into the tv and just get nothing on screen and 3 flashing red lights on my machine.

please help.

Dave sad.gif  sad.gif  sad.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on August 14, 2006, 10:47:00 AM
QUOTE(chinozzz @ Aug 13 2006, 08:28 AM) *

I got this tutorial to work for me PERFECTLY. I didnt even have to turn the xbox off and on, it immediately went into flashing my drive. I BOTCHED 2 drives and both of them were able to be restored just s good as new.

Thank You Andy Hewitt


No Problem, I'm glad you managed to save your drives.



QUOTE(davechann @ Aug 14 2006, 08:48 AM) *

can anyone help please??
I have followed all the instructions and it all seems to go as it should but when it is finished I plug the 360 into the tv and just get nothing on screen and 3 flashing red lights on my machine.

please help.

Dave (IMG:style_emoticons/default/sad.gif)  (IMG:style_emoticons/default/sad.gif)  (IMG:style_emoticons/default/sad.gif)


Depends on what the 3 lights are? I'm assuming your getting a Error 64/65 on screen?
If so recheck your orig.bin for your original key area and MANUALLY patch a fresh copy of the Xtreme software.
Then try flashing it again and see how that goes.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: davechann on August 14, 2006, 11:15:00 AM
I dont get anything at all on screen mate I just get a black screen and I tried doing a manual patch on the xtreme 3 firmware but to no avail.

its doing my head in now I havent even had a game in the damn thing yet  sad.gif  sad.gif

Dave
Title: Saving A Bricked Samsung After Bad Flash.
Post by: boulie on August 18, 2006, 02:24:00 AM
hi guys.
First of all i alredy flashed several samsung without any problems.
Yesterday a friend of mine came to me for his TS. I flashed it with the Xtreme 3.0.
When i reboot it, i keep getting the green lights blinking (the middle one). No way to eject the drive, in the dash
it's wrote "opening", but nothing happen. I tried to reflash with the original firmware but it hangs at same point.
If someone would have an idea any help would be appreciated Cheesy
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on August 18, 2006, 04:05:00 PM
QUOTE(davechann @ Aug 14 2006, 06:15 PM) View Post

I dont get anything at all on screen mate I just get a black screen and I tried doing a manual patch on the xtreme 3 firmware but to no avail.

its doing my head in now I havent even had a game in the damn thing yet  sad.gif  sad.gif

Dave


Even with the DVD drive disconnected the console will still boot to the dashboard.
If it just shows a black screen and youve confirmed your video cable is in properly then its a dead console.
Take it back to the shop and get it swapped out.




QUOTE(boulie @ Aug 18 2006, 09:24 AM) View Post

hi guys.
First of all i alredy flashed several samsung without any problems.
Yesterday a friend of mine came to me for his TS. I flashed it with the Xtreme 3.0.
When i reboot it, i keep getting the green lights blinking (the middle one). No way to eject the drive, in the dash
it's wrote "opening", but nothing happen. I tried to reflash with the original firmware but it hangs at same point.
If someone would have an idea any help would be appreciated Cheesy


Sounds like its a failed flash, its the same symptoms as one ......
Just confirm you have a proper key saved and rebuild the flash using another copy of the firmware.

Let me know how it goes.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: boulie on August 18, 2006, 10:55:00 PM
QUOTE(Andy Hewitt @ Aug 19 2006, 12:12 AM) View Post

Even with the DVD drive disconnected the console will still boot to the dashboard.
If it just shows a black screen and youve confirmed your video cable is in properly then its a dead console.
Take it back to the shop and get it swapped out.
Sounds like its a failed flash, its the same symptoms as one ......
Just confirm you have a proper key saved and rebuild the flash using another copy of the firmware.

Let me know how it goes.



hello, yes i have my proper firmware key, what do you mean by rebuilding ? thanks for the response.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on August 19, 2006, 06:18:00 AM
QUOTE(boulie @ Aug 19 2006, 06:02 AM) View Post

hello, yes i have my proper firmware key, what do you mean by rebuilding ? thanks for the response.


Sorry, it was very late when I replied above. I'm a little more rested now.

If your getting a black screen, then sort that out first.
Your console will still boot to the dashboard WITHOUT a dvd drive and show on the Screen.
If your not getting any video signal theres no point in carrying on.

If you are getting a screen, then carry on trying to repair your drive.
Extract your key and replace it into another copy of the firmware as it sounds like your copy is corrupted and acting like a failed flash.

If in doubt, you can always flash the 0800 firmware from the xtreme1 release and test the drive in windows. That will confirm the hardware works fine. Once confirmed the hardware is fine then you can concentrate on your Key and firmware.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: boulie on August 20, 2006, 12:10:00 AM
hi again, I tried to paste the key to MY origin.bin and then re-inject it, but i still have the same trouble,
always the green led blinking quickly...and i can't connect it to my pc as it hangs on directly at the boot sequence sad.gif if you have any other idea it will be welcome biggrin.gif
thanks again for your help Andy
Title: Saving A Bricked Samsung After Bad Flash.
Post by: SicilianBoy on September 05, 2006, 05:29:00 PM
hi,i also bricked a sammy drive tonight,i read this thread all the way through but i still cant revive my drive.

i tried all these commands:

mtkflash w /m original.bin
mtkflash w /b  original.bin
mtkflash w /sata /m original.bin
mtkflash w /sata /b original.bin

the drive does get recognized on port 2 but it always get stuck while flashing giving me errors like:

"erase chip failed" or "www 01 error" once it said: "updating" but it got stuck at 01% and so on...

i would like to understand if there is something im missing or if i should keep on trying until perhaps it will flash it succesfully or if its broken and i dont have any way to recover it

i am pretty confidend that original.bin is the right file and so i was hoping to revive it...

please any help perhaps?

thanks a lot in advance

later
Title: Saving A Bricked Samsung After Bad Flash.
Post by: davbere on September 05, 2006, 09:21:00 PM
Hello Andy,

I have a bricked samsung that after relashing to orig.bin(with the autoflasher 3.2) has quit ejecting and gives error 65 when installed in the 360.
 I have tried recovering using your guidelines but it just stays at  "port 9800, master/slave: a0
mY QUESTION TO YOU OR ANYONE IS WHICH VERSION OF MTKFLASH should I be using. The same one I used to flash with ? I am using a pci card with via chipset.

Thanks,

David.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on September 06, 2006, 07:40:00 AM
QUOTE(SicilianBoy @ Sep 6 2006, 12:29 AM) *

hi,i also bricked a sammy drive tonight,i read this thread all the way through but i still cant revive my drive.

i tried all these commands:

mtkflash w /m original.bin
mtkflash w /b  original.bin
mtkflash w /sata /m original.bin
mtkflash w /sata /b original.bin

the drive does get recognized on port 2 but it always get stuck while flashing giving me errors like:

"erase chip failed" or "www 01 error" once it said: "updating" but it got stuck at 01% and so on...

i would like to understand if there is something im missing or if i should keep on trying until perhaps it will flash it succesfully or if its broken and i dont have any way to recover it

i am pretty confidend that original.bin is the right file and so i was hoping to revive it...

please any help perhaps?

thanks a lot in advance

later


I've added you to my MSN, we'll have a chat there.


QUOTE(davbere @ Sep 6 2006, 04:21 AM) *

Hello Andy,

I have a bricked samsung that after relashing to orig.bin(with the autoflasher 3.2) has quit ejecting and gives error 65 when installed in the 360.
 I have tried recovering using your guidelines but it just stays at  "port 9800, master/slave: a0
mY QUESTION TO YOU OR ANYONE IS WHICH VERSION OF MTKFLASH should I be using. The same one I used to flash with ? I am using a pci card with via chipset.

Thanks,

David.


if its detecting the sata interfaces, your using the correct version.

Sounds like a failed flash, just keep trying until you got the orig.bin reinstalled.

Have you confirmed the orig.bin is actually good ?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: jakeboy on September 06, 2006, 07:34:00 PM
I created a MS-DOS boot floppy disk and placed MTKFLASH and Original.bin files on it - Booted PC and at the A prompt I typed MTKFLASH W /SATA /M Original.bin and I get this:

MTKFLASH by Joseph ???, MTK 1998 (ver 1.83c)
Port : 170, Master/Slave: aO

Then I turn of 360 and wait a sec and turn back on and Hit key 1 and nothing happens.  So I turn it off/on again and hit key 1 and nothing happens and so forth until I get this:


An internal stack overflow has caused this session to be halted.  Change the STACKS setting in your CONFIG.SYS file, and then try again.

I have a PCI controller with this driver - Adaptec Serial ATA 1205SA Host Controller - Also, its a SiI 3112A SataLink.

Any suggestions on how to get this to work on my Hitachi 47DJ?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: tvanzant12 on September 07, 2006, 02:36:00 AM
I just have a few questions regarding the bricked samsung drive. When I boot up with my sata hard drive hooked up I get a stack error, so when i unhook the hard drive i hook the sata cable from the samsung to the motherboard where I just unhooked the hard drive. I then boot up and get 3 choices, primary master, secondary master and secondary slave. Im going to assume the samsung drive is option 1. My 2 questions are, when you say "Turn off power to the DVD drive" do you mean power off your xbox, or manually pull the 12v plug out of the DVD drive itself. The second question is when you say "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" Is keep trying the last part mean, just powering off, then powering back up? Thanks in advance,
Title: Saving A Bricked Samsung After Bad Flash.
Post by: jakeboy on September 07, 2006, 03:35:00 AM
I was able to get MTKFLASH to indicate this:
Please wait...
Drive Scaned:
1: IDE Sec Master
2: Si3112 Pri Master
3: Si3112 Sec Master
choose one drive:

I pressed 2 because that is my SataLink and I get this error:

Port: a000, Master/Slave: a0
SiI3112 do not support IDE flash

Does this mean that MTKFLASH will not work at all???
Title: Saving A Bricked Samsung After Bad Flash.
Post by: lankyadz on September 07, 2006, 04:29:00 PM
Please Help, i flashed my friends samsung using xtreme 3.0 but it kept saying unrecognized disc.

I then flashed the drive back with orig.bin and now i get a black screen with white writing sayin e65.

what do i do, the drive will not recognize on pc at all now


HELP HELP HELP
Title: Saving A Bricked Samsung After Bad Flash.
Post by: lankyadz on September 09, 2006, 09:44:00 AM
QUOTE(lankyadz @ Sep 7 2006, 11:29 PM) View Post

Please Help, i flashed my friends samsung using xtreme 3.0 but it kept saying unrecognized disc.

I then flashed the drive back with orig.bin and now i get a black screen with white writing sayin e65.

what do i do, the drive will not recognize on pc at all now
HELP HELP HELP


ok so now i have managed to flash with the hacked version that i made by hotswapping the drive. when i pt an original game in it says "put this disc in an xbox 360 to play" if i put a copy on it says "unrecognized disc."

anyone got any ideas????
Title: Saving A Bricked Samsung After Bad Flash.
Post by: MHD5113 on September 09, 2006, 10:14:00 AM

Andy thanks to your tutorial I saved my dead Toshiba-Samsung DVD-ROM. But I've got a serious prob with another XBOX 360. It has a Hitachi LG 47 with a bad flashed firmware. MTKFlash stops responding when I press 1 or 2 in choosing the SATA interface. The drive is recognized in BIOS Setup but not in windows. XBOX 360 LED flashes (like the eject times), but the tray is locked in its place. When I disconnect it from PC and let it boot by itself the south-east LED (out of 4) blinks RED and an ERROR message appears on TV.

Andy and all xperts, save my Hitachi. I'm really really disappointed for that : ((
Title: Saving A Bricked Samsung After Bad Flash.
Post by: alombardo on September 11, 2006, 12:47:00 AM
I´ve decide to flash my Samsung firmware, it is a ms25. I´ve followed all the steps of the samsung autopatcher, I used a floppy disk. The motherboard of my computer is a nforce3, so I used the general options to flash the firmware. When I tried to do backup of my firmware the floppy disk failed. Then it run the installation of the new firmware, it run well but when I connected the xbox360 it appear on the screen E65. Can I try to flash it again? What I´ve I done wrong? Can I still recover it?

Thanks to all
Title: Saving A Bricked Samsung After Bad Flash.
Post by: lankyadz on September 12, 2006, 06:31:00 PM
QUOTE(alombardo @ Sep 11 2006, 07:47 AM) *

I´ve decide to flash my Samsung firmware, it is a ms25. I´ve followed all the steps of the samsung autopatcher, I used a floppy disk. The motherboard of my computer is a nforce3, so I used the general options to flash the firmware. When I tried to do backup of my firmware the floppy disk failed. Then it run the installation of the new firmware, it run well but when I connected the xbox360 it appear on the screen E65. Can I try to flash it again? What I´ve I done wrong? Can I still recover it?

Thanks to all


Do you have a reliable version of your original firmware, if not ur screwed. I had the same problem
Title: Saving A Bricked Samsung After Bad Flash.
Post by: kingpip on September 14, 2006, 02:26:00 AM
is there any way to get the original firmware back after the drive as been flashed ??
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Bentenrai on September 18, 2006, 05:04:00 PM
I keep trying this over and over, no success.
I have a samsung, and when I try to reflash it it hangs at the 'ao' part that you mentioned. I've tried it at a billion different points while booting and its still not working. Any suggestions?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: slummarine on September 20, 2006, 07:53:00 AM
hi i can get mkflash to work its detecting my drive when i start the flash with my origional.bin i get this message ERR:fail to open imput file!  

Could this mean my origional backup is corroupt?

Title: Saving A Bricked Samsung After Bad Flash.
Post by: lio256 on September 20, 2006, 03:50:00 PM
QUOTE(MHD5113 @ Sep 9 2006, 04:14 PM) *

Andy and all xperts, save my Hitachi. I'm really really disappointed for that : ((


I'm in the same boat i'm afraid. I have a backup of my original Hitachi firmware but wondered if there was anyway to reflash the drive like with the Sammy?

I hope someone can help with this soon.
And thanks for the great work you are doing for this community.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: slummarine on September 21, 2006, 09:38:00 AM
is there any way of checking the origional.bin is not corroupt ive mamgaed to sort my drive out now neway but i was wondering if there is a tool for checking the file to make sure its a clean backup

Cheers
Mick
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Mana on September 21, 2006, 09:41:00 AM
QUOTE(alombardo @ Sep 11 2006, 07:47 AM) *

I´ve decide to flash my Samsung firmware, it is a ms25. I´ve followed all the steps of the samsung autopatcher, I used a floppy disk. The motherboard of my computer is a nforce3, so I used the general options to flash the firmware. When I tried to do backup of my firmware the floppy disk failed. Then it run the installation of the new firmware, it run well but when I connected the xbox360 it appear on the screen E65. Can I try to flash it again? What I´ve I done wrong? Can I still recover it?

Thanks to all


lol this is why auto patching is such a bad idea.  if the original backup fails and it flashes the modded firmware and that doesnt work...

then u have totally screwed yoru xbox up.

trade it in or buy a new one.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Andy Hewitt on September 21, 2006, 03:40:00 PM
Sorry folks, If I've not been in touch for a couple of days, then PM me.

Other people do and your just going to miss your turn, if you get my drift.

Anyone still have probs, PM me or add me to MSN.

andyhewitt (at) f2s (dot) com

speak soon smile.gif

Title: Saving A Bricked Samsung After Bad Flash.
Post by: Nicotine on September 21, 2006, 11:35:00 PM
having 0 luck

asus a8n32 slu deluxe (NF4, running the NF4 patched MTKFlash)


system works fine....i has the first samsung hack on it.

games work, etc etc.

im trying to update now to the new 3.3....

i know my pc is ok, cuz i did a friends drive on monday.

when i plug my 360 in and do mtkflash r /m orighack.bin (saving my original hacked xtreme with my key, incase), it asks me if i want port 1 or 2. i choose 2 (like always), it hangs and waits..... (status=00, waiting for 70)

if i choose option 1, the eject light in the middle of the ring of light blinks constantly and doesnt stop.

i've tried powering the 360 on RIGHT smack after hittin 1 or 2, but it just hangs.

tried doing that at different time intervals....   MTKFlash w /m xtreme33.bin

waited NO time at all (hitting 1 or 2 at the same time i turn the xbox on), waited half a sec, waited one sec, waited 2...

any suggestions? this shit is driving me insane.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: majik655 on September 29, 2006, 05:21:00 PM
I do not know if this will help anyone but this worked for me on a ms28 drive...
my setup is asus p4p800se onboard ich5 sata.

for my setup everyone was saying to type mtkflash command then press enter.. then when asked for what ports .. then turn xbox on then off or whatever..  this works for some and seems to not work for others..

well the only way I could do it is..

type mtkflash w /m firmware.bin  do not hit enter YET..

turn xbox off.  then back on.. press ENTER like 2 seconds and I mean like 2 , 2.2, 3 no more..maybe 1.5
if mtkflash comes back with drive not found.. repeat process.. type mtkflash command again.. turn off xbox .. turn on xbox press enter,..

if timed correctly.. it will ask what port number... THEN press the correct one.  and hopefully you are on your way.

Again this is the way it work for me.. again it was on a ms28 drive.. so it seems kinda like the same process.   the timing sounds the same.

its just the powering of the xbox is a step before what alot of others say.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: br1nger on October 01, 2006, 06:58:00 PM
I have got a bad TS-H943 flash I believe but i dont have any difficulties reading/writing my firmware afterwards Ive done this several times trying to get my xbox to come alive again but I recieve the E65 everytime even when flashing back original.bin firmware. Wondering if anyone would be able to help me on this I would suppose my original.bin got corrupted or something on the way from SST--->Floppy---->HDD as the filesize is 256kb I see no other way. Maybe somebody with some training in this would spot the original key needed for a successfull firmware. My original *.bin link is below if anyone could/would help I would be in your dept.

Thanks.

http://rapidshare.de/files/35168315/ORG.BIN.html


Specs
_________

TS-H943 MS:25
VIA VT8237 SATA Controller
LiTEON SHW635S
Title: Saving A Bricked Samsung After Bad Flash.
Post by: amzchhabra on October 11, 2006, 10:54:00 AM
Just for all members with a bricked Samsung drive who cant get it working...

I sent my bricked x360 to Andy as it failed the flash back @ 12%, which meant the drive was completely unusable, it wouldnt eject, and was giving E65 during boot...

Andy, I do not know how, FIXED IT!!!! He has the skills when finding that "flash window" on the samsung drive.

Andy, Many Thanks Mate!!!

This guy is a Legend, and any advice or help needed with a bad flash, this is the man to be speaking to!

Amit
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Chinokk on October 14, 2006, 03:11:00 PM
i bricked my drive as i was flashing to xtreme4.0 sad.gif
floppy error, like some guys posted above

can't get this swapping thingy to work sad.gif
when i smash "1" too fast, it hangs, and says "status=00, should be 70"
when i do it too late (2-3 secs?)  it says "status=80, should be 70"

did u people who managed to unbrick ur drives also get that status=80 message in one of ur attempts?
or is my status=80 the proof that i managed to smash the button ;p in time, and my drive is just bricked in another way than your was? ^^
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Chinokk on October 15, 2006, 12:33:00 PM
ah and i have a ms25 btw.

been trying this all night, no luck sad.gif
ends up with status=80 or status=00

help  uhh.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: readn on October 16, 2006, 06:16:00 PM
I too am having a problem with my bricked Hitachi-LG 0046DH drive.
I've tried using the MTKFLASH w /sata /m orginal.bin command with no luck.
Many times I just get an error 51 but looking for 70 and other times I'm just getting a "can not find drive" error.
is the MTKFLASH deal only good for the Sammy drives?

I am using MTKFLASH 1.83c with it modified to work with my Asus Motherboard it has the VIA chip set.

Before the bricked problem it was able to detect via the Slacks Boot disk and I was able to flash it using the Birdy's 2.0 auto patcher it was only when I decided to restore back to orginal bios and keep it that way was when the bricked problem surfaced.

If anyone can help me out here I'm much appericated it !!
 sad.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: XboX-RoxX on October 21, 2006, 06:07:00 PM
gone out of my mind trying this got late also so imma goto bed b4 i do ill paste wut im upto

already flashed the FW with xtreme.bin problem was i didnt do key correctly and got the error loading from original game insert a 360 etc

tried numerous times to restore my orig.bin but it just hangs i know the sata etc was good due to it copied my backup and flashed ok
but silly me realised when saw that it wouldnt read my game that i had obviously done the key wrong
so now i try return to original and it just wont let me do it
tried for hours and no way will it even attempt to write the new FW or write my original
tried numerous ways i burnt the dvd 0800 but found out i needed to burn to dual layer will that enable me to rewrite my FW or re hack with the latest pls help me
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Mike46669 on October 21, 2006, 06:39:00 PM
I tried doing this for my borked hitachi drive, no luck.  Is there any way to even fix the h / lg drive from a bad flash?  the tray is locked in place, windows wont see it, idk what to do (IMG:style_emoticons/default/sad.gif)

This post has been edited by Mike46669: Oct 22 2006, 01:51 AM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: XboX-RoxX on October 22, 2006, 11:43:00 AM
well hi again im such a happy chappy i could fly lol
my xbox360 is ALIVE!!!!

this is wut i had to do butn the enable0800.iso to DVD+R Dual Layer Burner LG Super Multi 16x Dual Layer
media RiVision DVD+R DL 2.4x 8.5GB 240mins loaded CLONEDVD loaded the enable0800.iso
butnet it @ 2.4x
was bangin my head against the wall getting no where trying to reflash after flashing with xtreme41a.bin
messed up key with hex editor after flash wouldnt read originals or backups
after chatting with a friend of a friend on msn he told me to
Make BOOT Floppy add mtkflash.exe and mtkflash.typ and add my original FW orig.bin
i did this
then i booted pc
booted xbox
put in the enable0800 dvdr and let it run for 10-15 secs
have matkflash w /m firmware.bin ready to hit enter
once 10-15 secs is up eject the dvrom and press enter at same time
then select 1 which was my pri master sata and bingo it was flashing my dvdrom all went ok
put appropriate cables back etc tested to boot original working fine
then i wasnt happy cos i wanted it hackd tongue.gif
so i had the version xtreme3.3
i used the make x33.bin.bat with my orig.bin in same dir
double clicked make x33.bin.bat
hey presto it created my bin file
X33.bin
now onto floppy with this new FW binfile X33.bin and mtkflash etc
boot xbox
boot pc
dos typed
mtkflash w /m X33.bin
return
select 1 for my sata
bingo flashing procedure begins and completes nicely
put back together and woohoo my originals boot no problems
only sad thing is i used my last dvdr on burning the enable0800.iso lmao so now have to wait till tomorrow for the real momenyt of truth will update the post etc as and when
im sooooo damn happy this tutorial also helped me bigtime i was on the right track just i had to reset mine due to 41a 41b having FWGuard and cannot read / write an new / old FW without doing the dvdr with enable0800 tongue.gif didnt see much info on the 0800 method and there is a hell of a lot of tutorials etc some are very good some just plain old confuse ya remeber best help and learning is help of a friends who knows peace till next time
smile.gif
XboX-RoxX U Know It Does!!!!!
Title: Saving A Bricked Samsung After Bad Flash.
Post by: xbox360sexual on October 22, 2006, 02:37:00 PM
For all HITACHI users, MTKFLASH WILL NOT WORK WITH HITACHI'S!!!

The only way I fixed my bricked Hitachi was removing the chip and buying a new programmed one from 'swaytech.org' smile.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: bomberray on October 24, 2006, 11:42:00 AM
got a question on that hotswap thing:

how do i get mtkflash recognize my HDD (samsung sp1614n)?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: DrMadVibes on October 24, 2006, 03:27:00 PM
QUOTE(Chinokk @ Oct 15 2006, 08:33 PM) *

ah and i have a ms25 btw.

been trying this all night, no luck (IMG:style_emoticons/default/sad.gif)
ends up with status=80 or status=00

help  (IMG:style_emoticons/default/uhh.gif)


Same for me. I have a TS-H943A F/W=ms25 (FEB 2006). I succesfully flashed my XBOX 360 two times before. One time with Xtreme Firmware 3.0, the second time with 3.3. A few hours ago I tried flashing it with Xtreme Firmware 4.2A. Since I have waited to long the XBOX 360 disconnected his own power during the 4th bank (that's 3 if I remember correctly, starting with 00) at 00%.

Now my XBOX DVD drive won't open no more and when booting just my XBOX, all cables attached, I receive the error 65 (E 65 / E65).

When connecting to my PC, I use the SATA directly from my motherboard as I did succesfully two times before. I turn on my XBOX, boot my PC and wait for DOS to be loaded. During boot all for red lights are blinking aswell as the green one. Then I use the command : MTKFLASH W /SATA /M ORIG.BIN [ENTER]. Next I disconnect my power to the DVD (using the white / black cable on XBOX). Still no difference in the blinking of the leds. Plug it back in and press "1" (primary SATA). I tried this procedure with different time intervals. I even tried it reversed (that is pressing 1 first, then connecting the power again). I even tried some hard XBOX reboots.

All I get is:
Status 80, should be 70
Status 00, should be 70
Status 07, should be 70

I am quite convinced that the status should be 70 (IMG:style_emoticons/default/wink.gif) but how to get it, that's the question.
Any suggestions??

While typing this my XBOX should be cooled down a bit, I will try again in a sec.
ANDY: i added you to my buddy list, hope to meet you online soon (PM). Maybe you can help me out...

Thanks..

PS. ORIG.BIN is as clean as possible and yes I have like 20+ backups.

This post has been edited by DrMadVibes: Oct 24 2006, 10:31 PM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: DrMadVibes on October 24, 2006, 03:57:00 PM
Some additional information:

After choosing '1' from the following options:
1: NF4SAT2 primary master
2: NF4SAT2 primary slave

it keeps hanging on : 9e0, master/slave : a0

When waiting from 1 to 10 seconds I receive the error message:
status 80, should be 70

When waiting < 1 second (power on, then press '1'), I get:
status 00, should be 70

I am using MTKFLASH v1.83c and have Asus A8N-SLI motherboard.

Any ideas??
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Maigus on October 24, 2006, 05:42:00 PM
Hey guys in my recent attempt to upgrade from 3.2 to 4.1a I have hit the issue of a bad flash recovery.  I have tired everything I have read here, but still keep getting a status of 51 when it says it should be 70.

After about an hour and a half of trying I can only figure that I must have the worst timing for powering up the DVD-Rom before selecting my Sata channel.  So I was wondering can anyone give me a better description on how much time I should let go by after powering up before I select my channel?

Thanks in advance.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: 2gunsup on October 24, 2006, 06:59:00 PM
QUOTE(Maigus @ Oct 24 2006, 07:13 PM) *

Hey guys in my recent attempt to upgrade from 3.2 to 4.1a I have hit the issue of a bad flash recovery.  I have tired everything I have read here, but still keep getting a status of 51 when it says it should be 70.

After about an hour and a half of trying I can only figure that I must have the worst timing for powering up the DVD-Rom before selecting my Sata channel.  So I was wondering can anyone give me a better description on how much time I should let go by after powering up before I select my channel?

Thanks in advance.


im in the same boat, dont get a 51, i only get 00 and 80, for you guys that have done this sucessfully, whats your timing?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: jaysynn on October 24, 2006, 07:10:00 PM
QUOTE(XboX-RoxX @ Oct 22 2006, 01:43 PM) *

well hi again im such a happy chappy i could fly lol
my xbox360 is ALIVE!!!!

this is wut i had to do butn the enable0800.iso to DVD+R Dual Layer Burner LG Super Multi 16x Dual Layer
media RiVision DVD+R DL 2.4x 8.5GB 240mins loaded CLONEDVD loaded the enable0800.iso
butnet it @ 2.4x
was bangin my head against the wall getting no where trying to reflash after flashing with xtreme41a.bin
messed up key with hex editor after flash wouldnt read originals or backups
after chatting with a friend of a friend on msn he told me to
Make BOOT Floppy add mtkflash.exe and mtkflash.typ and add my original FW orig.bin
i did this
then i booted pc
booted xbox
put in the enable0800 dvdr and let it run for 10-15 secs
have matkflash w /m firmware.bin ready to hit enter
once 10-15 secs is up eject the dvrom and press enter at same time
then select 1 which was my pri master sata and bingo it was flashing my dvdrom all went ok
put appropriate cables back etc tested to boot original working fine
then i wasnt happy cos i wanted it hackd (IMG:style_emoticons/default/tongue.gif)
so i had the version xtreme3.3
i used the make x33.bin.bat with my orig.bin in same dir
double clicked make x33.bin.bat
hey presto it created my bin file
X33.bin
now onto floppy with this new FW binfile X33.bin and mtkflash etc
boot xbox
boot pc
dos typed
mtkflash w /m X33.bin
return
select 1 for my sata
bingo flashing procedure begins and completes nicely
put back together and woohoo my originals boot no problems
only sad thing is i used my last dvdr on burning the enable0800.iso lmao so now have to wait till tomorrow for the real momenyt of truth will update the post etc as and when
im sooooo damn happy this tutorial also helped me bigtime i was on the right track just i had to reset mine due to 41a 41b having FWGuard and cannot read / write an new / old FW without doing the dvdr with enable0800 (IMG:style_emoticons/default/tongue.gif) didnt see much info on the 0800 method and there is a hell of a lot of tutorials etc some are very good some just plain old confuse ya remeber best help and learning is help of a friends who knows peace till next time
(IMG:style_emoticons/default/smile.gif)
XboX-RoxX U Know It Does!!!!!



DUDE i love you! using your method unbricked my friend's samsung drive tytytytytytytytytytytytyty
Title: Saving A Bricked Samsung After Bad Flash.
Post by: DrMadVibes on October 25, 2006, 12:23:00 AM
Any ideas on opening a drive when the eject button / function doesn't work? or does this mean power is definitially off?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: 2gunsup on October 25, 2006, 04:53:00 AM
QUOTE(DrMadVibes @ Oct 25 2006, 01:54 AM) *

Any ideas on opening a drive when the eject button / function doesn't work? or does this mean power is definitially off?



same question, mine doesnt work at all, I try to select open via the control and it stays stuck on opening.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: 2gunsup on October 25, 2006, 10:42:00 AM
bump
Title: Saving A Bricked Samsung After Bad Flash.
Post by: psxguy on October 25, 2006, 03:48:00 PM
FREE BUMP! With the info in this thread I was able to get one on of my X360s from


Bricked Samsung Ms25

TO

Flashed to xtreme 4.2b not reading any original or backup discs (could never figure this part out  (IMG:style_emoticons/default/unsure.gif) )

TO

Store bought stock condition.  (IMG:style_emoticons/default/biggrin.gif)

This post has been edited by psxguy: Oct 25 2006, 10:49 PM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Chinokk on October 25, 2006, 05:16:00 PM
QUOTE(DrMadVibes @ Oct 24 2006, 11:57 PM) *

Some additional information:

After choosing '1' from the following options:
1: NF4SAT2 primary master
2: NF4SAT2 primary slave

it keeps hanging on : 9e0, master/slave : a0

When waiting from 1 to 10 seconds I receive the error message:
status 80, should be 70

When waiting < 1 second (power on, then press '1'), I get:
status 00, should be 70

I am using MTKFLASH v1.83c and have Asus A8N-SLI motherboard.

Any ideas??


yeah my drive is still bricked
i also have a asus a8n-sli board
i consider soldering out the sst chip and get a new one flashed with my original firmware
would cost me ~ 16€, but the epoxy removal sucks really, so i'll wait one week or two more if someone can figure out how to fix this the "soft" way...
btw. you are the first one having the same problem i have (status 80 thingy)


QUOTE(DrMadVibes @ Oct 25 2006, 07:54 AM) *

Any ideas on opening a drive when the eject button / function doesn't work? or does this mean power is definitially off?


you can open it by moving the black cogwheel just beneath the tray, but why would you want to do that? (IMG:style_emoticons/default/tongue.gif)
it won't spin any disks (if ur were thinking about the 0800 dvd), cause all mechanics are disabled :/
Title: Saving A Bricked Samsung After Bad Flash.
Post by: DrMadVibes on October 27, 2006, 04:28:00 PM
Since I could not get it working I went for the solder out function. By using Hot air equipment for removing the flash chip, and a professional universal programmer for reading/flashing the chip, I managed to get my original firmware and key back on my drive.

It works again! Since I am not a hardware tech at all I managed to found some help here in Holland at Stegen.

http://www.stegen.com/product_info.php/cPa...products_id/987

Thanks Stegen!
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Fyreblaze on October 28, 2006, 04:19:00 PM
So I bricked my drive. I'm trying to use your method using an xecuter connectivity kit. I'm also using a 6421 controller. I type: "mtkflash w /m orig.bin" and get:

drive scanned:
1: IDE Sec Master
2: Xtreme Pri Master
Choose one drive:

I power off my TS drive, wait for a while, then power it on. 0-5 seconds later I press 2, butIi always get hung up. If I press it anywhere from instantly to ~ 15 seconds I get:

Port: dfa0, master/slave: a0
status = 00, should be 70

If I wait for a long time bofore pressing 2 (about 15 seconds) I get:

Port: dfa0, master/slave: a0
status = 51, should be 70

Is there any way you can judge timing off that? what should the timing be? around 2 seconds? Is my drive just fried? I turn the power on in the back and it takes around 15 seconds before the button on the connectivity kit makes it eject. Also, last question. How can you make sure your origional firmware isn't corrupt?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: -ricky- on October 29, 2006, 01:54:00 AM
QUOTE(XboX-RoxX @ Oct 23 2006, 04:43 AM) *

well hi again im such a happy chappy i could fly lol
my xbox360 is ALIVE!!!!

this is wut i had to do butn the enable0800.iso to DVD+R Dual Layer Burner LG Super Multi 16x Dual Layer
media RiVision DVD+R DL 2.4x 8.5GB 240mins loaded CLONEDVD loaded the enable0800.iso
butnet it @ 2.4x
was bangin my head against the wall getting no where trying to reflash after flashing with xtreme41a.bin
messed up key with hex editor after flash wouldnt read originals or backups
after chatting with a friend of a friend on msn he told me to
Make BOOT Floppy add mtkflash.exe and mtkflash.typ and add my original FW orig.bin
i did this
then i booted pc
booted xbox
put in the enable0800 dvdr and let it run for 10-15 secs
have matkflash w /m firmware.bin ready to hit enter
once 10-15 secs is up eject the dvrom and press enter at same time
then select 1 which was my pri master sata and bingo it was flashing my dvdrom all went ok
put appropriate cables back etc tested to boot original working fine
then i wasnt happy cos i wanted it hackd tongue.gif
so i had the version xtreme3.3
i used the make x33.bin.bat with my orig.bin in same dir
double clicked make x33.bin.bat
hey presto it created my bin file
X33.bin
now onto floppy with this new FW binfile X33.bin and mtkflash etc
boot xbox
boot pc
dos typed
mtkflash w /m X33.bin
return
select 1 for my sata
bingo flashing procedure begins and completes nicely
put back together and woohoo my originals boot no problems
only sad thing is i used my last dvdr on burning the enable0800.iso lmao so now have to wait till tomorrow for the real momenyt of truth will update the post etc as and when
im sooooo damn happy this tutorial also helped me bigtime i was on the right track just i had to reset mine due to 41a 41b having FWGuard and cannot read / write an new / old FW without doing the dvdr with enable0800 tongue.gif didnt see much info on the 0800 method and there is a hell of a lot of tutorials etc some are very good some just plain old confuse ya remeber best help and learning is help of a friends who knows peace till next time
smile.gif
XboX-RoxX U Know It Does!!!!!



Thanks mate - using the enable0800.iso DVDR worked a treat!! My floppy died during the middle of flashing and had no luck re-flashing FW until buring the enable0800.iso DVDR. As the eject button had stopped functioning due to the bad flash I needed to unscrew the DVD drive metal enclosure and manually place the disc in the drive and re-assemble. Apart from that small problem I successfully re-flashed using the exact procedure in your post. A suppose "wasting" a DVD+R DL disc is a very small price to pay to get my xbox 360 working again!!

Cheers  smile.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Slawterr on October 29, 2006, 08:48:00 PM
Here I am in the same boat with a bad flash, the drive doesn't even spin up and won't eject. I was updating my flash to 4.2 and then POOF the 360 turned itself off and froze at about 7% on bank 4. I've tried everything in this thread and was wondering if anyone had any ideas. Tried everything I can without the 0800 disc since the drive won't open or let alone spin. And yes I know it won't spin becuause I left my Table Tennis disc in it. (IMG:style_emoticons/default/smile.gif)

When I attempt to flash, mtk just sits there with its thumb up its ass and doesn't end up giving me any errors or anything except if I hit esc. I get error 00, 01 and 05 randomly. I'm about to throw this thing out the window. Any ideas would be appreciated.

This post has been edited by Slawterr: Oct 30 2006, 04:51 AM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: gerzand on October 29, 2006, 09:10:00 PM
I am in a very similar boat as the guy that has posted before me.

I was going from a stock drive to firmware 42a when my 360 overheated and turned off. Flashing stopped at 6% through Bank 3. I tried multiple timings with mtkflash (waiting 1, 1.5, 2, 2.5, even 3 seconds) before pressing #2 for my corresponding SATA  port. I get either 00, or 80 depending on how long I wait before pressing #2. I even speculated that maybe i needed to try the enable 0800 disc to disable firmgard, but from what I can see my drive isnt even spinning up (it also wont eject, so I manually ejected it in order to get it in there and it discs dont move a bit).

Any ideas? Thanks in advance.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: 2gunsup on October 30, 2006, 02:05:00 PM
QUOTE(gerzand @ Oct 29 2006, 10:41 PM) *

I am in a very similar boat as the guy that has posted before me.

I was going from a stock drive to firmware 42a when my 360 overheated and turned off. Flashing stopped at 6% through Bank 3. I tried multiple timings with mtkflash (waiting 1, 1.5, 2, 2.5, even 3 seconds) before pressing #2 for my corresponding SATA  port. I get either 00, or 80 depending on how long I wait before pressing #2. I even speculated that maybe i needed to try the enable 0800 disc to disable firmgard, but from what I can see my drive isnt even spinning up (it also wont eject, so I manually ejected it in order to get it in there and it discs dont move a bit).

Any ideas? Thanks in advance.


ive ran into the same roadblock =\ can someone help us  (IMG:style_emoticons/default/sad.gif)
Title: Saving A Bricked Samsung After Bad Flash.
Post by: andrew1979 on November 02, 2006, 06:17:00 AM
this method work for samsung ms28?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: andrew1979 on November 02, 2006, 06:57:00 AM
QUOTE(andrew1979 @ Nov 2 2006, 02:48 PM) *

this method work for samsung ms28?



this method work for samsung ms28 with error 65?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: mgs666 on November 04, 2006, 12:12:00 AM
hi everybody

same problem for me

have done 10 consoles before this one, bad sector on floppy so bad samsung flash

i've tried to reflash it but i've the same problem as you all, mtkflash error

1sec 2sec 10 sec, i've tried a lot but nothing change

so UP this post  biggrin.gif

thanks
Title: Saving A Bricked Samsung After Bad Flash.
Post by: violentj1 on November 04, 2006, 07:37:00 PM
im in the same boat as you guys-have any of you had any sucess yet
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Chinokk on November 05, 2006, 11:59:00 AM
i got a new ms25, so i replaced the whole drive
flashed the new one with 3.3 fw
i'll pass on firmguard unless there's another way to bypass it than the 0800 disk (a hard way, like solder a bridge somewhere, dunno wink.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: monsoft on November 05, 2006, 03:30:00 PM
OK guys.

This trick isn't new and anyone who did reflashing his dvd-rom with MS28 know it.
This is only way to start flashing.

But you can change some moves to get almost 100% hits.

When you get screen with list to choose contoller (1,2..) turn off DVD-ROM power and hit your
right choice. After that mtkflash will show information about address and channel etc...
Now switch on DVD-ROM power and mtkflash should write.

I did it couple of times and always 100% successful smile.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: sew2902 on November 06, 2006, 03:15:00 PM
I'm having the same problems as you guys, MS28 drive, pc crashed mid flash, drive wont open now or anything. I had flashed it before so I know all about the flash recovery method (turn it off and on at the right time, etc), but now after the bad flash nothing i do will make mtkflash do anything. It will give me the menu option of selecting the drive, but turning the xbox on and off at about a 1000 different times and places did nothing. I'm chalking it up as a loss, and the fall update makes it even more of a pain because I have a spare hitachi drive I can't use now either  sad.gif .
Title: Saving A Bricked Samsung After Bad Flash.
Post by: bloodtrax on November 06, 2006, 09:16:00 PM
Thank you so much Andy Hewitt. I just did as you said and i brought my samsung drive back from the dead  biggrin.gif  But I have a favour to ask all that may be able to help me. When i bricked my sammy i got a replacement hitachi swapped my key over and got the hitachi booting no problem. So as i thought my sammy was dead i deleted my firmware files for it. My brother has a sammy ms25 I used his orig.bin modded it with 4.2a and added the key from my now working hitachi and flashed that to my sammy all is fine it works again. But my sammy is an ms28 so i have no orig.bin for an ms28 I was wondering if anyone could give me a stock ms28 orig.bin that i can put my key into incase i have to go back to the original firmware sometime in the future. Thanks Bloodtrax.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: monsoft on November 08, 2006, 02:43:00 PM
QUOTE(sew2902 @ Nov 6 2006, 05:15 PM) *

I'm having the same problems as you guys, MS28 drive, pc crashed mid flash, drive wont open now or anything. I had flashed it before so I know all about the flash recovery method (turn it off and on at the right time, etc), but now after the bad flash nothing i do will make mtkflash do anything. It will give me the menu option of selecting the drive, but turning the xbox on and off at about a 1000 different times and places did nothing. I'm chalking it up as a loss, and the fall update makes it even more of a pain because I have a spare hitachi drive I can't use now either  (IMG:style_emoticons/default/sad.gif) .


Do not turn off whole xbox, rutn off and on only dvd-rom. In my case was exactly like you said.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: sew2902 on November 09, 2006, 05:07:00 PM
QUOTE(monsoft @ Nov 8 2006, 09:14 PM) *

Do not turn off whole xbox, rutn off and on only dvd-rom. In my case was exactly like you said.


Thanks bro, that did it. Really appreciate the help  (IMG:style_emoticons/default/biggrin.gif) .
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Yid on November 13, 2006, 03:46:00 PM
this might sound strange, but how do you know youve bricked your drives ? I have had friends ask me questions about this, they say their 360's wont play copies etc no originals work etc.

50% of the time you guys have had a bad flash but it has still flashed as there was no error but the drive didnt like it so it will put you in modeb for protection.

To get out of modeb, make sure there is no game in the drive, boot the 360 by pressing eject, put the game in and close the tray.

voila, it should now load your games and take you out of modeb

Might not work for you all, but should work for some unless youve totally screwed it.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: corc on November 17, 2006, 02:06:00 AM
Andy you saved my 360, thanks my friend.

Just for those out there with a bricked samsung that are trying to get it back 2 life and with no success get it to andy and he will work his magic.  I tried for days and days with my bricked drive but no success with my nforce3 chip set but got it to andy and with 24 hours he had it back in the post on its way to me.  thanks again andy for all the help, you truely are a life saver.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: big_evil on November 17, 2006, 07:57:00 AM
to power off the dvdrom only, is it as simple as pulling out the power connector and then replacing it?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: sew2902 on November 17, 2006, 01:57:00 PM
QUOTE(big_evil @ Nov 17 2006, 02:28 PM) *

to power off the dvdrom only, is it as simple as pulling out the power connector and then replacing it?


Yup.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Julius Pleaser on December 08, 2006, 09:45:00 PM
I used KDX for extracked my key and I think that is what causes my issue.  It flashed fine and will load fine, but it won't play any games including originals.

Now when I try and flash back to the original firmware I get "Port: a400, Master/Slave: a0" I have tried all the methods above. Powering off/on xbox at certain times, enable800 disc, etc.  But I always get the same message.  At best I have gotten different #'s (170??  I think) once or twice.
  Any ideas?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Julius Pleaser on December 08, 2006, 10:16:00 PM
I also wanted to add that when I press esc I always get "status = 51, should be 70"
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Julius Pleaser on December 09, 2006, 10:32:00 AM
Ok, after 8 long hours and staying up to 2:30am I finally got it to work.  Many thanks to Andy Hewitt for keeping me sane and making me realize the exact order of how you do it really does make a difference.  I had previously tried EVERYTHING in this thread, but not in the exact order that ended up working.  So here it is, what I did to get it to work.  I am pretty sure step 1.5 was completely useless but I am including it just in case in some unkown way it actually did something.

Assuming you have connected your 360 to your PC properly and made a proper boot disk (ie. mtkflash setup to work with your SATA chipset, and the appropriate firmware on the disk and has your drive key properly inserted.... Don't use KDX, as that is what caused all my problems in the first place.)


1. Boot Xbox 360 and wait for it to finish it's bootup

1.5 I booted the 360 drive with the Enable 0800 disc in since I had Xtreme 4.2A previously flashed.  I am 99% sure this step was useless as I end up power-cycling the drive before I actually flash it which would reset it.  But I am including it just in case.

2. Boot PC

3. From prompt type "mtkflash w /m whatever.bin" like normal and hit enter

4. It should now ask you which device to write choices 1,2, etc.  If it doesn't then you have no ide devices connected and you should connect at least one IDE CD/DVD drive and repeat steps 1-3 so that you get to this menu rather than it auto-selecting your SATA.

5. Don't make a selection yet!!!  Staying at this menu of what to flash, turn off your Xbox 360. Wait 5 seconds.

6. Now select the device to flash (1,2, whatever) that corresponded with your SATA controller.

7. It should be sitting at that "Port: a400, Master/Slave: a0" type message now.  Count to exactly 10 seconds. Not 9 seconds, not 11 seconds, exactly 10 seconds

8. Turn on Xbox 360 and it should start to flash
Title: Saving A Bricked Samsung After Bad Flash.
Post by: astandard on December 10, 2006, 12:07:00 AM
Im a spanking noob and of course I've managed to brick my MS25 on the first try..lol. Backed up the orig FW fine. Just that during flashing, it hung at bank 3. I've read all the posts on this thread and tried every possible methods that were mentioned. And the results are rather depressing...still a NO GO sad.gif I get nothing after "Port: dd60, M/S:a0". I even tried to pop in manually (by open the drive case) the enable800 DL disc. The drive won't spin. Arghh...are helps still available for this problem?  Any other definitive method that doesn't require luck or randomly turn on/off PC, xbox, etc...at certain timeframe?

MS25
VT6421A chipset/PCI Card
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Langoman on December 10, 2006, 09:26:00 PM
QUOTE(Chinokk @ Nov 5 2006, 04:59 PM) *

i got a new ms25, so i replaced the whole drive
flashed the new one with 3.3 fw
i'll pass on firmguard unless there's another way to bypass it than the 0800 disk (a hard way, like solder a bridge somewhere, dunno (IMG:style_emoticons/default/wink.gif)


AWESOME MAN!!!!

That worked at first time to me (IMG:style_emoticons/default/biggrin.gif). I followed each step properly and got it with 100% ratting.

Great!!

Thanks a lot man, 'cause after fall update I got E66 with firm 4.2b and 0800disc didn't work on my sammy ms25 drive.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Spidey29 on December 13, 2006, 09:26:00 AM
QUOTE(Julius Pleaser @ Dec 9 2006, 09:03 AM) *

Ok, after 8 long hours and staying up to 2:30am I finally got it to work.  Many thanks to Andy Hewitt for keeping me sane and making me realize the exact order of how you do it really does make a difference.  I had previously tried EVERYTHING in this thread, but not in the exact order that ended up working.  So here it is, what I did to get it to work.  I am pretty sure step 1.5 was completely useless but I am including it just in case in some unkown way it actually did something.

Assuming you have connected your 360 to your PC properly and made a proper boot disk (ie. mtkflash setup to work with your SATA chipset, and the appropriate firmware on the disk and has your drive key properly inserted.... Don't use KDX, as that is what caused all my problems in the first place.)
1. Boot Xbox 360 and wait for it to finish it's bootup

1.5 I booted the 360 drive with the Enable 0800 disc in since I had Xtreme 4.2A previously flashed.  I am 99% sure this step was useless as I end up power-cycling the drive before I actually flash it which would reset it.  But I am including it just in case.

2. Boot PC

.......



I'm going to give your method a try Julius. I flashed my drive for the first time last night (after making sure all update patches were applied), I did the manual MTKFlash-NF4 method and got my orig.bin with key. I started flashing the Sammy MS25 and my floppy died on bank 4 (bank1,2,3 = 100%, bank4 = 0%) leaving me with a non-detected drive (not in bios, nothing) - Xbox boots up with flashing center light (power icon) in green. I'm thinking burning the image/tools to a bootable DOS CD might be better, once you've acquired your key and inputted it in the bin - anyone see any problems with that? My flash doesn't like to boot, I don't see any reason for MTKFLASH to want to write to anything when you flash - plus, CD's are like 5cents.

I've tried just about every method, but I haven't tried leaving it on the "Port: a400, Master/Slave: a0" - when I try to MTKFLASH it as it is, it throws this error almost instantly after making a selection. We'll see. After that, I'm going to try the power-off DVD-only method (requires opening the case again) and the enable0800 disc methods.

This post has been edited by Spidey29: Dec 13 2006, 05:27 PM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Julius Pleaser on December 13, 2006, 10:29:00 AM
Just make sure you follow what I did exactly.  You can ignore the enable0800 part as I have confirm it was not needed like i thought.

Also, make sure you have the AV cable plugged into your 360 or it won't boot properly.
And if after you type mtkflash... it goes to the error right away, then you don't have another IDE plugged into your PC which you need so that you have the choice menu come up./
Title: Saving A Bricked Samsung After Bad Flash.
Post by: hairless47 on December 13, 2006, 05:46:00 PM
My MS25 sammy flash hung up at bank3. The drive would not spin & gave an error E65. I finally reflashed the drive by connecting to a VIA4621 PCI card on Sata Port #1. I started my computer with my usb key. I entered the MTKFLASH w /m orig.bin but don't hit enter yet. I powered up my xbox360. When the green ring started to light up at 10 seconds I then hit the enter key. I was give a choice of 1 or 2.  I powered down the xbox360. After 5 seconds, I repowered up the xbox360. Start at 1 second intervals to push the 2 key. 2 seconds worked for me. My Sammy drive was reflashed &  biggrin.gif  is working properly.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Spidey29 on December 14, 2006, 01:22:00 PM
QUOTE(hairless47 @ Dec 13 2006, 04:46 PM) *

My MS25 sammy flash hung up at bank3. The drive would not spin & gave an error E65. I finally reflashed the drive by connecting to a VIA4621 PCI card on Sata Port #1. I started my computer with my usb key. I entered the MTKFLASH w /m orig.bin but don't hit enter yet. I powered up my xbox360. When the green ring started to light up at 10 seconds I then hit the enter key. I was give a choice of 1 or 2.  I powered down the xbox360. After 5 seconds, I repowered up the xbox360. Start at 1 second intervals to push the 2 key. 2 seconds worked for me. My Sammy drive was reflashed &  (IMG:style_emoticons/default/biggrin.gif)  is working properly.


I got a question for ya. Did you flash with a different SATA card(or onboard) originally? Because I was using the onboard SATA on my DFI LanParty NF4-based mobo. It worked fine and always detected, now no matter what - it won't detect. I'm curious if picking up a VIA-based SATA card will resolve my issue.

I'm having the exact same issue. Flashed fine til Bank#4 when my A:/ failed. After that, no spinning, no ejecting, no detecting in the system.

I initially wanted to try it with my USB drive, but the HP utility doesn't like my generic Flash drive - it formats and says it worked, but the drive remains empty and won't boot. I get an NTLDR error. *shrug*

This post has been edited by Spidey29: Dec 14 2006, 09:27 PM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: goldguy27 on December 17, 2006, 02:08:00 AM
I keep getting a status at 00, status needs to be at 70 or whatever.  When i first started doing it i got an 80, but i cant seem to get it back to save my life.  Ahh i dont know what i havent tried
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Spidey29 on December 18, 2006, 03:36:00 AM
Alright, got my brick MS25 working again. Here's what I did:

- Went to store and bought a MACSENSE (temporary, until NewEgg delivers theirs) SATA card, had the VIA VT6421A. It's for a Mac/PowerPC, so I used the drivers from VIAArena.com

- Used "Xtreme Boot Maker" to make a custom MTKFlash w/ MS28 patches.

- Made a bootable USB drive
NOTE: I couldn't get this to work before, the problem was that WindowsXP makes a bootable disk that references the A: drive, so it'll give a "NTLDR" error without the disk in the drive. I downloaded a MS DOS 8.0 image from bootdisk.com and put that on the disk. Then used HP's tools (found in one of the toolkits, it's 1.9mb, not the 40mb version) to make the flash drive bootable.
NOTE2: Highly recommend this, it's faster and safer than a floppy. Plus, you can get a cheap flashdrive on sale. I got a cheapo Emprex just for this stuff (512mb) at Fry's for $4.99

- Opened Xbox360 to reach the power cable. I have a port on the outside for SATA, but not for power disconnect.

- Got to the MTKFlash menu screen, turned Xbox360 off and selected "3" (my XTREME in the list).

- Counted to 10 seconds and plugged power into Xbox360 drive. It flashed and was done. No more errors!

So it appears that once I flashed from MS25 to 4.2b (MS28 based), it no longer liked the NF4 onboard SATA. Only way to flash now (for me at least) is with a VIA based board.

Just for a quick recap:
The drive was "bricked" initially because of a floppy that died halfway through the flash. It wouldn't respond to eject, wouldn't spin up, wouldn't do anything. It'd lock up the PC on boot if powered on when the PC did a POST.

This post has been edited by Spidey29: Dec 18 2006, 11:39 AM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: goldguy27 on December 18, 2006, 07:17:00 PM
well i bricked my samsung ms25 with the ms28 based xtreme42a.bin.  Thank god for Andy Hewitt, he talked me through the soldering, and managed to coach me through all the timings to bring her back to life.  i feel like i just took the defibilator to my own mother.  Im back in business, and the 360 is working perfectly.  Thanks again andy.  I actually left my wires crossed the entire time, and it worked on my k8v se deluxe mobo with an onboard via controller.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: ILLPLEASA on December 21, 2006, 10:00:00 PM
Just fell into some bad luck myself last night when I was flashing 5.0A onto my drive.. Floppy disk died on my through bank 3 (for the first time since I ever started backing up btw)... I panicked ofcourse since this was the first time that ever happened and thought I was SOL...

I started reading about the Bad Flash Recovery Method (or 10 Sec Method as some people call it) and read over DOZENS of differnt ways that people got their f'ed up drives working again... Well I'm just here to show (like eveyone else online) how exactly it was that I did it lol..

Only difference is that I'm pretty much writing it so that if I ever need to do this again (hopefully never cause I'm sticking with CD-RW for booting to DOS and never using Floppies again) (My comp can't boot to USB thats why I'm stuck using CD's btw) then I can just re-read the steps I used so I don't forget them later lol..

My drive was a MS25 (March 06) and it wasn't completely bricked, it just didn't eject or spin up... MTKFLASH still recognized it in DOS btw as well...

I have a VT6421 SATA PCI Card connected to my pc because my motherboard is the old school IDE-ATA (I know, I know)

Mind you I was up for like 8-12 hours reading through threads and trying different methods and failing each and every time before reading one last different approach (well slightly different because all methods are almost the same with just slight variations) and I was gonna try a few more times before I gave up and presto... Flashed

Well heres what I did...

1) Had the Xbox360 Samsung TS-H943 drive connected to my PC via SATA (Both the PC and the 360 were powered off)

2) Powered on the PC and let my floppy boot into DOS. When it did I typed MTKFLASH w /m /sata orig.bin (as I wanted to flash the original firmware and not any modified ones) but DIDN'T hit enter yet...

3) Powered on my 360 drive and let it boot to the Main Menu...

4) Pressed enter on my PC and MTKFLASH loaded up and showed me a Menu with all current selections including my VIA chipset...

5) Powered OFF Xbox 360... and waited ATLEAST 5 seconds after I turned off the system (This is cause right after you turn off you can still here the motor from the fan working.. just wait for that too turn off...)

6) Pressed button corresponding to my VIA chipset and got the usual error "Port: 10d8, Master/Slave: a0" (you will get the same or a slight variation of the same error...)

7) Started counting to 10 right after I pressed it...
(Now realize this people, its not a regular count to ten.. I tried many tens, fast, slow, clock ticks, stopwatch, and all didnt work.. I just after a while developed my own time speed for counting to ten.. Like I said, its not an exact 10 that you can time with a watch or stop watch as that DIDNT work for me.. But who knows it just might work for you! Mine was more like a 1,1,2,2,3,3 ect.. counting outloud kinda thing... You get the drift...)

8) After the 10 count, I turned on the Xbox 360 and the flashing started immediately...

Now this was the final method that I was using the last couple of times before it actually worked... If step 8 didn't work for me then I did the following...

(Extra Mini Sub Tuturial for when step 8 failed instead of flashed)

A - I would press escape so that the MTKFLASH would quit and I would be back at the DOS Prompt..
B - I would turn off my 360 (and wait 5 sec or more till the fan turned off)
C - Once the 360 turned off I would then type MTKFLASH w /m /sata orig.bin but DIDN'T hit enter yet (as I did in step 2)...
D - I would then power up my Xbox 360 till it got to the main menu, and pressed ENTER on the PC.. If the selections showed my VIA chipset then I would repeat steps 5 to 8 from above again...
E - If it didnt I would repeat the process from Step A (in this mini sub tuturial) until my VIA chipset showed in the list.. After it showed then I would repeat steps 5-8 from above (the main tuturial)...

Now remember this.. For some it might work right away.. For others it might take HOURS, DAYS, or even WEEKS... Some may NEVER do it.. There is not a GUARANTEED guide that will get yours to work.. There are MANY methods... Some might work for you, others might not... TRY ALL OF THEM.. Research and attempt all the methods!! The key to getting this to work is to HAVE PATIENCE and not to expect it to work right away... You will frustrate yourself.. You will want to give up.. But keep trying..
Title: Saving A Bricked Samsung After Bad Flash.
Post by: IceMatrix8 on January 17, 2007, 07:51:00 AM
QUOTE(amshaggy @ Jul 19 2006, 04:25 AM) View Post

i have the via6421l sata card and managed to read my orig firmware no probs. went to flash and floppy gave up after bank 1. evertytime i switch on the xbox to re-flash the green light just blinks. my sata card doesnt give me the option to chose 1 or 2 it just does it. but wehn i try to reflash the light just blinks on the 360 and nothing happens just sit at master/slave a0. tr to press escape and try again but the whole pc freezes. is there anyway i can get round this any help would be much appreciated?

btw its a sammy drive.


i have the same problem...
when i press 1 to flash my drive the pc freezes and then restarts...what did you do to solve this problem??? please help////
Title: Saving A Bricked Samsung After Bad Flash.
Post by: conners on February 03, 2007, 03:46:00 AM
Please Help!

I`ve got hold of a MS25 drive, im using an aliM5283 sata card, i used xtreme boot maker and managed to dump my orig.bin file 4 times to check it was working and that i got the same key back, now the problem, i got xtreme 5.2a, added my drive key, added it to my floopy disc, and wrote the command line, the drive started to flash and just stopped at 40% now i cant detect my samsung drive at all, is there anything i can do?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: cjg26 on February 05, 2007, 05:44:00 PM
I'm having a terrible problem myself with a bad flash on a TS-H943 ms25 drive (Manufactured May 10, 2006 but doesn't have any of the ms28 problems).  I've previously flashed it over 25 times at least with no probs but all of a sudden the last time i flashed it I got a floppy disk read error after the 2nd of 4 banks were complete.  I've tried every method I can find to recover it but nothing seems to work.  The last working firmware on the drive was Xtreme52A and I was in the process of flashing Xtreme52B to help the drive read cheaper media.  I've been flashing the drive with a Gigabyte motherboard (Intel 945 express chipset), but I also have a via chipset sata pci card which I've been using to try the recovery and mtkflash has been edited to work with the via chipset.  I even managed to get the enable0800 DVD in the drive but that doesn't help because the drive doesn't spin up when powered on so people who have hopes that will work can scratch that.  I'm figuring the success stories of people with this problem are coming from people who flashed over the drive's original firmware and not over a version of Xtreme firmware which has firmguard (or whatever it's called) embedded to keep the firmware from being altered unless the drive is in enable0800 mode.  And after bricked, the drive cannot enter enable0800 mode because the DVD won't spin up........thus I figure is my problem.  When I attempt to flash with the recovery method the drive needs to =70 (whatever this means) and mine either =80 or 00.  Has anyone had success with an eeprom programmer on a bricked drive chip?  I figure that's my last option if it's possible.  I have the chip without the gew.  I'm desperate so any help is appreciated.  Thanks!
Title: Saving A Bricked Samsung After Bad Flash.
Post by: IateMIc on April 22, 2007, 08:50:00 AM
I always get   Port/ B000, Master/Slave/ a0  when I try ILLPLEASA methode.
What do I have to do?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Mi|enko on June 01, 2007, 03:59:00 AM
QUOTE(XboX-RoxX @ Oct 22 2006, 01:12 PM) View Post

well hi again im such a happy chappy i could fly lol
my xbox360 is ALIVE!!!!

this is wut i had to do butn the enable0800.iso to DVD+R Dual Layer Burner LG Super Multi 16x Dual Layer
media RiVision DVD+R DL 2.4x 8.5GB 240mins loaded CLONEDVD loaded the enable0800.iso
butnet it @ 2.4x
was bangin my head against the wall getting no where trying to reflash after flashing with xtreme41a.bin
messed up key with hex editor after flash wouldnt read originals or backups
after chatting with a friend of a friend on msn he told me to
Make BOOT Floppy add mtkflash.exe and mtkflash.typ and add my original FW orig.bin
i did this
then i booted pc
booted xbox
put in the enable0800 dvdr and let it run for 10-15 secs
have matkflash w /m firmware.bin ready to hit enter
once 10-15 secs is up eject the dvrom and press enter at same time
then select 1 which was my pri master sata and bingo it was flashing my dvdrom all went ok
put appropriate cables back etc tested to boot original working fine
then i wasnt happy cos i wanted it hackd tongue.gif
so i had the version xtreme3.3
i used the make x33.bin.bat with my orig.bin in same dir
double clicked make x33.bin.bat
hey presto it created my bin file
X33.bin
now onto floppy with this new FW binfile X33.bin and mtkflash etc
boot xbox
boot pc
dos typed
mtkflash w /m X33.bin
return
select 1 for my sata
bingo flashing procedure begins and completes nicely
put back together and woohoo my originals boot no problems
only sad thing is i used my last dvdr on burning the enable0800.iso lmao so now have to wait till tomorrow for the real momenyt of truth will update the post etc as and when
im sooooo damn happy this tutorial also helped me bigtime i was on the right track just i had to reset mine due to 41a 41b having FWGuard and cannot read / write an new / old FW without doing the dvdr with enable0800 tongue.gif didnt see much info on the 0800 method and there is a hell of a lot of tutorials etc some are very good some just plain old confuse ya remeber best help and learning is help of a friends who knows peace till next time
smile.gif
XboX-RoxX U Know It Does!!!!!

Dude.  I ****ing love you.  lol  I've been screwing with the thing for 3 hours, fearful that my wife might wake up and see my 360 dismantled on the floor and tears streaming down my face.  I used the enable0800 and it fixed it in 3 seconds flat.  Thanks bud.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: ExiZ on June 01, 2007, 05:16:00 AM
thread dredge or what, just use the 10 second trick, no need for 0800 anymore, most of these old tutorials are outdated now with the newer techniques and bringing them to the front will only cause people more grief tbh
Title: Saving A Bricked Samsung After Bad Flash.
Post by: hollowman231 on October 03, 2007, 04:13:00 PM
I have a samsung drive with F/W ms25 I download the ixtrem12.bin to flash to my drive. The flash went bad and now I get error 65. I need to know how to get it back so I can try again.  I have the orig.bin file on my flash card and I load into dos from that. The post from above said to enter mtkflash w /m /sata orig.bin and hit enter. I have tried this many times and each time it comes up as no drive detected. Can anyone help me with this?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: candp on October 22, 2007, 07:46:00 AM
QUOTE(hollowman231 @ Oct 3 2007, 11:13 PM) View Post

I have a samsung drive with F/W ms25 I download the ixtrem12.bin to flash to my drive. The flash went bad and now I get error 65. I need to know how to get it back so I can try again.  I have the orig.bin file on my flash card and I load into dos from that. The post from above said to enter mtkflash w /m /sata orig.bin and hit enter. I have tried this many times and each time it comes up as no drive detected. Can anyone help me with this?

i have excact same problem as you mate but with 3 samsung drives they all seemed to flash ok weith 1.2 but when plugged in get error 65 now i can not get wondows to recognise the drives get no disc detected and non of them eject i am ripping my hair out trying to sort these out as i only doing them for a favour to a friend any advice much appreciated
Title: Saving A Bricked Samsung After Bad Flash.
Post by: cypher21 on October 22, 2007, 08:07:00 AM
QUOTE(candp @ Oct 22 2007, 04:22 PM) View Post

i have excact same problem as you mate but with 3 samsung drives they all seemed to flash ok weith 1.2 but when plugged in get error 65 now i can not get wondows to recognise the drives get no disc detected and non of them eject i am ripping my hair out trying to sort these out as i only doing them for a favour to a friend any advice much appreciated


WTF, you've fucked up 3 samsung drives!! You are THE man, i don't know anyone who could manage that!

did you manage to read the firmware and got all the original firmwares of those drives?
if so, do the 10s trick and flash them back to original!

What sata chipset do you have?
and WTF are you doing with samsung drives in windows?????? you need to flash them in DOS
Title: Saving A Bricked Samsung After Bad Flash.
Post by: WoofyBear on October 22, 2007, 10:40:00 AM
QUOTE(candp @ Oct 22 2007, 10:22 AM) View Post

i have excact same problem as you mate but with 3 samsung drives they all seemed to flash ok weith 1.2 but when plugged in get error 65 now i can not get wondows to recognise the drives get no disc detected and non of them eject i am ripping my hair out trying to sort these out as i only doing them for a favour to a friend any advice much appreciated


I am in a similar situation with the Error 65 screen. The ms28 will not spin up at all. I have tried the 10 second trick and various others with no success. I have the connectivity kit and trying to use it to even just open the drive door doesn't work. My pc reports that the drive has no firmware installed at all. I have flashed many drives in the past, both Samsung and Hitachi's and have never run into anything like this before.

Is there any way at all to get this drive to reflash? I have another ms28 drive that is working perfectly and flashed with 1.2c . Can I somehow use this drive to kick start the other into accepting flashes. Just for the record not only will the drive not accept flashes it also won't let me read anything off it either.

Appreciate if anyone has any help for this or can point me in the right direction.

 blink.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: candp on October 22, 2007, 01:58:00 PM
QUOTE(cypher21 @ Oct 22 2007, 03:43 PM) *

WTF, you've fucked up 3 samsung drives!! You are THE man, i don't know anyone who could manage that!

did you manage to read the firmware and got all the original firmwares of those drives?
if so, do the 10s trick and flash them back to original!

What sata chipset do you have?
and WTF are you doing with samsung drives in windows?????? you need to flash them in DOS



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!

This post has been edited by candp: Oct 22 2007, 09:01 PM
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Carlitosbaby on October 22, 2007, 03:18:00 PM
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.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: candp on October 22, 2007, 03:39:00 PM
QUOTE(Carlitosbaby @ Oct 22 2007, 10:18 PM) View Post

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 sad.gif
Title: Saving A Bricked Samsung After Bad Flash.
Post by: two-rok on October 22, 2007, 05:52:00 PM
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?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Hercules Man on October 22, 2007, 05:39:00 PM
QUOTE(two-rok @ Oct 23 2007, 12:52 AM) View Post

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
Title: Saving A Bricked Samsung After Bad Flash.
Post by: two-rok on October 23, 2007, 03:56:00 AM
QUOTE(Hercules Man @ Oct 23 2007, 01:15 AM) View Post

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
Title: Saving A Bricked Samsung After Bad Flash.
Post by: mookie_gr on October 23, 2007, 10:12:00 AM
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?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: two-rok on October 23, 2007, 10:33:00 AM
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
Title: Saving A Bricked Samsung After Bad Flash.
Post by: two-rok on October 23, 2007, 02:06:00 PM
QUOTE(two-rok @ Oct 23 2007, 11:32 AM) View Post

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?
Title: Saving A Bricked Samsung After Bad Flash.
Post by: two-rok on October 23, 2007, 02:36:00 PM
QUOTE(two-rok @ Oct 23 2007, 09:42 PM) View Post

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.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: mookie_gr on October 23, 2007, 04:33:00 PM
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
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Hercules Man on October 23, 2007, 10:00:00 PM
QUOTE(two-rok @ Oct 23 2007, 10:12 PM) View Post

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
Title: Saving A Bricked Samsung After Bad Flash.
Post by: two-rok on October 25, 2007, 10:40:00 AM
QUOTE(Hercules Man @ Oct 24 2007, 05:36 AM) View Post

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
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Hercules Man on October 25, 2007, 11:54:00 AM
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 sad.gif, already done 4 360's with that fix, was hoping i dont have to do my own.


H MAn

Title: Saving A Bricked Samsung After Bad Flash.
Post by: SuperStition on December 27, 2007, 03:53:00 PM
Will this work on a Hitachi? I have no drive key, I would like to extract it.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: swampy1111 on March 20, 2008, 04:01:00 PM
QUOTE(SuperStition @ Dec 28 2007, 01:29 AM) View Post

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
Title: Saving A Bricked Samsung After Bad Flash.
Post by: XBX0 on January 13, 2009, 06:52:00 PM
I need help getting my samsung tsh943 working again it doesnt power up no spin up nothing... it gives me a status x80 not x70 mtkflash or dosflash wont work it just shows on what ort its on and wont recognize it
Title: Saving A Bricked Samsung After Bad Flash.
Post by: XBX0 on January 14, 2009, 03:15:00 AM
I can get a status 0x70 in windows but the write will fail but in dos I get a 0x80 with my samsung tsh943
Title: Saving A Bricked Samsung After Bad Flash.
Post by: bneese on October 09, 2010, 10:41:00 PM
Here is my story. My MS25 is dead. I can't even get it to restore to the original firmware. I have an MS28 that I have tried to use JungleFlasher and copy the MS25 firmware and spoof the original MS28 firmware to use the MS25 key. Nothing seems to work. the MS28 says it has the correct key, but when I try and play a game it spins a couple times and then says open tray.

Please help.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: bneese on October 10, 2010, 09:25:00 AM
QUOTE(bneese @ Oct 10 2010, 05:41 AM) View Post

Here is my story. My MS25 is dead. I can't even get it to restore to the original firmware. I have an MS28 that I have tried to use JungleFlasher and copy the MS25 firmware and spoof the original MS28 firmware to use the MS25 key. Nothing seems to work. the MS28 says it has the correct key, but when I try and play a game it spins a couple times and then says open tray.

Please help.


Here is my log info from JungleFlasher. The Key is correct I am so frustrated.

Firmware is:  iXtreme LT                      
Loading firmware file C:\Users\Brian Neese\Downloads\Samsung_iXtreme_LT_v1.0\Sam_CFW.bin
MD5 hash:  13dc153256fb835d703d3de1158cc07f
Inquiry string found
Identify string found
Drive key @ 0x401A
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Spoofed As:    [TSSTcorpDVD-ROM TS-H943Ams25]
Firmware is:  iXtreme LT                      

Getting Status from port 0xDF00
Parallel flash found with Status 0x70
Writing target buffer to flash
Erasing Bank 0: ................
Writing Bank 0: ................
Erasing Bank 1: ................
Writing Bank 1: ................
Erasing Bank 2: ................
Writing Bank 2: ................
Erasing Bank 3: ................
Writing Bank 3: ................

Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Write verified OK !


Getting Status from port 0xDF00
Parallel flash found with Status 0x70

Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Loading firmware from buffer
Inquiry string found
Identify string found
Drive key @ 0x401A
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Spoofed As:    [TSSTcorpDVD-ROM TS-H943Ams25]
Firmware is:  iXtreme LT                      
Key database updated


Loading MTK_Flash source file
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Buzzcut on October 10, 2010, 10:32:00 AM
As you've been told in your other thread, get a new drive.
Title: Saving A Bricked Samsung After Bad Flash.
Post by: Haygar on October 10, 2010, 05:32:00 PM
Or, if the ms25 is dead because of the pcb and not the laser, if you slot the ms28 board in with your desired FW and the correct key you should be good to go. wink.gif