There was no 3.03 DE. There was briefly a 3.03 MK before they released 3.10.
I upgraded to 3.10 MK and downgraded to 3.02 DE without issue.
I haven't seen a 3.03 DE firmware?
Mike replaced the 3.03 MK firmware with 3.10 MK in the newest download pack. Let me know if you want to have the 3.03 MK. There was never a 3.03 DE, only a 3.02 DE
Thanks. I already had the 3.03 MK.
I can say that 3.03 MK doesn't work with DeUHD which only confirms what I expected before testing.
Do you think Mike might do another release that might make the mk firmware work with other third party software like DeUHD or maybe that a silly question and I could face some abuse for asking?
The sleep bug fix has nothing to do with mk. That's part of the 3.10 firmware that Asus put out. So I'm really not sure where you got that the mk patch has anything to do with that. The mk patch for the 3.10 firmware restores uhd friendly functionality and removes a new downgrade restriction that they added. That's it.
Do you think Mike might do another release that might make the mk firmware work with other third party software like DeUHD or maybe that a silly question and I could face some abuse for asking?
I don't want to confuse the issue but I will leave this info here in case someone was foolish enough to flash NON MK 3.10 or if you buy a drive in the future that comes with NON MK 3.10. This means the ORIGINAL unaltered 3.10 firmware. This CAN NOT be downgraded using the windows flasher tools and a DE firmware. They added additional protection against that.
So, if you find yourself in this situation, what do you do? Simple....flash MK 3.10. That WILL install over the top of original 3.10. Then you are able to use DE firmware to downgrade it further should you desire to.
Um, I don't think you understand the difference between the Windows flashers and dosflash if you're asking that question. Your theoretical "power loss scenario" could happen during a dosflash flash because it's UNSAFE. It's wiping the eeprom and replacing it with every part of the bin file directly. The Windows flasher does not use that method of flashing. It copies the firmware bin to the drive's memory and issues a "self-update" command. If that process fails, the drive goes into recovery mode meaning you simply need to flash it again. So no, your theoretical "corrupt flash" scenario does not exist in Windows. It is only possible in dosflash which is NOT a recommended flash method at this point.
Was wondering if anyone has the WH16NS40 SVC Code NS40 or WH14NS40 SVC Code NS40 bin file so I can try and flash back from NS50 to see if I can get it working again. Chances it might work are slim but won't know till I try.
Yes I know, I can't express well what asking.
OK so it doesn't have anything thing to do with SPI locking with certain firmwares.
I feared, after flashing official Asus 3.10 firmware, then trying to flash back Mike 3.10-mkv firmware (which possibly the official-3.10-Asus firmware could allow, but not lower versions), but then there would be a powerloss, and the (old) firmware parts outside being flashed over got corrupted, so that the LG or Asus uitlity won't recognize the drive anymore. I feared that akind of more-or-less SPI locking stayed, which new even could prohibit to use Dosflash (only to use with LG/Asus flasher), but now LG and Asus wouldn't work anymore, too, due to corrupted main firmware. Just remembering a case where a user needed to use Dosflash to recover firmware (he flashed wrong BH16NS40 NS50 fw/else afaik), the LG/Asus tools rejected, first dumping the remaining firmware (primarily to rescue the not-touched CB+encryption-data from those LG/Asus tools) with Dosflash, then use EEPROM data mover to transfer the CB+encryption over to a Clean firmware. And he flash that with Dosflash to rescue his drive.
I feared that even that rescue procedure would no longer be orking, because Asus did a harder kind of SPI locking.
But I probably just see too bad things where in reality no are
ThanksWon't work. Not the way you're thinking. The ONLY way I've seen anyone recover an NS40 code flashed with the NS50 firmware is by doing a really nasty process with dosflash. What sucks is it SHOULD be possible but for whatever reason once the drive is flashed with the NS50 firmware, it is prevented from flashing the NS40 firmware probably due to some protection in the firmware itself so people didn't brick their drive going the other way. If you want the process for rescuing it using dosflash, and assuming you have access to a machine that has a sata port that can be set to IDE mode, let me know.
Was wondering if anyone has the WH16NS40 SVC Code NS40 or WH14NS40 SVC Code NS40 bin file so I can try and flash back from NS50 to see if I can get it working again. Chances it might work are slim but won't know till I try.
Was wondering if anyone has the WH16NS40 SVC Code NS40 or WH14NS40 SVC Code NS40 bin file so I can try and flash back from NS50 to see if I can get it working again. Chances it might work are slim but won't know till I try.
Won't work. Not the way you're thinking. The ONLY way I've seen anyone recover an NS40 code flashed with the NS50 firmware is by doing a really nasty process with dosflash. What sucks is it SHOULD be possible but for whatever reason once the drive is flashed with the NS50 firmware, it is prevented from flashing the NS40 firmware probably due to some protection in the firmware itself so people didn't brick their drive going the other way. If you want the process for rescuing it using dosflash, and assuming you have access to a machine that has a sata port that can be set to IDE mode, let me know.
Don't get any error. All it does is pop out the tray and then nothing.Unfortunately both flashers will give an error if you try to flash back to NS40 firmware. The only way to get it working again is to connect your drive to SATA port 0 or 1, switch PC to IDE mode in bios and use DOSFLASH & EEPROM Data Mover.
1. Use Dosflash to dump the current NS50 firmware on device. This is important as it still contains your drive calibration info etc..
2. Use the EEPROM Data Mover with your firmware dump and the clean NS40 1.02 bin I have attached to create your new NS40 firmware.
3. Use Dosflash to erase drive.
4. Use Dosflash to write the newly created NS40 bin file.
5. Breathe! Your drive should be working again!!
I am working on the ASUS flasher, trying to get it to flash the NS40 firmware but I'm not having much luck. If you want, give this flasher a try first and let me know what error you get.