I don't think mis-flashing can brick the device such that you can't just flash it again. I've never read of such a thing, in any case, so I assume it would be rare.

Note you can boot an Ubuntu CD directly (no system install) and then do you thing from within its environment ("Live CD"). Keep that in mind if the Windows approach doesn't pan out.

Good luck!
Andy

This is what I got so far:

I have entered the following line at the command line (after copying the OS file into the same directory as the flasher, located at C:\Program Files (x86)\maemo\flasher-3.5>):

flasher-3.5 -F RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin -f -R

The response I got is the following:

flasher v2.5.2 (Sep 24 2009)

RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin: %m

No message about waiting for anything. My guess is this might be what they meant when they said this program is for the N900, not for the N810, am I correct?

I am downloading the Ubuntu iso image to try an USB stick install in the meantime.

Quick reply...
The Wiki says:
The Maemo Flasher-3.5 Tool is a command line utility that supports N900 device with Fremantle 5.x platform releases and N800, N810 and N810 WiMAX devices with Maemo Diablo 4.1.x platform releases.
That's why I hoped it might help. I haven't used it for a very long time, myself.
Though, since Windows 7 can cause problems, it should be easier for you to boot Ubuntu...
Best wishes.

Yes, I knew it 'should' support the N810. I have now tried both methods, both have failed so far.
vandys is trying to assist me privately with the Ubuntu method, so I sent him the full result of my Linux attempt. I may post it here if we cannot sort it out (it is a bit long).

Odd, I tried the Windows method again, and this time I got as far as the Waiting window, not sure why it failed before. Unfortunately, unlike the Ubuntu method, the program cannot see the device, keeps waiting. May try different ways again, not sure.

I did not try the double checks from Ubuntu, don't know how to do that.

EDIT: when I choose "Take Ownership" (Windows Explorer), it fails completely. When I choose "Open command window here", it runs as far as the Waiting window. Just in case it helps someone else.

Here is a copy of part of the reply I sent to vandys privately, the result of the Ubuntu attempt, in case someone else wants to chime in:

################################################## ###
ubuntu@ubuntu:~$ cd Downloads
ubuntu@ubuntu:~/Downloads$ dir
flasher-3.0-static
ubuntu@ubuntu:~/Downloads$ chmod a+x flasher-3.0-static
ubuntu@ubuntu:~/Downloads$ sudo rmmod cdc_phonet
Error: Module cdc_phonet is not currently loaded
ubuntu@ubuntu:~/Downloads$ sudo rmmod phonet
Error: Module phonet is not currently loaded
ubuntu@ubuntu:~/Downloads$ sudo ./flasher-3.0-static -f -F RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin -R
flasher v0.9.0 (Jan 19 2007)

SW version in image: RX-44_DIABLO_5.2008.43-7_PR_MR0
Image 'kernel', size 1536640 bytes
Version 2.6.21-200842maemo1
Image 'initfs', size 2327808 bytes
Version 0.95.22-200842maemo1w38b3
Image 'rootfs', size 125435904 bytes
Version RX-34+RX-44+RX-48_DIABLO_5.2008.43-7_PR_MR0
Image '2nd', size 8192 bytes
Valid for RX-44: 0808
Version 1.1.16-200844maemo2
Image 'xloader', size 9216 bytes
Valid for RX-44: 0808
Version 1.1.16-200844maemo2
Image 'secondary', size 100736 bytes
Valid for RX-44: 0808
Version 1.1.16-200844maemo2
Image '2nd', size 8192 bytes
Valid for RX-44: 0801, 0802, 0803, 0804, 0805, 0806, 0901, 0902
Version 1.1.16-200844maemo2
Image 'xloader', size 9216 bytes
Valid for RX-44: 0801, 0802, 0803, 0804, 0805, 0806, 0901, 0902
Version 1.1.16-200844maemo2
Image 'secondary', size 100736 bytes
Valid for RX-44: 0801, 0802, 0803, 0804, 0805, 0806, 0901, 0902
Version 1.1.16-200844maemo2
Suitable USB device not found, waiting
USB device found found at bus 001, device address 006
Error claiming USB interface: Device or resource busy

################################################## ######
If it helps, the Windows attempt was obtained from a different computer than the Ubuntu attempt.

Thanks to everyone for all the help so far.

The waiting to find your device message is fairly common.

The easiest trick on this is to hold and continue to hold the Home Key when you turn on your tablet right when you are told to do so.

Also, it would be wise to make sure the tablet is charging since turning it off and on constantly is quite the battery drain.

I would give you my outdated Windows version (which has never failed), but I just fired it up, and it's no longer happy like it used to be.

I guess it's looking for an updated version and then stalls which I've never seen before.

Maybe it has something to do with the repositories being down.

I'm not sure.

On the N810, right? I tried that, wasn't sure how long I should hold it, didn't seem to work.

Thanks, at this point I am willing to try anything.

I dusted off my old WinXP system just to try it, it complained of not being to find the libUSB driver, my Windows 7 machine found it all by itself. Not sure the different Windows OS would make any difference to the basic flashing issue.

SUCCESS!

Failed on Windows 7 Home and Starter, Failed on Ubuntu, after an initial failure, succeeded in an old Windows XP machine I had been meaning to throw away.

I was successful also in installing GarnetVM, just as I suspected, it needed the update. But after installing dosbox, the keyboard program for it failed to install, oh well.

But now that I have GarnetVM working, I feel much more at peace with what I don't know about this device yet. Now off to figure out the hotsync problem (and how to run VM from the card) . . .

For Garnet, copy and paste this into Xterm.

mkdir ~/.gvm/cards
echo -e "/media/mmc1\nRW" > ~/.gvm/cards/0

That will give you a memory slot on your SD card.

You should see a new folder called /PALM/Launcher/ on your external memory card where you can easily dump all of your .prc and .pdb files.

I can give you my stuff for Dosbox if you still need them.