xboxscene.org forums

Pages: 1 2 3 [4] 5 6 ... 12

Author Topic: Saving A Bricked Samsung After Bad Flash.  (Read 950 times)

amshaggy

  • Archived User
  • Newbie
  • *
  • Posts: 3
Saving A Bricked Samsung After Bad Flash.
« Reply #45 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.

Logged

Keltik

  • Archived User
  • Newbie
  • *
  • Posts: 44
Saving A Bricked Samsung After Bad Flash.
« Reply #46 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
Logged

Andy Hewitt

  • Archived User
  • Jr. Member
  • *
  • Posts: 82
Saving A Bricked Samsung After Bad Flash.
« Reply #47 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)


Logged

Andy Hewitt

  • Archived User
  • Jr. Member
  • *
  • Posts: 82
Saving A Bricked Samsung After Bad Flash.
« Reply #48 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.
Logged

amshaggy

  • Archived User
  • Newbie
  • *
  • Posts: 3
Saving A Bricked Samsung After Bad Flash.
« Reply #49 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.

Logged

Keltik

  • Archived User
  • Newbie
  • *
  • Posts: 44
Saving A Bricked Samsung After Bad Flash.
« Reply #50 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
Logged

sython

  • Archived User
  • Newbie
  • *
  • Posts: 8
Saving A Bricked Samsung After Bad Flash.
« Reply #51 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
Logged

Andy Hewitt

  • Archived User
  • Jr. Member
  • *
  • Posts: 82
Saving A Bricked Samsung After Bad Flash.
« Reply #52 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.
Logged

SicilianBoy

  • Archived User
  • Newbie
  • *
  • Posts: 6
Saving A Bricked Samsung After Bad Flash.
« Reply #53 on: July 27, 2006, 02:46:00 PM »

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

Andy Hewitt

  • Archived User
  • Jr. Member
  • *
  • Posts: 82
Saving A Bricked Samsung After Bad Flash.
« Reply #54 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.
Logged

R1zz

  • Archived User
  • Newbie
  • *
  • Posts: 1
Saving A Bricked Samsung After Bad Flash.
« Reply #55 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
Logged

Andy Hewitt

  • Archived User
  • Jr. Member
  • *
  • Posts: 82
Saving A Bricked Samsung After Bad Flash.
« Reply #56 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.
Logged

chinozzz

  • Archived User
  • Jr. Member
  • *
  • Posts: 55
Saving A Bricked Samsung After Bad Flash.
« Reply #57 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
Logged

davechann

  • Archived User
  • Newbie
  • *
  • Posts: 2
Saving A Bricked Samsung After Bad Flash.
« Reply #58 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
Logged

Andy Hewitt

  • Archived User
  • Jr. Member
  • *
  • Posts: 82
Saving A Bricked Samsung After Bad Flash.
« Reply #59 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.
Logged
Pages: 1 2 3 [4] 5 6 ... 12