Open mjmeans opened 6 years ago
I haven't tested it in quite some time - let me know your results.
Ah. Sorry. I saw your readme update from January this year that you were working on updating it to the current version of Windows IoT. I was wondering if you had verified that it works and maybe just not updated the repo yet.
Unfortunately not, it's still just an item on my to-do list.
On Oct 13, 2017 10:55, "mjmeans" notifications@github.com wrote:
Ah. Sorry. I saw your readme update from January this year that you were working on updating it to the current version of Windows IoT. I was wondering if you had verified that it works and maybe just not updated the repo yet.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/t0x0/random/issues/8#issuecomment-336523904, or mute the thread https://github.com/notifications/unsubscribe-auth/AIGzYlpYKiw-Qs89uU2pwwPMR_PxbmHRks5sr6QBgaJpZM4P4osn .
@t0x0 could you provide some clues as to what modifications are needed?
Some of us may be able to fork and start work on it for PRs.
As I recall, the original RPi FFU image didn't match the specification (https://docs.microsoft.com/en-us/windows-hardware/manufacture/mobile/ffu-image-format), and the code was written to successfully extract it anyway. I'm assuming that the future images actually conform to the spec, and so my code is broken. I apologize, but I won't be able to offer much more assistance until I can find time to dig into the details of the actual issues.
I've successfully followed this method using DISM for other non-RPi boards to flash the flash.ffu image:
https://docs.microsoft.com/en-us/windows/iot-core/connect-your-device/dism
So, perhaps if the flash.ffu file was created to the Microsoft "FFU specs", the above method using DISM will be fine.
I instruct consumers not on Windows 10 to just install an evaluation of Windows 10 inside of a VM, and attach the USB device from there. the ISO is freely downloadable from Microsoft. On one hand, it keeps from having to install Python. On the other hand, it's install Windows 10 just to write a USB device! lol
Dism isn't available to python under Raspbian. So that defeats the purpose of using a custom NOOBS under Raspbian or other Linux to handle the flash recovery.
DISM consistently functions in my experience (as long as WSL and Ubuntu aren't installed on your installation of Win10, in which case you would receive Error 5, Access Denied.) FFU2IMG is intended specifically for situations where dism is either unavailable or undesired, so recommending dism isn't particularly germane to the discussion, although perhaps it will help someone looking for more information.
Hello, I'm wondering if this works with the current versions of Windows IoT?
My goal is to make a NOOBS os image from a custom flash.ffu that can be used as a factory restore appliance for a Windows IoT running on RPi3.