xboxscene.org forums

Pages: 1 ... 8 9 [10] 11 12

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

goldguy27

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

Spidey29

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

goldguy27

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

ILLPLEASA

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

IceMatrix8

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

conners

  • Archived User
  • Full Member
  • *
  • Posts: 175
Saving A Bricked Samsung After Bad Flash.
« Reply #140 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?
Logged

cjg26

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

IateMIc

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

Mi|enko

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

ExiZ

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

hollowman231

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

candp

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

cypher21

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

WoofyBear

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

candp

  • Archived User
  • Newbie
  • *
  • Posts: 12
Saving A Bricked Samsung After Bad Flash.
« Reply #149 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
Logged
Pages: 1 ... 8 9 [10] 11 12