www.makemkv.com

MakeMKV support forum
https://forum.makemkv.com/forum/

did i brick my drive? buffalo

https://forum.makemkv.com/forum/viewtopic.php?f=16&t=28254

Page 1 of 1

did i brick my drive? buffalo

Posted: Mon May 23, 2022 9:01 pm
by pupster
C:\Program Files (x86)\MakeMKV>makemkvcon64.exe f --all-yes -d F: rawflash enc -i \t\HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin

Reading input file \t\HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin
Flashing flags = 0x0 : 0 0 0 0 : ---- ---- ---- ----
Sending image in encrypted format
Current Drive ID: BUFFALO_Optical_Drive_BU13_212009251100_MOFL7EA3249
Ready to write drive flash memory. (auto confirmed)
Operation started: Sending flash image to drive
100% Operation finished
Operation started: Programming flash
100% Operation finished

Program Flash NG 06/29/00

Command produced error code 0x8f062900


now the drive isn't recognized by windows and the tray isn't opening....

Re: did i brick my drive? bullalo

Posted: Tue May 24, 2022 12:59 am
by Billycar11
likely not unplug the drive for a min plug it back in choose recovery in sdftool gui choose the wrong firmware then the right follow the steps and wait for it to be done is it should come back to life if you let it sit long with the wrong firmware you could have burned the laser out.

Re: did i brick my drive? bullalo

Posted: Tue May 24, 2022 4:26 am
by pupster
thanks...

well...i tried to load sdftool flasher and it's giving this "Unhandled exception has occurred in your application." when i select my drive:

when i try to select the wrong firmware (or the right firmware), the recover drive option is greyed out. i didn't use sdftool the first time when i flashed the wrong firmware as it was giving the same/similar error before...

what i ignore the initial error i sdftool and try to write the correct firmware (i can't recover as it's greyed out), i get "command produced error code 0x8f05c103" and sdftool stops

Error log from sdftool when i try to select my bricked drive...:


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at SDFtool_Flasher_Updated.Form1.comboBox_DriveList_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
System.Private.CoreLib
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
SDFtool Flasher
Assembly Version: 1.3.3.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Windows.Forms
Assembly Version: 6.0.2.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Windows.Forms.Primitives
Assembly Version: 6.0.2.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ComponentModel.Primitives
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.InteropServices
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Drawing.Primitives
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections.Specialized
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Drawing.Common
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Threading
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Diagnostics.TraceSource
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Diagnostics.Process
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
Microsoft.Win32.Primitives
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ComponentModel.EventBasedAsync
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Threading.Thread
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ComponentModel.TypeConverter
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Numerics.Vectors
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Memory
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ComponentModel
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Resources.Extensions
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Drawing
Assembly Version: 6.0.2.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ObjectModel
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Linq
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.Serialization.Formatters
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections.Concurrent
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
Microsoft.Win32.SystemEvents
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections.NonGeneric
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Configuration.ConfigurationManager
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Private.Uri
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.InteropServices.RuntimeInformation
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Security.Cryptography.Algorithms
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Security.Cryptography.Primitives
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Xml.ReaderWriter
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Private.Xml
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Text.RegularExpressions
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Net.WebClient
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Text.Encoding.Extensions
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Xml.XmlSerializer
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
Microsoft.Win32.Registry
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.CompilerServices.Unsafe
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.Loader
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Diagnostics.StackTrace
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Reflection.Metadata
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections.Immutable
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Threading.ThreadPool
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------

************** JIT Debugging **************

Re: did i brick my drive? bullalo

Posted: Tue May 24, 2022 5:23 am
by MartyMcNuts
pupster wrote: ↑
Tue May 24, 2022 4:26 am
 thanks...

well...i tried to load sdftool flasher and it's giving this "Unhandled exception has occurred in your application." when i select my drive:

when i try to select the wrong firmware (or the right firmware), the recover drive option is greyed out. i didn't use sdftool the first time when i flashed the wrong firmware as it was giving the same/similar error before...

what i ignore the initial error i sdftool and try to write the correct firmware (i can't recover as it's greyed out), i get "command produced error code 0x8f05c103" and sdftool stops

