Anyway to recover if I brick?

Yes, I already did the teardown and was going to use dd to make a “recovery” but I noticed there was only one partition. Yes it stopped a little short of all of the possible sectors so there might be a hidden partition (my guess that’s where /dev/sdb comes from?) but there’s no OS on the hard drisk, just the drive where your data is stored. Interesting enough, I attached the battery back to the board and powered it up without an hard drive and it boots up fine remembering my previous settings. I can connect to it with WiFi, explorer the web based UI (storage is missing [duh] and it does complain about sharing software but I assume it’s because it can’t find the directories), and ssh into it. Even further proving that the OS is on board/eMMC.  

Like I said, I’m just looking for a way to unbrick, I know a little bit about the ‘arm’ world and more about Linux so I feel confident about playing around but I really want a way to recover first. . I mainly want to install Gentoo so I can remove the stuff I don’t use/like, add features I do want/like, and allow for password protect/multiple users/etc. I would use a RPI or an Odroid but MPW is nicely packaged and pretty vs something I could aseemble on my own. If the current firmware wasn’t lacking many things I want, I would just fine tune it like you.

Just for reference, here’s a listing with no hard disk attached.

Edited to put the output of ‘fdisk -l’ into a spoiler section.

login as: root

root@192.168.60.1's password:
# fdisk -l

Disk /dev/mtdblock0: 0 MB, 131072 bytes, 256 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock1: 0 MB, 131072 bytes, 256 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock2: 0 MB, 131072 bytes, 256 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock3: 0 MB, 131072 bytes, 256 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock4: 1 MB, 1966080 bytes, 3840 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock5: 0 MB, 131072 bytes, 256 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock6: 5 MB, 5242880 bytes, 10240 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock7: 121 MB, 121110528 bytes, 236544 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock8: 1 MB, 1048576 bytes, 2048 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock9: 4 MB, 4194304 bytes, 8192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

#