While trying to update the firmware on my samsung drive to 1.51 using jungleflasher in vista, my computer froze halfway through writing, leaving what seems to be a dead drive (can't get it to retun 0x70) so i bought a replacement samsung (ms28) drive on ebay.
My question is, since i already have the firmware prepared for my dead drive, can i just flash my new one with the same firmware since the keys from my old drive are already written in to that firmware?
Just wanted to check before i go ahead and try it.
No, it was an MS25 when i got it but i thought that once it was flashed (i'd already put the last ixtreme on it before 1.51 came out) then it would act like an ms28 so it wouldn't make a difference. Like i said, i think!
Edit: ok, i found the thing in manual spoofing where you can select what type of firmware to spoof as so i changed it to ms28 (to match the new drive) so i now have 2 firmwares, one spoofed as ms25 and the other as ms28, which one shall i use?
Edit: Right, i've flashed it using the ms25 firmware that i tried flashing my old drive with when it froze thinking if it doesn't work i can just reflash it with the ms28 and it worked so thanks for your help leerage :)
now that you have a second samsung you can probally bring the dead one back to life if all that happened was a bad flash. I killed a few sammy's in my day but brought them back in dos. I don't remember my exact steps as I was just f'ing around trying to fix the ones I bricked. Anyway in a nut shell I used dosfash16 and read a good drive. Moved in the firmware from the dead drive into the folder from the one that I successfully read, and then flashed away at the dead drive. They seem to be fine now. I am sure I left out a few steps but if I get really board anytime soon I will intentionally brick a sammy and see if I can bring it back.Detailing my steps along the way....hmmm now that I think of it, the drive I read then bricked must have been erased. So I used a good drive to read then return the proper drive status dosflash expected, then swapped the drives and connected the bad one to the sata cable and flashed it. I think why I was successful as once dosflash was prepared by recieving a good drive status the blank/bricked drive doesn't have to be in any "vendor mode" or anything so it took the flash command.
Yeah i tried using dosflash 16 but still couldn't get it to return anything other than 0x80, tried opening the drive halfway and power cycling the drive during the return and all sorts of tricks. Not a bad idea to get it to return on the good drive and swap them over, also might give it a go if i get bored, a mates got a busted xbox it might come in handy for.
