Tried that. Got something rather odd:

sysinfo: Phone info (block phone-info) read failed (-1)
CMT: cannot open phonet0: no such device
Waiting for messages...

And it just hangs there.

Modprobe phonet (before everything else comes up) doesn't seem to do anything.

Edit 1: Apparently modprobe phonet0 doesn't actually create the phonet interface in /dev. Any clue how that's created?

Edit 2: Seems like you can just bring up the interface via ifconfig. Will try that when I get back.

Edit 3: Doesn't help. It just complains "No such device", even with the phonet module loaded..

Edit 4: I just got a copy of a u-boot bootable Backupmenu, and by studying its interface file, I think I might have a shadow of a clue on how to get phonet0 to start - apparently loading g_nokia and then configuring USB networking might do it. Not sure, though.

Edit 5: I apparently forgot to read through the scripts again. There's a netif-up script in /lib/phonet-utils which might do the trick.

Edit 6: That didn't work either. netif-up phonet0 gave me "Interface phonet0 not found". Loading g_nokia didn't help either.

Edit 7:
Got a few more errors after mounting sysfs and such:
CAL ERROR: open(/dev/mtd1): no such device.

Edit 8: I have a feeling I might not be able to fix this without fixing the USB port, sadly (which will be a while - I don't have access to a soldering iron, and won't for a few months - and it hasn't actually broken off yet, which slightly complicates things). The bootable backupmenu image does have a working (as far as I can tell) phonet0, but chrooting into a Maemo rootfs or trying to replicate its setup might be quite complex - and then it might not be able to open mtd1, which would be another complication.

Edit 9: Noticed another module I missed: omap_ssi. Maybe this will help?

Edit 10: So apparently inserting g_softupd (and skipping g_nokia) got me slightly further. I don't have the issues with phonet0 anymore. Unfortunately, I still get sysinfo: Phone info (block phone-info) read failed (-1) and CAL ERROR: open(/dev/mtd1): no such device, followed by a hang at Waiting for Messages.

Edit 11: In regards to MTD: does the hardware require some kind of offset to it be passed by kernel paramters? I've noticed something here:
http://lists.infradead.org/pipermail...ry/034078.html

Edit 12: Found something odd. In U-Boot, executing the command "mtdparts" (which is supposed to list the MTD partitions available) gives me "onenand: partitioning exceeds flash size".

Edit 13: There is definitely something wrong with U-Boot here. Somehow, mtdparts thinks that the size of onenand0 is 0. Therefore, any partition would be "too large".

Edit 14: Oddly enough, I'm able to read from any offset, though trying to specify size doesn't work, as it will just complain that I'm trying to read more than the chip size. Not specifying size, it just crashes. Trying to get it to dump a page from any offset also crashes U-Boot.

Edit 15: Checked dmesg messages. Interesting part relating to onenand:
omap2-onenand omap2-onenand: initializing on XS0, phys base 0x20000000, virtual base d1040000
onenand_wait: timeout! state 23 ctrl 0x0000 intr 0x8080
OneNAND Manufacturer: Unknown (0xa0)