www.makemkv.com

Yeah, I had that issue, but repeatedly typing dosflash solved that.

Dosflash only asked me what to do with the flash after it detected the drive (which was the case in 10 tries out of 30). But everytime the drive was detected and I went for the next step, the readout failed with the error message I gave.

Are you certain that when you "Press the relative number of the detected device (...) and press "R..."', that you are using the correct 'relative number'? It's been over a year, so I'm having trouble recalling what the output looked like.

Colindo wrote: Mon Nov 12, 2018 12:02 pm Yeah, I had that issue, but repeatedly typing dosflash solved that.

Dosflash only asked me what to do with the flash after it detected the drive (which was the case in 10 tries out of 30). But everytime the drive was detected and I went for the next step, the readout failed with the error message I gave.

If your having issues with dos flash use another method the easiest is the unlocked flasher it is not mentioned in this thread but it's out there look here at what I posted viewtopic.php?f=16&t=18251 or you can use the bootable pe/ 32 bit windows way the way you are trying is the most complicated

If I'm not mistaken, the unlocked flasher that you refer to does not work with my firmware 3.03. I tried that first and it gives the infamous "Write DRAM" error.
I will try the Windows PE edition, I guess.

@d00zah I am as sure as I can be, at least that was the number that had the Asus model name in it.

Colindo wrote:If I'm not mistaken, the unlocked flasher that you refer to does not work with my firmware 3.03. I tried that first and it gives the infamous "Write DRAM" error.
I will try the Windows PE edition, I guess.

@d00zah I am as sure as I can be, at least that was the number that had the Asus model name in it.

The whole point of the unlocked flasher is to shitcan 3.03 ASUS and 1.03 LG right?
Works better then I ever dreamed in the Windows 7 environment.


Sent from my iPhone using Tapatalk Pro

Hi guys,

I was more successful with the Windows environment, but it remains weird. With the normal dosflash32.exe, I received the same error as in DOS. I took a screenshot so that you can see what I mean. I then used the dosflash32_BH16NS40.exe, which was also created with the Windows bootable and it worked instantly. So I have my dumped firmware.

I then used the Data Mover with a clean 3.00 firmware, but my drive still rejects it when I try to flash the new firmware, still saying the DRAM write error. I attached the dumped firmware as txt-file, so maybe if someone would be so kind to convert it for me, that would be great. Just in case I made a mistake. My drive is the Asus BW-16D1HT. Any help would be appreciated.

You're on the wrong port dude, make sure it's 0X01F0 and channel reads "Primary"

Also are you using SATA 0 for the drive with nothing else plugged into any SATA port?

@Colindo,

Here is an ASUS 3.02 created for you using your dump file data. As others have said, make sure you are on port SATA 0.

Good luck

Thanks Marty,

so to get this right, I definitely need to be on SATA0 to read out the flash drive, even if I managed to get one using SATA1? Do I also need to be on the right port to flash it? Does it need to be an IDE connection only for the read-out, or also for the flash?

I'm not Marty but I've flashed 7 drives in the last hour and a half. The answer is yes, SATA 0 with your SATA controller set to IDE mode.

Colindo wrote: Sun Nov 18, 2018 4:51 pm Thanks Marty,

so to get this right, I definitely need to be on SATA0 to read out the flash drive, even if I managed to get one using SATA1? Do I also need to be on the right port to flash it? Does it need to be an IDE connection only for the read-out, or also for the flash?

you dont need to be on sata 0 or 1 mostly depends on motherboard im on port 3 and have flashed 50+ drives and never one writer error you do need IDE mode for dosflash if you were able to read the flash chip you are able to write it. think your main problem is that trash meme of a windows 7 pe image it has to many auto start auto driver config scripts and sometimes hides drives half way through you doing stuff i use win 10 pe but you can use any just make sure its 32 bit and in a mostly stock.

Billycar11 wrote: Mon Nov 19, 2018 12:18 am

Colindo wrote: Sun Nov 18, 2018 4:51 pm Thanks Marty,

so to get this right, I definitely need to be on SATA0 to read out the flash drive, even if I managed to get one using SATA1? Do I also need to be on the right port to flash it? Does it need to be an IDE connection only for the read-out, or also for the flash?

you dont need to be on sata 0 or 1 mostly depends on motherboard im on port 3 and have flashed 50+ drives and never one writer error you do need IDE mode for dosflash if you were able to read the flash chip you are able to write it. think your main problem is that trash meme of a windows 7 pe image it has to many auto start auto driver config scripts and sometimes hides drives half way through you doing stuff i use win 10 pe but you can use any just make sure its 32 bit and in a mostly stock.

LOL Bill I knew that was coming. How is it we all keep grabbing the same horrendous Windows 7 PE?

jonghotti wrote: Mon Nov 19, 2018 1:01 am LOL Bill I knew that was coming. How is it we all keep grabbing the same horrendous Windows 7 PE?

because that is what is linked on the first page and people think only that one will work but any 32bit windows or pe will work from xp-10 maybe farther back but have not tested

Hi

I have an Asus BC-12D2HT which has FW 3.01. On top of that my PCs don't offer IDE mode, just RAID instead of AHCI.

Is there any way I can downgrade this sucker? If not which drives can I buy that should work out of the box with UHD discs for MakeMKV?