Error log from sdftool when i try to select my bricked drive...:


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at SDFtool_Flasher_Updated.Form1.comboBox_DriveList_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
System.Private.CoreLib
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
SDFtool Flasher
Assembly Version: 1.3.3.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Windows.Forms
Assembly Version: 6.0.2.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Windows.Forms.Primitives
Assembly Version: 6.0.2.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ComponentModel.Primitives
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.InteropServices
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Drawing.Primitives
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections.Specialized
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Drawing.Common
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Threading
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Diagnostics.TraceSource
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Diagnostics.Process
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
Microsoft.Win32.Primitives
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ComponentModel.EventBasedAsync
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Threading.Thread
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ComponentModel.TypeConverter
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Numerics.Vectors
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Memory
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ComponentModel
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Resources.Extensions
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Drawing
Assembly Version: 6.0.2.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.ObjectModel
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Linq
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.Serialization.Formatters
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections.Concurrent
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
Microsoft.Win32.SystemEvents
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections.NonGeneric
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Configuration.ConfigurationManager
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Private.Uri
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.InteropServices.RuntimeInformation
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Security.Cryptography.Algorithms
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Security.Cryptography.Primitives
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Xml.ReaderWriter
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Private.Xml
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Text.RegularExpressions
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Net.WebClient
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Text.Encoding.Extensions
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Xml.XmlSerializer
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
Microsoft.Win32.Registry
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.CompilerServices.Unsafe
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Runtime.Loader
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Diagnostics.StackTrace
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Reflection.Metadata
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Collections.Immutable
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
System.Threading.ThreadPool
Assembly Version: 6.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------

************** JIT Debugging **************
You need to be running a recent version of Windows 10 64 bit and have MakeMKV (v1.15.3 or above) installed in the default directory to ue SDFtool Flasher.

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 12:03 am
by pupster
well i tried putting the new replacement drive on a windows 10 x64 machine and i got the same error; unhandled exception using sdftool (latest) and latest make mkv installed.

ideas?

can i still flash using the command line tool, or do i risk bricking my drive again? i think i used the wrong firmware to flash the first time around....

it's a buffalo "BU13" is the firmware version... BRUHD-PU3-BK

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 12:38 am
by MartyMcNuts
pupster wrote: ↑
Sat May 28, 2022 12:03 am
 well i tried putting the new replacement drive on a windows 10 x64 machine and i got the same error; unhandled exception using sdftool (latest) and latest make mkv installed.

ideas?

can i still flash using the command line tool, or do i risk bricking my drive again? i think i used the wrong firmware to flash the first time around....

it's a buffalo "BU13" is the firmware version... BRUHD-PU3-BK
Did you try running it as an administrator??

You should be able to use the command line tool. The firmware really depends on what you want to end up on and what ripping software you use.

In any scenario, you want to flash BU40N 1.03-MK first. You could leave the drive on this firmware if you like. If you want to use a different firmware, from here you could flash to:
  • Buffalo BU12-MK
  • BU40N 1.00
BU40N 1.03-MK and BU12-MK work with MakeMKV (and should work with AnyDVDHD beta version).
BU40N 1.00 works with the above plus other software such as DVDFab etc..

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 2:10 am
by pupster
yup running as admin; tried to upload video but it won't let me attach

so i'm not seeing the 1.03 mk in the all firmware packet...so you're saying i DONT want to do this?

makemkvcon64.exe f --all-yes -d F: rawflash enc -i \t\HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin


since that's the 1.02 firmware......



i see THIS post and a file linked in the first post. is that file the correct 1.03 MK?

viewtopic.php?f=19&t=19422

it doesn't say it's 1.03 mk just 1.03nm...:

HL-DT-ST-BD-RE_BU40N-1.03-NM00000-211810241934.zip
(1.27 MiB) Downloaded 1927 times

download/file.php?id=1937

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 2:57 am
by MartyMcNuts
pupster wrote: ↑
Sat May 28, 2022 2:10 am
 yup running as admin; tried to upload video but it won't let me attach

so i'm not seeing the 1.03 mk in the all firmware packet...so you're saying i DONT want to do this?

makemkvcon64.exe f --all-yes -d F: rawflash enc -i \t\HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin


since that's the 1.02 firmware......

HELL NO!!!!!! HL-DT-ST-BD-RE_WH16NS60-1.02-NM00100-211810291936.bin is desktop firmware for a desktop drive. NEVER, EVER flash desktop firmware to a slim drive.

pupster wrote: ↑
Sat May 28, 2022 2:10 am
 i see THIS post and a file linked in the first post. is that file the correct 1.03 MK?

viewtopic.php?f=19&t=19422

it doesn't say it's 1.03 mk just 1.03nm...:

HL-DT-ST-BD-RE_BU40N-1.03-NM00000-211810241934.zip
(1.27 MiB) Downloaded 1927 times

download/file.php?id=1937

HL-DT-ST-BD-RE_BU40N-1.03-NM00000-211810241934 is the correct firmware. We all say MK as it's far easier than NM0000......

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 5:16 am
by pupster
right i actually meant to say...


makemkvcon64.exe f --all-yes -d F: rawflash enc -i \t\HL-DT-ST-BD-RE_BU40N-1.03-NM00000-211810241934.bin

that would be the CORRECT way to manually flash from the command prompt since sdftool is giving me errors?

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 5:19 am
by Billycar11
pupster wrote: ↑
Sat May 28, 2022 5:16 am
 right i actually meant to say...


makemkvcon64.exe f --all-yes -d F: rawflash enc -i \t\HL-DT-ST-BD-RE_BU40N-1.03-NM00000-211810241934.bin

that would be the CORRECT way to manually flash from the command prompt since sdftool is giving me errors?
read the guide or get my or martys automated flasher

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 5:56 am
by pupster
i read the guide up to the point where i realized i effed up (copied the wrong firmware) and i watched the video; i just can't get the sdftool to open the buffalo drive on my systems. from looking at the forums it seems there may be a problem flashing it w/in the default enclosure. anyone know if i for sure have to remove it and put it in another enclosure like the vantec NST-510S3-BK that does support usb flashing?

i think marty's automated flasher IS the sdftool, isn't it? that's what not working... [got from this link: viewtopic.php?f=16&t=22896]

I'm using SDFtool 1.3.3 and it says NET framework 4.7.2 is already installed; i'm using windows 10

in the enclosed video, even though it looks like the drive flashed, when i load it up in makemkv, it still shows it's on the same BU13 platform...and encrypted

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 6:13 am
by pupster
figured it out...the checkbox for the encrypted option wasn't showing (see video) - dunno why the font is not letting me see it, but clicking on the word encrypted allowed me to see part of a green check mark, and after that was ticked it worked...thanks all

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 6:47 am
by pupster
MartyMcNuts wrote: ↑
Sat May 28, 2022 12:38 am
In any scenario, you want to flash BU40N 1.03-MK first. You could leave the drive on this firmware if you like. If you want to use a different firmware, from here you could flash to:
  • Buffalo BU12-MK
  • BU40N 1.00
BU40N 1.03-MK and BU12-MK work with MakeMKV (and should work with AnyDVDHD beta version).
BU40N 1.00 works with the above plus other software such as DVDFab etc..
Thanks again sir. I did downgrade to BU40N 1.00. Seems like there's no reason to install BU12-MK (even though this is a "Buffalo drive" since that has less capability vs. the stock BU40N 1.00?

Re: did i brick my drive? buffalo

Posted: Sat May 28, 2022 10:50 am
by MartyMcNuts
pupster wrote: ↑
Sat May 28, 2022 6:47 am
MartyMcNuts wrote: ↑
Sat May 28, 2022 12:38 am
In any scenario, you want to flash BU40N 1.03-MK first. You could leave the drive on this firmware if you like. If you want to use a different firmware, from here you could flash to:
  • Buffalo BU12-MK
  • BU40N 1.00
BU40N 1.03-MK and BU12-MK work with MakeMKV (and should work with AnyDVDHD beta version).
BU40N 1.00 works with the above plus other software such as DVDFab etc..
Thanks again sir. I did downgrade to BU40N 1.00. Seems like there's no reason to install BU12-MK (even though this is a "Buffalo drive" since that has less capability vs. the stock BU40N 1.00?
Less software compatibility, yes.
All times are UTC
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited